mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Amrit Anand <quic_amrianan@quicinc.com>,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, agross@kernel.org, andersson@kernel.org,
	konrad.dybcio@linaro.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, kernel@quicinc.com,
	Elliot Berman <quic_eberman@quicinc.com>
Subject: Re: [PATCH 1/2] dt-bindings: hwinfo: Introduce board-id
Date: Thu, 25 Jan 2024 11:40:40 +0100	[thread overview]
Message-ID: <21eda361-ae7c-48d7-b1ea-ef1bfe8d9104@linaro.org> (raw)
In-Reply-To: <b4c27fb4-0cbf-7bad-3fc3-163fb4a5eb3f@quicinc.com>

On 24/01/2024 13:42, Amrit Anand wrote:

>>> +select:
>>> +  anyOf:
>>> +    - required:
>>> +        - 'board-id'
>>> +    - required:
>>> +        - 'board-id-types'
>>> +    - required:
>>> +        - '#board-id-cells'
>> I don't fully get why do you need this select. Isn't the schema selected
>> by nodename? Or maybe it is for the final required: but then this could
>> be just set of dependencies.
> The nodename here would be "/". So it will be applied to all the DTs, right?
> Here, we wanted this to apply only if the above mentioned properties are 
> present.

The nodename will select it.

> Do you suggest moving this to qcom,board-id.yaml and the required: as well.
> So that vendor specific yaml could be applied?

I suggest dropping the select.

Different topic is that we cannot even test it because you did not
provide any user of this binding.

>>> +
>>> +properties:
>>> +  $nodename:
>>> +    const: "/"
>> Blank line.
> Will add it.
>>> +  board-id:
>>> +    $ref: /schemas/types.yaml#/definitions/uint32-matrix
>>> +    description: |
>> Do not need '|' unless you need to preserve formatting.
> Ack
>>> +      A list of identifiers that can be used to match with this devicetree.
>> s/devicetree/Devicetree/ ?
> Will update
>>> +      The interpretatation of each cell can be matched with the
>> Typo: interpretation
> Will update
>>> +      board-id-type at the same index.
>>> +
>>> +  board-id-types:
>>> +    $ref: /schemas/types.yaml#/definitions/non-unique-string-array
>>> +    description:
>>> +      Defines the type of each cell, indicating to the DeviceTree selection
>> s/DeviceTree/Devicetree/ ?
> Will update
>>
>>> +      mechanism how to parse the board-id.
>>> +
>>> +  '#board-id-cells':
>>   What are the cells for?
> Bootloader will use this to check the number of entries in a tuple of 
> board-id.

Doesn't the board-id-type define number of cells? How could you have the
same board-id-type with different number of elements on board A and board B?


Best regards,
Krzysztof


  reply	other threads:[~2024-01-25 10:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-20 11:20 [PATCH 0/2] Add board-id support for multiple DT selection Amrit Anand
2024-01-20 11:20 ` [PATCH 1/2] dt-bindings: hwinfo: Introduce board-id Amrit Anand
2024-01-20 12:36   ` Rob Herring
2024-01-20 19:10   ` Trilok Soni
2024-01-22 10:10     ` Amrit Anand
2024-01-23 11:50       ` Krzysztof Kozlowski
2024-01-23 17:18         ` Conor Dooley
2024-01-23 18:51           ` Elliot Berman
2024-01-23 20:05             ` Trilok Soni
2024-01-24 12:44               ` Amrit Anand
2024-01-23 12:09   ` Krzysztof Kozlowski
2024-01-24 12:42     ` Amrit Anand
2024-01-25 10:40       ` Krzysztof Kozlowski [this message]
2024-01-24 15:00   ` Rob Herring
2024-01-20 11:20 ` [PATCH 2/2] dt-bindings: hwinfo: Add Qualcomm's board-id types Amrit Anand
2024-01-20 12:36   ` Rob Herring
2024-01-20 13:32   ` Konrad Dybcio
2024-01-22 10:07     ` Amrit Anand
2024-01-22 18:10       ` Elliot Berman
2024-01-22 19:27         ` Dmitry Baryshkov
2024-01-24 12:47         ` Amrit Anand
2024-01-21  2:05   ` kernel test robot
2024-01-22 18:12   ` Elliot Berman
2024-01-20 13:04 ` [PATCH 0/2] Add board-id support for multiple DT selection Konrad Dybcio
2024-01-22 17:50   ` Elliot Berman
2024-01-24 14:56 ` Rob Herring
2024-02-02  5:00   ` Amrit Anand
2024-02-14 12:56     ` Amrit Anand
2024-02-14 13:12       ` Krzysztof Kozlowski

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=21eda361-ae7c-48d7-b1ea-ef1bfe8d9104@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@quicinc.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_amrianan@quicinc.com \
    --cc=quic_eberman@quicinc.com \
    --cc=robh+dt@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

all inboxes | Powered by JetHome®