[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f21bc259-45fa-d14b-a556-625b813287f4@quicinc.com>
Date: Mon, 22 Jan 2024 15:40:04 +0530
From: Amrit Anand <quic_amrianan@...cinc.com>
To: Trilok Soni <quic_tsoni@...cinc.com>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
<agross@...nel.org>, <andersson@...nel.org>,
<konrad.dybcio@...aro.org>
CC: <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-msm@...r.kernel.org>, <kernel@...cinc.com>,
Elliot Berman
<quic_eberman@...cinc.com>
Subject: Re: [PATCH 1/2] dt-bindings: hwinfo: Introduce board-id
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@...cinc.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@...r.kernel.org will have concern folks from all the
architectures?
Please correct me.
Thanks,
Amrit.
Powered by blists - more mailing lists