From: Alex Elder <elder@linaro.org>
To: Stephen Boyd <swboyd@chromium.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
linux-arm-msm@vger.kernel.org,
Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [PATCH] arm64: dts: qcom: sc7180: Remove ipa_fw_mem node on trogdor
Date: Tue, 17 May 2022 14:51:34 -0500 [thread overview]
Message-ID: <ceb32b66-1341-d54f-a60a-5c342119c784@linaro.org> (raw)
In-Reply-To: <20220517193307.3034602-1-swboyd@chromium.org>
On 5/17/22 2:33 PM, Stephen Boyd wrote:
> We don't use this carveout on trogdor boards, and having it defined in
> the sc7180 SoC file causes an overlap message to be printed at boot.
>
> OF: reserved mem: OVERLAP DETECTED!
> memory@86000000 (0x0000000086000000--0x000000008ec00000) overlaps with memory@8b700000 (0x000000008b700000--0x000000008b710000)
>
> Delete the node in the trogdor dtsi file to fix the overlap problem and
> remove the error message.'
Is the mpss_mem node (which defines 0x86000000-0x8ec00000) correct?
You're right, we don't use that memory on Chrome OS, but I just
wondered whether the other node might also have a problem.
I don't actually know... Bjorn, do you?
-Alex
> Cc: Alex Elder <elder@linaro.org>
> Cc: Matthias Kaehlcke <mka@chromium.org>
> Fixes: 310b266655a3 ("arm64: dts: qcom: sc7180: define ipa_fw_mem node")
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
> arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi b/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi
> index 732e1181af48..262224504921 100644
> --- a/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi
> @@ -42,6 +42,7 @@ charger-crit {
> */
>
> /delete-node/ &hyp_mem;
> +/delete-node/ &ipa_fw_mem;
> /delete-node/ &xbl_mem;
> /delete-node/ &aop_mem;
> /delete-node/ &sec_apps_mem;
>
> base-commit: 42226c989789d8da4af1de0c31070c96726d990c
next prev parent reply other threads:[~2022-05-17 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 19:33 [PATCH] arm64: dts: qcom: sc7180: Remove ipa_fw_mem node on trogdor Stephen Boyd
2022-05-17 19:51 ` Alex Elder [this message]
2022-05-17 20:06 ` Stephen Boyd
2022-05-17 20:56 ` Alex Elder
2022-06-06 19:51 ` Stephen Boyd
2022-06-08 12:44 ` Alex Elder
2022-06-27 20:03 ` (subset) " 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=ceb32b66-1341-d54f-a60a-5c342119c784@linaro.org \
--to=elder@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=patches@lists.linux.dev \
--cc=swboyd@chromium.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).