[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240525-bountiful-reprogram-929d3bd18aed@spud>
Date: Sat, 25 May 2024 18:21:32 +0100
From: Conor Dooley <conor@...nel.org>
To: Elliot Berman <quic_eberman@...cinc.com>
Cc: Rob Herring <robh+dt@...nel.org>, Frank Rowand <frowand.list@...il.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Amrit Anand <quic_amrianan@...cinc.com>,
Peter Griffin <peter.griffin@...aro.org>,
Caleb Connolly <caleb.connolly@...aro.org>,
Andy Gross <agross@...nel.org>,
Doug Anderson <dianders@...omium.org>,
Simon Glass <sjg@...omium.org>, Chen-Yu Tsai <wenst@...omium.org>,
Julius Werner <jwerner@...omium.org>,
"Humphreys, Jonathan" <j-humphreys@...com>,
Sumit Garg <sumit.garg@...aro.org>,
Jon Hunter <jonathanh@...dia.org>,
Michal Simek <michal.simek@....com>,
boot-architecture@...ts.linaro.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH RFC v3 4/9] dt-bindings: arm: qcom: Update Devicetree
identifiers
On Tue, May 21, 2024 at 11:38:01AM -0700, Elliot Berman wrote:
> #define QCOM_BOARD_ID(a, major, minor) \
> - (((major & 0xff) << 16) | ((minor & 0xff) << 8) | QCOM_BOARD_ID_##a)
> + (((major & 0xff) << 16) | ((minor & 0xff) << 8) | ((QCOM_BOARD_ID_##a) & 0xff))
I assume there's no devices that have a >8 bit QCOM_BOARD_ID that would
end up with a different value in their dtb due to this change?
Cheers,
Conor.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists