From: David Heidelberg <david@ixit.cz>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.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] ARM: dts: qcom: apq8960: correct memory base
Date: Sat, 6 Jul 2024 15:03:08 -0700 [thread overview]
Message-ID: <b793eff2-2e38-49f8-8dbe-18c11d2b8f3e@ixit.cz> (raw)
In-Reply-To: <ir4hatefzt6luxkjrqro2bf5k7s2hnsw6o75q5543rakh2zpvg@wnnerfjswabz>
Hello Bjorn,
the apq8960 is just mental typo due to dealing with apq8064 code at same
time. I sent properly named patch [1] with your description and Dmitry's
R-b.
Thank you
David
[1] `ARM: dts: qcom: msm8960: correct memory base`
On 06/07/2024 13:05, Bjorn Andersson wrote:
> On Sat, Jul 06, 2024 at 12:34:07PM GMT, David Heidelberg wrote:
>> Bootloader will provide the information anyway to the kernel.
> How about we describe an actual problem here?
>
> Perhaps this is the problem you're solving?:
>
> """
> DeviceTree validation requires a unit address on the memory node, adjust
> the base to match [Ref] and use this as unit address.
>
> The bootloader will update the information with the actual values during
> boot.
> """
>
> I'd also prefer s/apq8960/msm8960/ in $subject, is there a reason why
> you did choose apq8960?
>
> Regards,
> Bjorn
>
>> Ref: https://github.com/msm8916-mainline/lk2nd/blob/main/target/msm8960/rules.mk
>>
>> Signed-off-by: David Heidelberg <david@ixit.cz>
>> ---
>> arch/arm/boot/dts/qcom/qcom-msm8960.dtsi | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git ./arch/arm/boot/dts/qcom/qcom-msm8960.dtsi ./arch/arm/boot/dts/qcom/qcom-msm8960.dtsi
>> index a9c6d2dbb460..ebc43c5c6e5f 100644
>> --- ./arch/arm/boot/dts/qcom/qcom-msm8960.dtsi
>> +++ ./arch/arm/boot/dts/qcom/qcom-msm8960.dtsi
>> @@ -47,9 +47,9 @@ L2: l2-cache {
>> };
>> };
>>
>> - memory {
>> + memory@80000000 {
>> device_type = "memory";
>> - reg = <0x0 0x0>;
>> + reg = <0x80000000 0>;
>> };
>>
>> cpu-pmu {
>> --
>> 2.45.2
>>
--
David Heidelberg
prev parent reply other threads:[~2024-07-06 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 19:34 David Heidelberg
2024-07-06 19:38 ` Dmitry Baryshkov
2024-07-06 20:05 ` Bjorn Andersson
2024-07-06 22:03 ` David Heidelberg [this message]
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=b793eff2-2e38-49f8-8dbe-18c11d2b8f3e@ixit.cz \
--to=david@ixit.cz \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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®