From: Kathiravan Thirumoorthy <quic_kathirav@quicinc.com>
To: Robert Marko <robimarko@gmail.com>
Cc: <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <srinivas.kandagatla@linaro.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: ipq8074: add QFPROM node
Date: Sun, 22 Jan 2023 22:35:43 +0530 [thread overview]
Message-ID: <29d9de45-1ce7-d6e5-bf02-052e911a067b@quicinc.com> (raw)
In-Reply-To: <CAOX2RU7p-0ZTx8fkY4hOk=Zmx6RT+1PwVL+CQxkjzVadm0ehTA@mail.gmail.com>
On 1/22/2023 10:29 PM, Robert Marko wrote:
> On Sun, 22 Jan 2023 at 17:57, Kathiravan Thirumoorthy
> <quic_kathirav@quicinc.com> wrote:
>>
>> On 1/21/2023 4:53 PM, Robert Marko wrote:
>>> IPQ8074 has efuses like other Qualcomm SoC-s that are required for
>>> determining various HW quirks which will be required later for CPR etc,
>>> so lets add the QFPROM node for start.
>>>
>>> Individidual fuses will be added as they are required.
>>>
>>> Signed-off-by: Robert Marko <robimarko@gmail.com>
>>> ---
>>> arch/arm64/boot/dts/qcom/ipq8074.dtsi | 7 +++++++
>>> 1 file changed, 7 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi
>>> index 8eba586065a3..f29491f647fe 100644
>>> --- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi
>>> +++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi
>>> @@ -301,6 +301,13 @@ mdio: mdio@90000 {
>>> status = "disabled";
>>> };
>>>
>>> + qfprom: efuse@a4000 {
>>> + compatible = "qcom,ipq8074-qfprom", "qcom,qfprom";
>>> + reg = <0x000a4000 0x1000>;
>>
>> From the HW document, I see the overall size of this region is 0x2000,
>> any reason to stick with 0x1000?
> Like always, I dont have access to docs and 0x1000 is all I could find
> downstream
> being used.
>
> Any chance you can share the regions inside of QFPROM, it would be great to use
> the ECC corrected one if available.
Sorry, What do you refer by "ECC corrected" here?
Thanks, Kathiravan T.
>
> Regards,
> Robert
>> Thanks, Kathiravan T.
>>
>>
>>> + #address-cells = <1>;
>>> + #size-cells = <1>;
>>> + };
>>> +
>>> prng: rng@e3000 {
>>> compatible = "qcom,prng-ee";
>>> reg = <0x000e3000 0x1000>;
next prev parent reply other threads:[~2023-01-22 17:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 11:23 [PATCH 1/2] dt-bindings: nvmem: qfprom: add IPQ8074 compatible Robert Marko
2023-01-21 11:23 ` [PATCH 2/2] arm64: dts: qcom: ipq8074: add QFPROM node Robert Marko
2023-01-22 16:57 ` Kathiravan Thirumoorthy
2023-01-22 16:59 ` Robert Marko
2023-01-22 17:05 ` Kathiravan Thirumoorthy [this message]
2023-01-22 17:09 ` Robert Marko
2023-01-23 4:44 ` Kathiravan Thirumoorthy
2023-01-23 9:46 ` Robert Marko
2023-01-22 11:59 ` [PATCH 1/2] dt-bindings: nvmem: qfprom: add IPQ8074 compatible 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=29d9de45-1ce7-d6e5-bf02-052e911a067b@quicinc.com \
--to=quic_kathirav@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).