linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Jamie Douglass <jamiemdouglass@gmail.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	phone-devel@vger.kernel.org,
	Dominik Kobinski <dominikkobinski314@gmail.com>,
	Konrad Dybico <konrad.dybico@linaro.org>
Subject: Re: [PATCH] arm64: dts: qcom: msm8992-lg-bullhead: Correct memory overlap with SMEM region
Date: Mon, 30 Jan 2023 16:03:27 +0100	[thread overview]
Message-ID: <CAB1t1CyGeXev-nfvgAfK+Wpny0EfyAiovNc6rH0miHzAWEoM=g@mail.gmail.com> (raw)
In-Reply-To: <fd879d4e-13d7-bb82-8668-a1423fc7e428@linaro.org>

On Mon, 30 Jan 2023 at 15:21, Konrad Dybcio <konrad.dybcio@linaro.org> wrote:
>
>
>
> On 30.01.2023 15:19, Petr Vorel wrote:
> > Hi Jamie,
> >
> > On Sat, 28 Jan 2023 at 06:53, Jamie Douglass <jamiemdouglass@gmail.com> wrote:
> >>
> >> A previously committed reserved memory region was overlapping with the
> >
> > IMHO there should be marked commit which you're fixing:
> > Fixes: 22c7e1a0fa45 ("arm64: dts: msm8992-bullhead: add memory hole region")
> Yes
>
> >
> >> SMEM memory region, causing an error message in dmesg:
> >>         OF: reserved mem: OVERLAP DETECTED!
> >>         reserved@5000000 (0x0000000005000000--0x0000000007200000)
> >>         overlaps with smem_region@6a00000
> >>         (0x0000000006a00000--0x0000000006c00000)
> >> This patch splits the previous reserved memory region into two
> >> reserved sections either side of the SMEM memory region.
> >
> > Reviewed-by: Petr Vorel <pvorel@suse.cz>
> > Tested-by: Petr Vorel <pvorel@suse.cz>
> > ...
> >> +++ b/arch/arm64/boot/dts/qcom/msm8992-lg-bullhead.dtsi
> >> @@ -53,8 +53,13 @@ cont_splash_mem: memory@3400000 {
> >>                         no-map;
> >>                 };
> >>
> >> -               removed_region: reserved@5000000 {
> >> -                       reg = <0 0x05000000 0 0x2200000>;
> >> +               reserved@5000000 {
> > Can we keep "removed_region:" ?
> > removed_region: reserved@5000000 {
> >
> >> +                       reg = <0x0 0x05000000 0x0 0x1a00000>;
> >> +                       no-map;
> >> +               };
> >> +
> >> +               reserved@6c00000 {
> > Not sure which label to add, maybe append 2?
> > removed_region2: reserved@6c00000 {
> > @Konrad @Krzysztof WDYT?
> Generally, if you don't expect that there'll be a need to
> amend/reference the node from somewhere else, the label is
> rather useless..

Thank you for info. To be honest I have no idea. Previously the label
was added, but that does not mean that it's used.
'git grep -l removed_region' shows only labels in few dts/dtsi, IMHO
it's not used. IMHO it looks ok to avoid it.

Kind regards,
Petr

>
> Konrad
>
> >
> > Kind regards,
> > Petr
> >
> >> +                       reg = <0x0 0x06c00000 0x0 0x400000>;
> >>                         no-map;
> >>                 };
> >>         };

      reply	other threads:[~2023-01-30 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28  5:52 [PATCH] arm64: dts: qcom: msm8992-lg-bullhead: Correct memory overlap with SMEM region Jamie Douglass
2023-01-28 14:30 ` Konrad Dybcio
2023-01-28 22:30   ` Jamie Douglass
2023-01-30 14:19 ` Petr Vorel
2023-01-30 14:21   ` Konrad Dybcio
2023-01-30 15:03     ` Petr Vorel [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='CAB1t1CyGeXev-nfvgAfK+Wpny0EfyAiovNc6rH0miHzAWEoM=g@mail.gmail.com' \
    --to=petr.vorel@gmail.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dominikkobinski314@gmail.com \
    --cc=jamiemdouglass@gmail.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=konrad.dybico@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;
as well as URLs for NNTP newsgroup(s).