From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Stefan Wahren <wahrenst@gmx.net>,
catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Eric Anholt <eric@anholt.net>
Cc: devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] ARM: dts: bcm2711: force CMA into first GB of memory
Date: Thu, 07 Nov 2019 10:42:30 +0100 [thread overview]
Message-ID: <b63a382c72bec9e52ea10f9d41aa45c6b1147eba.camel@suse.de> (raw)
In-Reply-To: <09138a9d-40a5-4c5f-0cf4-1cb73579c600@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1992 bytes --]
On Thu, 2019-11-07 at 07:23 +0100, Stefan Wahren wrote:
> Hi Nicolas,
>
> Am 06.11.19 um 10:59 schrieb Nicolas Saenz Julienne:
> > arm64 places the CMA in ZONE_DMA32, which is not good enough for the
> > Raspberry Pi 4 since it contains peripherals that can only address the
> > first GB of memory. Explicitly place the CMA into that area.
> >
> > Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
> >
> > ---
> >
> > Changes since v1:
> > - Move into bcm2711.dtsi
> >
> > arch/arm/boot/dts/bcm2711.dtsi | 20 ++++++++++++++++++++
> > 1 file changed, 20 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/bcm2711.dtsi b/arch/arm/boot/dts/bcm2711.dtsi
> > index 1f3acd3363ea..6000a01652fa 100644
> > --- a/arch/arm/boot/dts/bcm2711.dtsi
> > +++ b/arch/arm/boot/dts/bcm2711.dtsi
> > @@ -12,6 +12,26 @@
> >
> > interrupt-parent = <&gicv2>;
> >
> > + reserved-memory {
> > + #address-cells = <2>;
> > + #size-cells = <1>;
> > + ranges;
> > +
> > + /*
> > + * arm64 reserves the CMA by default somewhere in ZONE_DMA32,
> > + * that's not good enough for the Raspberry Pi 4 as some
>
> sorry for the nitpicking but i hope the Raspberry Pi 4 B wont be the
> only user of BCM2711.
No worries :)
It's better that way anyway.
>
> So please s/Raspberry Pi 4/BCM2711/
>
> Beside that:
>
> Acked-by: Stefan Wahren <wahrenst@gmx.net>
Thanks!
>
> > + * devices can only address the lower 1G of memory (ZONE_DMA).
> > + */
> > + linux,cma {
> > + compatible = "shared-dma-pool";
> > + size = <0x2000000>; /* 32MB */
> > + alloc-ranges = <0x0 0x00000000 0x40000000>;
> > + reusable;
> > + linux,cma-default;
> > + };
> > + };
> > +
> > +
> > soc {
> > /*
> > * Defined ranges:
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-11-07 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 9:59 [PATCH v2 0/2] arm64: Fix CMA/crashkernel reservation Nicolas Saenz Julienne
2019-11-06 9:59 ` [PATCH v2 1/2] ARM: dts: bcm2711: force CMA into first GB of memory Nicolas Saenz Julienne
2019-11-07 6:23 ` Stefan Wahren
2019-11-07 9:42 ` Nicolas Saenz Julienne [this message]
2019-11-14 20:28 ` Florian Fainelli
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=b63a382c72bec9e52ea10f9d41aa45c6b1147eba.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wahrenst@gmx.net \
/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).