From: Trilok Soni <quic_tsoni@quicinc.com>
To: Elliot Berman <quic_eberman@quicinc.com>,
Amrit Anand <quic_amrianan@quicinc.com>
Cc: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <agross@kernel.org>,
<konrad.dybcio@linaro.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<kernel@quicinc.com>, Conor Dooley <conor@kernel.org>,
<andersson@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH 1/2] dt-bindings: hwinfo: Introduce board-id
Date: Tue, 23 Jan 2024 12:05:56 -0800 [thread overview]
Message-ID: <fd2c8c1b-02f3-2750-3449-f93fc119fda2@quicinc.com> (raw)
In-Reply-To: <1941558d-d1e0-43b7-9208-65b9ba191bc2@quicinc.com>
On 1/23/2024 10:51 AM, Elliot Berman wrote:
>
>
> On 1/23/2024 9:18 AM, Conor Dooley wrote:
>> On Tue, Jan 23, 2024 at 12:50:07PM +0100, Krzysztof Kozlowski wrote:
>>> On 22/01/2024 11:10, Amrit Anand wrote:
>>>>
>>>> On 1/21/2024 12:40 AM, Trilok Soni wrote:
>>>>> On 1/20/2024 3:20 AM, Amrit Anand wrote:
>>>>>> From: Elliot Berman <quic_eberman@quicinc.com>
>>>>>>
>>>>>> Device manufacturers frequently ship multiple boards or SKUs under a
>>>>>> single software package. These software packages will ship multiple
>>>>>> devicetree blobs and require some mechanism to pick the correct DTB for
>>>>>> the board the software package was deployed. Introduce a common
>>>>>> definition for adding board identifiers to device trees. board-id
>>>>>> provides a mechanism for bootloaders to select the appropriate DTB which
>>>>>> is vendor/OEM-agnostic.
>>>>> Please extend CC list to more architectures? linux-arm-kernel, risc-v etc; since
>>>>> the proposal below is not specific to ARM but any architecture is using the
>>>>> devicetree.
>>>> Wouldn't devicetree@vger.kernel.org will have concern folks from all the
>>>> architectures?
>>>> Please correct me.
>>>
>>> No.
>>
>> The chromium guys should get a CC on future versions of this stuff,
>> since they like doing wacky things with compatible strings in their
>> bootloader and this problem is one they also face. Doug Anderson and the
>> mediatek chromebook folks would be a good start.
>>
>
> Please CC Peter Griffin from Linaro as he helped restart this
> discussion at Plumbers.
>
> Peter Griffin <peter.griffin@linaro.org>
>
> Also, for the oneplus boards:
> Caleb Connolly <caleb.connolly@linaro.org>
Thank you everyone. Amrit - please take care of above comments
when you post next revision and as suggested please add other
architecture mailing lists using the devicetree. Thank you.
--
---Trilok Soni
next prev parent reply other threads:[~2024-01-23 20:06 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 [this message]
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
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=fd2c8c1b-02f3-2750-3449-f93fc119fda2@quicinc.com \
--to=quic_tsoni@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@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;
as well as URLs for NNTP newsgroup(s).