Thread (51 messages) 51 messages, 8 authors, 2025-03-13

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

From: Krzysztof Kozlowski <krzk@kernel.org>
Date: 2025-03-10 21:17:36
Also in: kvmarm, linux-acpi, linux-arch, linux-devicetree, linux-hyperv, linux-pci, lkml

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
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help