On Thu, Jan 22, 2026 at 05:10:06PM +0100, Thierry Reding wrote:
From: Thierry Reding treding@nvidia.com
This node contains two sets of properties, one for the case where the VPR is resizable (in which case the VPR region will be dynamically allocated at boot time) and another case where the VPR is fixed in size and initialized by early firmware.
The firmware running on the device is responsible for updating the node with the real physical address for the fixed VPR case and remove the properties needed only for resizable VPR. Similarly, if the VPR is resizable, the firmware should remove the "reg" property since it is no longer needed.
Signed-off-by: Thierry Reding treding@nvidia.com
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 34 ++++++++++++++++++++++++ 1 file changed, 34 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra234.dtsi b/arch/arm64/boot/dts/nvidia/tegra234.dtsi index 850c473235e3..62a5dfde9e38 100644 --- a/arch/arm64/boot/dts/nvidia/tegra234.dtsi +++ b/arch/arm64/boot/dts/nvidia/tegra234.dtsi @@ -29,6 +29,40 @@ aliases { i2c8 = &dp_aux_ch3_i2c; };
- reserved-memory {
#address-cells = <2>;#size-cells = <2>;ranges;vpr: video-protection-region@0 {compatible = "nvidia,tegra-video-protection-region";
The heap name doesn't follow the documented convention, see https://docs.kernel.org/userspace-api/dma-buf-heaps.html#naming-convention