@@ -967,49 +967,3 @@ Buffer import on decoder can be tested by setting the ``capture-io-mode`` to ``5
967967 the V4L2 interface. See compliance data for what is available.
968968 #. Current driver supports 8 channel 1080p Encode and 8ch 1080p Decode
969969 owing to the default CMA Memory configuration.
970-
971-
972- *************************
973- Configuration of CMA Size
974- *************************
975-
976- Wave5 uses common CMA region to read and write buffers to, since the IP does not posses an on-chip MMU.
977-
978- .. ifconfig :: CONFIG_part_variant in ('J721S2')
979-
980- The CMA size can be adjusted by opening the board dtsi file :file: `arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi `,
981- finding the "linux,cma" node and changing the size attribute. The default value is 896MB.
982-
983- .. ifconfig :: CONFIG_part_variant in ('AM62AX')
984-
985- The CMA size can be adjusted by opening the board dts file :file: `arch/arm64/boot/dts/ti/k3-am62a7-sk.dts `,
986- finding the "linux,cma" node and changing the size attribute. The default value is 576MB.
987-
988- .. ifconfig :: CONFIG_part_variant in ('J784S4', 'J742S2')
989-
990- The CMA size can be adjusted by opening the board dts file :file: `arch/arm64/boot/dts/ti/k3-j784s4-evm.dts `,
991- finding the "linux,cma" node and changing the size attribute. The default value is 1792MB.
992-
993- .. ifconfig :: CONFIG_part_variant in ('J722S')
994-
995- The CMA size can be adjusted by opening the board dts file :file: `arch/arm64/boot/dts/ti/k3-j722s-evm.dts `,
996- finding the "linux,cma" node and changing the size attribute. The default value is 896MB.
997-
998- .. ifconfig :: CONFIG_part_variant in ('AM62PX')
999-
1000- The CMA size can be adjusted by opening the board dts file :file: `arch/arm64/boot/dts/ti/k3-am62p5-sk.dts `,
1001- finding the "linux,cma" node and changing the size attribute. The default value is 576MB.
1002-
1003- The value can be increased according to the availability of space in DDR memory map.
1004- CMA allocation can also be changed without re-compilation. One can stop at u-boot prompt during boot and update the CMA parameter as shown below:
1005-
1006- .. code-block :: console
1007-
1008- target # setenv args_all $args_all cma=1000M
1009- target # boot
1010-
1011- .. note ::
1012-
1013- Allocating at u-boot tends to place the CMA in the lower 32 bit region of memory. This is fine if the Wave5 is being
1014- used in isolated pipelines where the only goal is to encode/decode. If pipelines that incorporate other hardware elements
1015- are being used, then the correct method would be to allocate at device tree level for compatibility.
0 commit comments