Message ID | 20240613150902.2173582-4-devarsht@ti.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | Add global CMA reserve area | expand |
Hi Devarsh, On 20:39-20240613, Devarsh Thakkar wrote: > From: Brandon Brnich <b-brnich@ti.com> > > AM62p has different multimedia components such as Camera, Display, H264 > Video Codec which uses CMA for buffer allocations. We require 576MiB for 12 > channel decode-to-encode 720x480@30FPS use case. > > Signed-off-by: Brandon Brnich <b-brnich@ti.com> > Signed-off-by: Devarsh Thakkar <devarsht@ti.com> > --- > arch/arm64/boot/dts/ti/k3-am62p5-sk.dts | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts b/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts > index fb980d46e304..5ef74d9f8eea 100644 > --- a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts > +++ b/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts > @@ -48,6 +48,13 @@ reserved-memory { > #size-cells = <2>; > ranges; > > + linux,cma { > + compatible = "shared-dma-pool"; > + reusable; > + size = <0x00 0x24000000>; > + linux,cma-default; > + }; Since AM62p has 8gb memory, this allocation can come from upper portion. Doing so breaks Wave5 encoding/decoding as the driver can not yet handle 48 bit addressing. 48bit support is scheduled to be upstreamed, but unsure of when this will actually make it in. Could we force this into lower 32bits using same alloc-ranges as done in your AM62a patch[0]? [0]: https://patchwork.kernel.org/project/linux-arm-kernel/patch/20240613150902.2173582-3-devarsht@ti.com/ Best, Brandon > + > secure_tfa_ddr: tfa@9e780000 { > reg = <0x00 0x9e780000 0x00 0x80000>; > no-map; > -- > 2.39.1 >
Hi Vignesh, On 14/06/24 22:34, Brandon Brnich wrote: [..] >> diff --git a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts b/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts >> index fb980d46e304..5ef74d9f8eea 100644 >> --- a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts >> +++ b/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts >> @@ -48,6 +48,13 @@ reserved-memory { >> #size-cells = <2>; >> ranges; >> >> + linux,cma { >> + compatible = "shared-dma-pool"; >> + reusable; >> + size = <0x00 0x24000000>; >> + linux,cma-default; >> + }; > > Since AM62p has 8gb memory, this allocation can come from upper portion. > Doing so breaks Wave5 encoding/decoding as the driver can not yet handle > 48 bit addressing. 48bit support is scheduled to be upstreamed, but unsure of > when this will actually make it in. > > Could we force this into lower 32bits using same > alloc-ranges as done in your AM62a patch[0]? > I would like to take a look at this separately, is it possible for you to drop this patch [3/3] from series due to above comments and take the rest two from the series ? Regards Devarsh
diff --git a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts b/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts index fb980d46e304..5ef74d9f8eea 100644 --- a/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts +++ b/arch/arm64/boot/dts/ti/k3-am62p5-sk.dts @@ -48,6 +48,13 @@ reserved-memory { #size-cells = <2>; ranges; + linux,cma { + compatible = "shared-dma-pool"; + reusable; + size = <0x00 0x24000000>; + linux,cma-default; + }; + secure_tfa_ddr: tfa@9e780000 { reg = <0x00 0x9e780000 0x00 0x80000>; no-map;