From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D106F492522; Thu, 2 Jul 2026 12:58:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782997117; cv=none; b=rbbgvI1yJKi+BdqmKGDx0feVDDh4sQ4hqU1LxAidrPjsvNCDH57gmsnWQh+d/BnB+kFOmGtuOR0auNnG5fkae3aK4qAac5JyIb+91NkANLKcVMsKQPYu+T36KNRpwkNT4rXXI4CEVHMNxWJdSPwcZkpKwwEebZy3GVE1cd32gUk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782997117; c=relaxed/simple; bh=ShsbAZ+6W71qAbfGXVC0TvICNAKnIcCP/PU8K2kCMHY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=VI2FPfFps6xwl9YeMpdk2NehX0ip4NOJR6tuotz4hWqkmjjSL8HOiPbBYiC2KX4UPKcE9mamceyZ0q7FksYs53Vyabk8pc8in/6JW3I44WKcPZioVf4lTriwB65YtxfrKakK74FKIJn8l9ZV9P54TUfgZDoSP0sNOveJVNgaLx8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=kO4usZ5Q; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="kO4usZ5Q" Received: by smtp.kernel.org (Postfix) with ESMTPSA id EEC311F000E9; Thu, 2 Jul 2026 12:58:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782997116; bh=E/1DCNOv6BvGR9MJ9FvUvqyYS0lnKrQcbwU1VR2yiNw=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=kO4usZ5QxTv0KTmHTZC/qASNpRJK/tbL1yjometAkq37XaVoiPj9yYNJYSMa/miOy WDumAgPKPoA6O+ZAhZknNP5uy3myN2YtroWwxIDDh/D9adoYaQBir+NbjrazmpzPB/ G26xcrXk1KhYilWa5NJdthwc2uJy3iDeefPoHZlhdFDGTm+nZ6/SJsuST7sAsnkvJn dXE7Zj7K2yahM8tyC7aM0z9NdoTfrtRX0iFx9IZ2s+glDcBGyXLo+A5UHqZ60T2grQ plqvfAsOE08WmETjdkeuGfJSTD3aYifZvi/nV1eTiyVSnRKxXP1QYtapabLU1eTAKw hZ6pAM4+B/9zQ== Date: Thu, 2 Jul 2026 14:58:33 +0200 From: Thierry Reding To: "Rob Herring (Arm)" Cc: Christian Borntraeger , Rasmus Villemoes , dri-devel@lists.freedesktop.org, David Hildenbrand , Yury Norov , linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, Robin Murphy , Simona Vetter , linux-trace-kernel@vger.kernel.org, Krzysztof Kozlowski , Christian =?utf-8?B?S8O2bmln?= , linux-mm@kvack.org, Russell King , Will Deacon , Masami Hiramatsu , David Airlie , Vasily Gorbik , Benjamin Gaignard , linaro-mm-sig@lists.linaro.org, Heiko Carstens , Sumit Semwal , Thierry Reding , Maxime Ripard , Thierry Reding , John Stultz , Luca Ceresoli , Vlastimil Babka , Brian Starkey , Mikko Perttunen , Michal Hocko , Steven Rostedt , Jonathan Hunter , Maarten Lankhorst , Sowjanya Komatineni , Suren Baghdasaryan , linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org, devicetree@vger.kernel.org, "Liam R. Howlett" , linux-tegra@vger.kernel.org, Catalin Marinas , Marek Szyprowski , Conor Dooley , Thomas Zimmermann , Andrew Morton , Gerald Schaefer , Alexander Gordeev , Lorenzo Stoakes , "T.J. Mercier" , Mathieu Desnoyers , iommu@lists.linux.dev, Mike Rapoport , Sven Schnelle Subject: Re: [PATCH v3 01/11] dt-bindings: reserved-memory: Document Tegra VPR Message-ID: References: <20260701-tegra-vpr-v3-0-d80f7b871bb4@nvidia.com> <20260701-tegra-vpr-v3-1-d80f7b871bb4@nvidia.com> <178293558945.1610040.13281502080616690110.robh@kernel.org> Precedence: bulk X-Mailing-List: linux-trace-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="jt3c4zsxeledpb4t" Content-Disposition: inline In-Reply-To: <178293558945.1610040.13281502080616690110.robh@kernel.org> --jt3c4zsxeledpb4t Content-Type: text/plain; protected-headers=v1; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH v3 01/11] dt-bindings: reserved-memory: Document Tegra VPR MIME-Version: 1.0 On Wed, Jul 01, 2026 at 02:53:10PM -0500, Rob Herring (Arm) wrote: >=20 > On Wed, 01 Jul 2026 18:08:12 +0200, Thierry Reding wrote: > > From: Thierry Reding > >=20 > > The Video Protection Region (VPR) found on NVIDIA Tegra chips is a > > region of memory that is protected from CPU accesses. It is used to > > decode and play back DRM protected content. > >=20 > > It is a standard reserved memory region that can exist in two forms: > > static VPR where the base address and size are fixed (uses the "reg" > > property to describe the memory) and a resizable VPR where only the > > size is known upfront and the OS can allocate it wherever it can be > > accomodated. > >=20 > > Reviewed-by: Rob Herring (Arm) > > Signed-off-by: Thierry Reding > > --- > > Changes in v2: > > - add examples for fixed and resizable VPR > > --- > > .../nvidia,tegra-video-protection-region.yaml | 76 ++++++++++++++= ++++++++ > > 1 file changed, 76 insertions(+) > >=20 >=20 > My bot found errors running 'make dt_binding_check' on your patch: >=20 > yamllint warnings/errors: >=20 > dtschema/dtc warnings/errors: > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/r= eserved-memory/nvidia,tegra-video-protection-region.example.dtb: protected@= 2a8000000 (nvidia,tegra-video-protection-region): reg: [[2, 2818572288], [0= , 1879048192]] is too long > from schema $id: http://devicetree.org/schemas/reserved-memory/nvidia,te= gra-video-protection-region.yaml > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/r= eserved-memory/nvidia,tegra-video-protection-region.example.dtb: protected@= 2a8000000 (nvidia,tegra-video-protection-region): Unevaluated properties ar= e not allowed ('no-map', 'reg' were unexpected) > from schema $id: http://devicetree.org/schemas/reserved-memory/nvidia,te= gra-video-protection-region.yaml Any ideas why that second error shows up? It turns out that it goes away when the first one is fixed (which admittedly is a stupid mistake), but I spent quite a bit of time looking for a fix before realizing that it's only a side-effect of the first. Thierry --jt3c4zsxeledpb4t Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAmpGYHcACgkQ3SOs138+ s6FXSg/8DETX0ZuK2IIeUJbIHp/syjqHI0/Rww4Pal6HHyPG1Nmh7Mw8aUeTurgJ joGwb1v3IfLcjn3lMb2FCqe/oBcRBhmc8WlGWIiqiFfoTtXAPo8Rg64dg0l2ndIV u9BZrRKqkWLAjjq8uSoXf/8ub0GjtRGMSEiRqa4adYKV0VAUPUbQjEzfikHg91aU kSrCvilTLa1KSh268wVWvSEKjraNsiSBq+IoZ3L641ddHo9unPIuXnoFTZzFam4o xj7cgpnuBO79MYgpv5vlyz3Rz9W1twGkNdysDqEVRuh8kHJLNsaFrWhMEOeoTcMX iCyp3WySjGD1yBTs7VM2RXj9RvBllF0DYKc142VSpEPhsy49wMcjv8Bag05Zwzys LHSKvs1SF/dN62tw1x2kZs+Jd4+QcwlTfGDQbtf3Xtf88MP6QcXUUWXB+VMcWumA K4mrmfHiRpBrk7IW3c+b4lGwZ6Tl72Z1c6LI07ju7x3DohTXat7hYT2+iDZI1xfA s47ub8HQS6xthrn9/xco8ZPWOOjizZiMRSe7l/2gbvrymb1LINSe8uL0W6CFPCJ6 G37Ad7PfTI1b60hHNGhEGteQtvty4ZuUr126ehR9qrhkvpzYWRUT/ml5MeCYjsOY hJrS/jVvbJcphwokdb+6MUfkHN1EC7gbyLCALmMVjSqAec+7Ds0= =yG1A -----END PGP SIGNATURE----- --jt3c4zsxeledpb4t--