On Thu, Jul 02, 2026 at 01:10:27PM +0900, Mikko Perttunen wrote: > All of the resources implemented by Host1x hardware may not be available > to the software in cases where those resources are assigned to other vm > partitions through the hypervisor register region. > > Add properties nvidia,channels and nvidia,syncpoints to specify the > range of resources that are accessible by this partition / virtual > machine. > > The hypervisor or bootloader that configures the partitioning in the > hypervisor register region is responsible for updating the values of > these properties in accordance to the configuration. > > Signed-off-by: Mikko Perttunen <[email protected]> > --- > .../bindings/display/tegra/nvidia,tegra20-host1x.yaml | 12 > ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git > a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.yaml > b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.yaml > index ffd0ed857d28..a6bef28e8559 100644 > --- > a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.yaml > +++ > b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.yaml > @@ -96,6 +96,18 @@ properties: > items: > - description: phandle to the HEG or core power domain > > + nvidia,channels: > + $ref: /schemas/types.yaml#/definitions/uint32-array > + minItems: 2 > + maxItems: 2 > + description: Describes range of usable Host1x channels as a <base count> > tuple.
Pasting my reply just now from v1: Property has only one meaning in DT schema, so basically you are now fixing nvidia,channels to uint32-array for all possible use cases and nvidia devices. Well, you have been warned. Reviewed-by: Krzysztof Kozlowski <[email protected]> Best regards, Krzysztof
