From: Wei Xu <xuwei5@hisilicon.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>, <xuwei5@hisilicon.com>
Subject: Re: [PATCH] arm64: dts: hisilicon: hi3798cv200: Add missing dma-ranges
Date: Sat, 21 Mar 2026 14:52:08 +0800 [thread overview]
Message-ID: <69BE4018.6020600@hisilicon.com> (raw)
In-Reply-To: <20260227072210.1350159-1-shawnguo@kernel.org>
Hi Shawn,
On 2026/2/27 15:22, Shawn Guo wrote:
> Reboot starts failing on Poplar since commit 8424ecdde7df ("arm64: mm:
> Set ZONE_DMA size based on devicetree's dma-ranges"), which effectively
> changes zone_dma_bits from 30 to 32 for arm64 platforms that do not
> properly define dma-ranges in device tree. It's unclear how Poplar reboot
> gets broken by this change exactly, but a dma-ranges limiting zone_dma to
> the first 1 GB fixes the regression.
>
> Fixes: 2f20182ed670 ("arm64: dts: hisilicon: add dts files for hi3798cv200-poplar board")
> Cc: stable@vger.kernel.org
> Signed-off-by: Shawn Guo <shawnguo@kernel.org>
> ---
> arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi b/arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi
> index f6bc001c3832..2f4ad5da5e33 100644
> --- a/arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi
> +++ b/arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi
> @@ -122,6 +122,7 @@ soc: soc@f0000000 {
> #address-cells = <1>;
> #size-cells = <1>;
> ranges = <0x0 0x0 0xf0000000 0x10000000>;
> + dma-ranges = <0x0 0x0 0x0 0x40000000>;
>
> crg: clock-reset-controller@8a22000 {
> compatible = "hisilicon,hi3798cv200-crg", "syscon", "simple-mfd";
>
Applied to the HiSilicon arm64 dt tree.
Thanks!
Best Regards,
Wei
prev parent reply other threads:[~2026-03-21 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 7:22 [PATCH] arm64: dts: hisilicon: hi3798cv200: Add missing dma-ranges Shawn Guo
2026-03-21 6:52 ` Wei Xu [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=69BE4018.6020600@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.org \
--cc=stable@vger.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