| Message ID | 20191104135412.32118-2-nsaenzjulienne@suse.de (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | arm64: Fix CMA/crashkernel reservation | expand |
Hi Nicolas, Am 04.11.19 um 14:54 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> do you want this in Linux 5.5 via devicetree/fixes? In this case please add an fixes tag. Otherwise this will be queued for Linux 5.6. > --- > arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 19 +++++++++++++++++++ > 1 file changed, 19 insertions(+) > > diff --git a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts > index cccc1ccd19be..3c7833e9005a 100644 > --- a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts > +++ b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts > @@ -19,6 +19,25 @@ > reg = <0 0 0>; > }; > > + 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 > + * 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; > + }; > + }; > + i think this is a SoC-specific issue not a board specifc one. Please move this to bcm2711.dtsi Thanks Stefan > leds { > act { > gpios = <&gpio 42 GPIO_ACTIVE_HIGH>;
On Mon, 2019-11-04 at 18:09 +0100, Stefan Wahren wrote: > Hi Nicolas, > > Am 04.11.19 um 14:54 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> > > do you want this in Linux 5.5 via devicetree/fixes? In this case please > add an fixes tag. This has to go into v5.5 if the second patch is accepted. That said I can't add a fixes tag as the code being fixed isn't yet in linus' tree. Any suggestions? Maybe go through Catalin's tree? > Otherwise this will be queued for Linux 5.6. > > > --- > > arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 19 +++++++++++++++++++ > > 1 file changed, 19 insertions(+) > > > > diff --git a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts > > b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts > > index cccc1ccd19be..3c7833e9005a 100644 > > --- a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts > > +++ b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts > > @@ -19,6 +19,25 @@ > > reg = <0 0 0>; > > }; > > > > + 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 > > + * 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; > > + }; > > + }; > > + > > i think this is a SoC-specific issue not a board specifc one. Please > move this to bcm2711.dtsi Noted, thanks! Regards, Nicolas
On 11/4/19 9:09 AM, Stefan Wahren wrote: [snip] >> + 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 >> + * 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; >> + }; >> + }; >> + > > i think this is a SoC-specific issue not a board specifc one. Please > move this to bcm2711.dtsi This sounds like a possibly fragile solution if someone changes CONFIG_CMA_SIZE_MBYTES to a value greater than 32MB no? I know we don't want machine descriptors for ARM64 kernels, but since there is already a specific 2711 machine compatible string check, maybe you could use that as well for determining whether arm64_dma_phys_limit or arm64_dma32_phys_limit should be chosen?
On 11/4/19 9:51 AM, Florian Fainelli wrote: > On 11/4/19 9:09 AM, Stefan Wahren wrote: > > [snip] > >>> + 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 >>> + * 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; >>> + }; >>> + }; >>> + >> >> i think this is a SoC-specific issue not a board specifc one. Please >> move this to bcm2711.dtsi > > This sounds like a possibly fragile solution if someone changes > CONFIG_CMA_SIZE_MBYTES to a value greater than 32MB no? > > I know we don't want machine descriptors for ARM64 kernels, but since > there is already a specific 2711 machine compatible string check, maybe > you could use that as well for determining whether arm64_dma_phys_limit > or arm64_dma32_phys_limit should be chosen? This last sentence was referring to an earlier version of another patch series, this is not being done right now, although ARCH_BCM2835 does forcibly select ZONE_DMA. Nevermind then, I do not see a cleaner solution right now either.
On Mon, 2019-11-04 at 09:51 -0800, Florian Fainelli wrote: > On 11/4/19 9:09 AM, Stefan Wahren wrote: > > [snip] > > > > + 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 > > > + * 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; > > > + }; > > > + }; > > > + > > > > i think this is a SoC-specific issue not a board specifc one. Please > > move this to bcm2711.dtsi > > This sounds like a possibly fragile solution if someone changes > CONFIG_CMA_SIZE_MBYTES to a value greater than 32MB no? I agree it's not the most flexible solution in the world. It also bypasses the command line interface. But I can't see any alternatives as of today. Overall, I suggest that we set CMA's size to whatever is needed for a sensible desktop use. And let odd users with custom HW modify it trough overlays (which they will most likely be forced to do anyway). That said I'm open to suggestions. Regards, Nicolas
On Mon, Nov 04, 2019 at 06:09:39PM +0100, Stefan Wahren wrote: > Hi Nicolas, > > Am 04.11.19 um 14:54 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> > > do you want this in Linux 5.5 via devicetree/fixes? In this case please > add an fixes tag. That's not really a fix since AFAICT CMA never worked properly on RPi4 with mainline. For 5.5, I queued the arm64 for-next/zone-dma patches which would allow RPi4 to get a CMA in the correct physical address range. However, since these patches cause a regression on other platforms that don't need a small ZOEN_DMA, my suggestion was to leave the CMA handling for RPi4 as per the current mainline (i.e. broken) and allow CMA from the full ZONE_DMA32 range (second patch in this series). IIUC, this dts patch can be merged independently of the ZONE_DMA patches for arm64 and it may be beneficial for current mainline (even without the arm64/for-next/zone-dma patches). [1] git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux for-next/zone-dma > Otherwise this will be queued for Linux 5.6. I'm happy to queue them together with your ack for 5.5, otherwise I'll only pick the second patch in this series. Thanks.
Am 05.11.19 um 15:51 schrieb Catalin Marinas: > Otherwise this will be queued for Linux 5.6. > I'm happy to queue them together with your ack for 5.5, otherwise I'll > only pick the second patch in this series. I had a comment for this patch which should be addressed in V2. After that i'm happy to gave my Ack. Thanks Stefan > > Thanks. >
diff --git a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts index cccc1ccd19be..3c7833e9005a 100644 --- a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts +++ b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts @@ -19,6 +19,25 @@ reg = <0 0 0>; }; + 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 + * 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; + }; + }; + leds { act { gpios = <&gpio 42 GPIO_ACTIVE_HIGH>;
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> --- arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)