All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Acayan <mailingradian@gmail.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: sdm670: add qfprom node
Date: Tue, 6 Dec 2022 17:27:17 -0500	[thread overview]
Message-ID: <Y4/BxaesXpr7nnbF@radian> (raw)
In-Reply-To: <20221205232103.bz4ar3dbmocfl3yv@builder.lan>

On Mon, Dec 05, 2022 at 05:21:03PM -0600, Bjorn Andersson wrote:
> On Mon, Dec 05, 2022 at 06:01:15PM -0500, Richard Acayan wrote:
>> Some hardware quirks and capabilities can be determined by reading the
>> fuse-programmable read-only memory. Add the QFPROM node so consumers
>> know if they need to do anything extra to support the hardware.
>> 
>> Signed-off-by: Richard Acayan <mailingradian@gmail.com>
>> ---
>>  arch/arm64/boot/dts/qcom/sdm670.dtsi | 7 +++++++
>>  1 file changed, 7 insertions(+)
>> 
>> diff --git a/arch/arm64/boot/dts/qcom/sdm670.dtsi b/arch/arm64/boot/dts/qcom/sdm670.dtsi
>> index f93705bc549f..933ad2fabf3a 100644
>> --- a/arch/arm64/boot/dts/qcom/sdm670.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sdm670.dtsi
>> @@ -731,6 +731,13 @@ gcc: clock-controller@100000 {
>>  			#power-domain-cells = <1>;
>>  		};
>>  
>> +		qfprom: qfprom@780000 {
>> +			compatible = "qcom,sdm670-qfprom", "qcom,qfprom";
>> +			reg = <0 0x780000 0 0x1000>;
>
> I suspect the qfprom block is inherited from SDM845, if so 0x780000
> contains raw, uncorrected data, while 0x784000 contains ECC-corrected
> versions of these. Please validate and use the same.

I just compared the qusb2p_hstx_trim values at 0x7801eb and 0x7841eb and
this seems to be true. Will change in the next version.

>
> Also, please pad the address to 8 digits, to make it easier to check the
> sort order.

Ack.

>
> Thanks,
> Bjorn
>
>> +			#address-cells = <1>;
>> +			#size-cells = <1>;
>> +		};
>> +
>>  		sdhc_1: mmc@7c4000 {
>>  			compatible = "qcom,sdm670-sdhci", "qcom,sdhci-msm-v5";
>>  			reg = <0 0x007c4000 0 0x1000>,
>> -- 
>> 2.38.1
>> 

  reply	other threads:[~2022-12-06 22:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05 23:01 [PATCH 1/3] dt-bindings: nvmem: qfprom: add sdm670 compatible Richard Acayan
2022-12-05 23:01 ` [PATCH 2/3] arm64: dts: qcom: sdm670: add qfprom node Richard Acayan
2022-12-05 23:21   ` Bjorn Andersson
2022-12-06 22:27     ` Richard Acayan [this message]
2022-12-05 23:01 ` [PATCH 3/3] arm64: dts: qcom: sdm670: add missing usb hstx nvmem cell Richard Acayan
2022-12-06  8:50 ` [PATCH 1/3] dt-bindings: nvmem: qfprom: add sdm670 compatible Krzysztof Kozlowski
2023-01-03 11:58 ` Srinivas Kandagatla
  -- strict thread matches above, loose matches on Subject: below --
2022-12-06 23:17 Richard Acayan
2022-12-06 23:17 ` [PATCH 2/3] arm64: dts: qcom: sdm670: add qfprom node Richard Acayan
2022-12-07 10:17   ` Konrad Dybcio
2022-12-07 16:59   ` 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=Y4/BxaesXpr7nnbF@radian \
    --to=mailingradian@gmail.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.