linux-kernel - Re: [PATCH hyperv-next v5 07/11] dt-bindings: microsoft,vmbus: Add interrupts and DMA coherence

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ff3739bb-a223-401e-9b70-a5201839b72c@kernel.org>
Date: Mon, 10 Mar 2025 22:17:20 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Roman Kisel <romank@...ux.microsoft.com>
Cc: arnd@...db.de, bhelgaas@...gle.com, bp@...en8.de,
 catalin.marinas@....com, conor+dt@...nel.org, dave.hansen@...ux.intel.com,
 decui@...rosoft.com, haiyangz@...rosoft.com, hpa@...or.com,
 joey.gouly@....com, krzk+dt@...nel.org, kw@...ux.com, kys@...rosoft.com,
 lenb@...nel.org, lpieralisi@...nel.org, manivannan.sadhasivam@...aro.org,
 mark.rutland@....com, maz@...nel.org, mingo@...hat.com,
 oliver.upton@...ux.dev, rafael@...nel.org, robh@...nel.org,
 ssengar@...ux.microsoft.com, sudeep.holla@....com, suzuki.poulose@....com,
 tglx@...utronix.de, wei.liu@...nel.org, will@...nel.org,
 yuzenghui@...wei.com, devicetree@...r.kernel.org, kvmarm@...ts.linux.dev,
 linux-acpi@...r.kernel.org, linux-arch@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-hyperv@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org, x86@...nel.org,
 apais@...rosoft.com, benhill@...rosoft.com, bperkins@...rosoft.com,
 sunilmut@...rosoft.com
Subject: Re: [PATCH hyperv-next v5 07/11] dt-bindings: microsoft,vmbus: Add
 interrupts and DMA coherence

On 10/03/2025 19:07, Roman Kisel wrote:
> 
> It is modeled as a bus in the kernel:
> https://www.kernel.org/doc/html/latest/virt/hyperv/vmbus.html
> 
>> Please upstream bindings for the bus devices and extend the example here
>> with these devices.
> 
> The set of synthetic devices that reside on the bus isn't fixed, and
> they don't require description neither in ACPI nor in DT as
> the devices negotiate their MMIO regions through the hyperv driver.
> 
> Perhaps, it is not as much bus as expected by the YAML files.

OK, then this is not really a bus from the bindings point of view. It is
a device schema which should end with additionalProperties: false.

If you have report about that pinctrl-0, it means you have undocumented
properties in your DTS. Maybe that's the dma-coherence you mentioned in
the commit msg.


Best regards,
Krzysztof