On 5/4/22 17:43, Rob Herring wrote:
On Fri, Apr 29, 2022 at 8:02 AM Bharat Kumar Gogada
<bharat.kumar.gogada@xxxxxxxxxx> wrote:
Describe cpm reg property before cfg reg property to align with
node name.
The order is an ABI. If breaking it is okay, explain why here.
I didn't push any description for versal to upstream u-boot or linux yet but
xilinx is using this order for years. DT binding order wasn't aligned to it.
For example: (Xilinx Linux is in sync with this).
https://github.com/Xilinx/u-boot-xlnx/blob/master/arch/arm/dts/versal.dtsi
Driver itself is working with reg-names and order of regs doesn't matter. It
means changed order doesn't break any functionality.
Right now reg order really matter in binding doc but would be good in these
examples to record that both ways are fine.
Would it be better to describe that both ways are fine?
reg-names:
oneOf:
- items:
- const: cfg
- const: cpm_slcr
- items:
- const: cpm_slcr
- const: cfg
Another small reason is that all hard IPs in Versal are normally placed below
4GB address range. And there are some others which also have mapping above. This
is one of that example and we normally aligned with 32bit address.
And the biggest reason is that current node name is pcie@fca10000 which should
be aligned with the first register base which is before this patch 0x600000000
but name suggest that the first reg should be cpm_slcr instead of cfg. That's
why I consider this patch as a fix and the patch should contain fixed tag.
Thanks,
Michal
