linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sean Anderson <sean.anderson@seco.com>,
	Vinod Koul <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	linux-phy@lists.infradead.org
Cc: devicetree@vger.kernel.org, "Fernández Rojas" <noltari@gmail.com>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	"Madalin Bucur" <madalin.bucur@nxp.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Jonas Gorski" <jonas.gorski@gmail.com>,
	linux-gpio@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
	"Camelia Alexandra Groza" <camelia.groza@nxp.com>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Ioana Ciornei" <ioana.ciornei@nxp.com>,
	linuxppc-dev@lists.ozlabs.org,
	"Bartosz Golaszewski" <brgl@bgdev.pl>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v11 03/13] dt-bindings: Convert gpio-mmio to yaml
Date: Tue, 14 Mar 2023 20:59:23 +0100	[thread overview]
Message-ID: <3d34e35f-fb5a-7522-9717-dd3402dd88d3@linaro.org> (raw)
In-Reply-To: <b7f45fc2-85f5-ad29-2dc4-bc059cac022e@seco.com>

On 14/03/2023 20:52, Sean Anderson wrote:
> On 3/14/23 15:45, Krzysztof Kozlowski wrote:
>> On 14/03/2023 19:50, Sean Anderson wrote:
>>> On 3/14/23 14:32, Krzysztof Kozlowski wrote:
>>>> On 14/03/2023 19:09, Sean Anderson wrote:
>>>>> On 3/14/23 13:56, Krzysztof Kozlowski wrote:
>>>>>> On 13/03/2023 17:11, Sean Anderson wrote:
>>>>>> +  reg-names:
>>>>>>> +    minItems: 1
>>>>>>> +    maxItems: 5
>>>>>>> +    items:
>>>>>>> +      enum:
>>>>>>
>>>>>> Why this is in any order? Other bindings were here specific, your 'reg'
>>>>>> is also specific/fixed.
>>>>>
>>>>> Some devicetrees have dirout first, and other have dat first. There is no
>>>>> mandatory order, and some registers can be included or left out as is
>>>>> convenient to the devicetree author.
>>>>>
>>>>> reg is not specific/fixed either. It is just done that way for
>>>>> convenience (and to match the names here).
>>>>
>>>> The items have order and usually we require strict order from DTS,
>>>> unless there is a reason. If there is no reason, use fixed order and
>>>> then fix the DTS.
>>>
>>> The items do not have order. That is the whole point of having a
>>> separate names property. The DTs are not "broken" for taking advantage
>>> of a longstanding feature. There is no advantage to rewriting them to
>>> use a fixed order, especially when there is no precedent. This is just
>>> an area where json schema cannot completely validate devicetrees.
>>
>> I don't understand "there is no precedent".There is - we rewrite
>> hundreds of DTS. Just look at mine and other people commits.
> 
> There is no precedent for a fixed order of registers for this device.
> We have always used reg-names to interpret regs.

And who is "we"? Bootloader? Firmware? BSD? Because they all matter. It
does not matter that one particular driver uses reg-names. The common
rule is always the same - entries are ordered and fixed (with exceptions).

> 
>> The reg-names are helper and entries were always expected to be ordered
> 
> This is not the case for this device. Registers may be in any order, and

Their physical order does not determine the order of entries in DT.

> some registers may be omitted (and not always the same ones).

OK, that's the reason.

> reg-names is the
> only way to determine which registers are present.


Best regards,
Krzysztof


  reply	other threads:[~2023-03-14 20:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 16:11 [PATCH v11 00/13] phy: Add support for Lynx 10G SerDes Sean Anderson
2023-03-13 16:11 ` [PATCH v11 01/13] dt-bindings: phy: Add 2500BASE-X and 10GBASE-R Sean Anderson
2023-03-13 16:11 ` [PATCH v11 02/13] dt-bindings: phy: Add Lynx 10G phy binding Sean Anderson
2023-03-13 16:11 ` [PATCH v11 03/13] dt-bindings: Convert gpio-mmio to yaml Sean Anderson
2023-03-13 21:43   ` Linus Walleij
2023-03-14 17:56   ` Krzysztof Kozlowski
2023-03-14 18:09     ` Sean Anderson
2023-03-14 18:32       ` Krzysztof Kozlowski
2023-03-14 18:50         ` Sean Anderson
2023-03-14 19:45           ` Krzysztof Kozlowski
2023-03-14 19:52             ` Sean Anderson
2023-03-14 19:59               ` Krzysztof Kozlowski [this message]
2023-03-15 12:23   ` kernel test robot
2023-03-13 16:11 ` [PATCH v11 04/13] dt-bindings: gpio-mmio: Add compatible for QIXIS Sean Anderson
2023-03-13 16:11 ` [PATCH v11 05/13] dt-bindings: clock: Add ids for Lynx 10g PLLs Sean Anderson
2023-03-13 16:11 ` [PATCH v11 06/13] clk: Add Lynx 10G SerDes PLL driver Sean Anderson
2023-03-13 16:11 ` [PATCH v11 07/13] phy: fsl: Add Lynx 10G SerDes driver Sean Anderson
2023-03-13 16:11 ` [PATCH v11 08/13] phy: lynx10g: Enable by default on Layerscape Sean Anderson
2023-03-13 16:11 ` [PATCH v11 09/13] arm64: dts: ls1046a: Add serdes nodes Sean Anderson
2023-03-14  7:08   ` Shawn Guo
2023-03-17 19:17     ` Sean Anderson
2023-03-13 16:11 ` [PATCH v11 10/13] arm64: dts: ls1046ardb: Add serdes descriptions Sean Anderson
2023-03-13 16:11 ` [PATCH v11 11/13] arm64: dts: ls1088a: Add serdes nodes Sean Anderson
2023-03-13 16:11 ` [PATCH v11 12/13] arm64: dts: ls1088a: Prevent PCSs from probing as phys Sean Anderson
2023-03-13 16:11 ` [PATCH v11 13/13] arm64: dts: ls1088ardb: Add serdes descriptions Sean Anderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3d34e35f-fb5a-7522-9717-dd3402dd88d3@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=bagasdotme@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=camelia.groza@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ioana.ciornei@nxp.com \
    --cc=jonas.gorski@gmail.com \
    --cc=kishon@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madalin.bucur@nxp.com \
    --cc=noltari@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sean.anderson@seco.com \
    --cc=vkoul@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).