From: Luca Weiss <luca@z3ntu.xyz>
To: Bjorn Andersson <andersson@kernel.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@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 1/2] arm64: dts: qcom: msm8953: Set initial address for memory
Date: Sun, 03 Dec 2023 11:38:13 +0100 [thread overview]
Message-ID: <2575326.iZASKD2KPV@z3ntu.xyz> (raw)
In-Reply-To: <t6ckvr7bcpoc3z4cam7bilp67nn6qyvrmnqch6tlkwug7n2neq@32f5mso75fvu>
On Sonntag, 3. Dezember 2023 05:20:23 CET Bjorn Andersson wrote:
> On Sat, Nov 25, 2023 at 01:19:27PM +0100, Luca Weiss wrote:
> > The dtbs_check really doesn't like having memory without reg set.
> >
> > The base address depends on the amount of RAM you have:
> > <= 2.00 GiB RAM: 0x80000000
> >
> > = 3.00 GiB RAM: 0x40000000
> > = 3.75 GiB RAM: 0x10000000
> >
> > (more does not fit into the 32-bit physical address space)
> >
> > So, let's pick one of the values, 0x10000000 which is used on devices
> > with 3.75 GiB RAM. Since the bootloader will update it to what's present
> > on the device it doesn't matter too much.
> >
> > Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> > ---
> >
> > arch/arm64/boot/dts/qcom/msm8953.dtsi | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/msm8953.dtsi
> > b/arch/arm64/boot/dts/qcom/msm8953.dtsi index e7de7632669a..a3ba24ca599b
> > 100644
> > --- a/arch/arm64/boot/dts/qcom/msm8953.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/msm8953.dtsi
> > @@ -174,10 +174,10 @@ scm: scm {
> >
> > };
> >
> > };
> >
> > - memory {
>
> Wouldn't it be sufficient to add @0 here, to please dtbs_check?
The checker itself also seems to be okay with memory@0 and no other change,
but there's this warning with W=1
arch/arm64/boot/dts/qcom/msm8953.dtsi:177.11-181.4: Warning (unique_unit_address_if_enabled): /memory@0: duplicate unit-address (also used in node /soc@0)
So probably we should still try to put it at a reasonable address like
0x10000000?
Regards
Luca
>
> Regards,
> Bjorn
>
> > + memory@10000000 {
> >
> > device_type = "memory";
> > /* We expect the bootloader to fill in the reg */
> >
> > - reg = <0 0 0 0>;
> > + reg = <0 0x10000000 0 0>;
> >
> > };
> >
> > pmu {
next prev parent reply other threads:[~2023-12-03 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 12:19 [PATCH v2 0/2] Small dtsi fixes for msm8953 SoC Luca Weiss
2023-11-25 12:19 ` [PATCH v2 1/2] arm64: dts: qcom: msm8953: Set initial address for memory Luca Weiss
2023-12-03 4:20 ` Bjorn Andersson
2023-12-03 10:38 ` Luca Weiss [this message]
2023-11-25 12:19 ` [PATCH v2 2/2] arm64: dts: qcom: msm8953: Use non-deprecated qcom,domain in LPASS Luca Weiss
2023-12-03 4:54 ` (subset) [PATCH v2 0/2] Small dtsi fixes for msm8953 SoC Bjorn Andersson
2023-12-10 23:25 ` 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=2575326.iZASKD2KPV@z3ntu.xyz \
--to=luca@z3ntu.xyz \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@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=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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