From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Kathiravan T <quic_kathirav@quicinc.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 3/4] arm64: dts: qcom: ipq6018: add QFPROM node
Date: Fri, 26 May 2023 15:28:09 +0200 [thread overview]
Message-ID: <a6a69233-1a59-b775-9679-bdd7a95ce468@linaro.org> (raw)
In-Reply-To: <CAA8EJpqSsTxpafOQZBBSZts2ZvxR1Wb6LMdcwnTxZvmyN=OSQA@mail.gmail.com>
On 26.05.2023 15:22, Dmitry Baryshkov wrote:
> On Fri, 26 May 2023 at 15:54, Kathiravan T <quic_kathirav@quicinc.com> wrote:
>>
>> IPQ6018 has efuse region to determine the various HW quirks. Lets
>> add the initial support and the individual fuses will be added as they
>> are required.
>>
>> Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>
>> ---
>> Changes in V2:
>> - Reorder the node based on node address
>>
>> arch/arm64/boot/dts/qcom/ipq6018.dtsi | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/ipq6018.dtsi b/arch/arm64/boot/dts/qcom/ipq6018.dtsi
>> index f531797f2619..0f6d6c6daed2 100644
>> --- a/arch/arm64/boot/dts/qcom/ipq6018.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/ipq6018.dtsi
>> @@ -302,6 +302,13 @@
>> status = "disabled";
>> };
>>
>> + qfprom: efuse@a4000 {
>> + compatible = "qcom,ipq6018-qfprom", "qcom,qfprom";
>> + reg = <0x0 0x000a4000 0x0 0x2000>;
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + };
>> +
>> prng: qrng@e1000 {
>> compatible = "qcom,prng-ee";
>> reg = <0x0 0x000e3000 0x0 0x1000>;
>
> It looks like the prng node name is incorrect. It should be qrng@e3000
> instead of qrng@e1000. Could you please send a followup to fix it?
In case that wasn't clear, since I think this series will go in as-is,
that fix would be sent separately, on top of this.
Konrad
>
> For this patch:
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>
>> --
>> 2.17.1
>>
>
>
next prev parent reply other threads:[~2023-05-26 13:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 12:53 [PATCH V2 0/4] Add QFPROM support for few IPQ SoCs Kathiravan T
2023-05-26 12:53 ` [PATCH V2 1/4] dt-bindings: nvmem: qfprom: add compatible " Kathiravan T
2023-05-30 12:59 ` Krzysztof Kozlowski
2023-05-30 13:03 ` Krzysztof Kozlowski
2023-05-30 13:03 ` Krzysztof Kozlowski
2023-05-26 12:53 ` [PATCH V2 2/4] arm64: dts: qcom: ipq5332: add QFPROM node Kathiravan T
2023-05-26 12:53 ` [PATCH V2 3/4] arm64: dts: qcom: ipq6018: " Kathiravan T
2023-05-26 12:54 ` Konrad Dybcio
2023-05-26 13:22 ` Dmitry Baryshkov
2023-05-26 13:28 ` Konrad Dybcio [this message]
2023-05-26 12:53 ` [PATCH V2 4/4] arm64: dts: qcom: ipq9574: " Kathiravan T
2023-05-27 1:07 ` [PATCH V2 0/4] Add QFPROM support for few IPQ SoCs Bjorn Andersson
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=a6a69233-1a59-b775-9679-bdd7a95ce468@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kathirav@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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®