<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-dev/Documentation/devicetree/bindings/virtio, branch master</title>
<subtitle>Linux kernel development work - see feature branches</subtitle>
<id>https://git.zx2c4.com/linux-dev/atom/Documentation/devicetree/bindings/virtio?h=master</id>
<link rel='self' href='https://git.zx2c4.com/linux-dev/atom/Documentation/devicetree/bindings/virtio?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/'/>
<updated>2022-09-26T18:39:55Z</updated>
<entry>
<title>dt-bindings: virtio: Convert virtio,pci-iommu to DT schema</title>
<updated>2022-09-26T18:39:55Z</updated>
<author>
<name>Jean-Philippe Brucker</name>
<email>jean-philippe@linaro.org</email>
</author>
<published>2022-09-23T07:44:38Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=803184f1ef815b39ec266ff25a0e7f00760e2e69'/>
<id>urn:sha1:803184f1ef815b39ec266ff25a0e7f00760e2e69</id>
<content type='text'>
Convert the binding that describes the virtio-pci based IOMMU to DT
schema. Change the compatible string to "pci&lt;vendor&gt;,&lt;device&gt;", which is
defined by the PCI Bus Binding, but keep "virtio,pci-iommu" as an option
for backward compatibility.

Signed-off-by: Jean-Philippe Brucker &lt;jean-philippe@linaro.org&gt;
Reviewed-by: Krzysztof Kozlowski &lt;krzysztof.kozlowski@linaro.org&gt;
Link: https://lore.kernel.org/r/20220923074435.420531-1-jean-philippe@linaro.org
Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;
</content>
</entry>
<entry>
<title>dt-bindings: virtio: mmio: add optional wakeup-source property</title>
<updated>2022-08-11T08:06:38Z</updated>
<author>
<name>Minghao Xue</name>
<email>quic_mingxue@quicinc.com</email>
</author>
<published>2022-06-10T08:58:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=51ded7cdf26deea7dd875047c2f005b81e80bdf4'/>
<id>urn:sha1:51ded7cdf26deea7dd875047c2f005b81e80bdf4</id>
<content type='text'>
Some systems want to set the interrupt of virtio_mmio device
as a wakeup source. On such systems, we'll use the existence
of the "wakeup-source" property as a signal of requirement.

Signed-off-by: Minghao Xue &lt;quic_mingxue@quicinc.com&gt;
Reviewed-by: Krzysztof Kozlowski &lt;krzysztof.kozlowski@linaro.org&gt;
Message-Id: &lt;1654851507-13891-2-git-send-email-quic_mingxue@quicinc.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
</content>
</entry>
<entry>
<title>dt-bindings: virtio,mmio: Allow setting devices 'dma-coherent'</title>
<updated>2022-03-20T19:08:08Z</updated>
<author>
<name>Rob Herring</name>
<email>robh@kernel.org</email>
</author>
<published>2022-03-10T01:35:27Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=6ac02df3fff71ddacc71e2ae79b73c16873b41c5'/>
<id>urn:sha1:6ac02df3fff71ddacc71e2ae79b73c16873b41c5</id>
<content type='text'>
'virtio,mmio' devices are always coherent within a guest. As Arm DTs
are default non-coherent, the 'dma-coherent' property needs to be set on
the virtio device to mark them as such. This aligns with the QEMU 'virt'
machine DTB.

Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;
Link: https://lore.kernel.org/r/20220310013528.549030-1-robh@kernel.org
</content>
</entry>
<entry>
<title>dt-bindings: virtio: Add binding for virtio devices</title>
<updated>2021-09-05T20:23:08Z</updated>
<author>
<name>Viresh Kumar</name>
<email>viresh.kumar@linaro.org</email>
</author>
<published>2021-07-27T05:23:48Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=ad93f7b3715449704225feb33d5fbe6507472245'/>
<id>urn:sha1:ad93f7b3715449704225feb33d5fbe6507472245</id>
<content type='text'>
Allow virtio device sub-nodes to be added to the virtio mmio or pci
nodes. The compatible property for virtio device must be of the format
"virtio,device&lt;ID&gt;", where ID is virtio device ID in hexadecimal format.

Signed-off-by: Viresh Kumar &lt;viresh.kumar@linaro.org&gt;
Link: https://lore.kernel.org/r/d8319fd18df7086b12cdcc23193c313893aa071a.1627362340.git.viresh.kumar@linaro.org
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Reviewed-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Reviewed-by: Rob Herring &lt;robh@kernel.org&gt;
</content>
</entry>
<entry>
<title>dt-bindings: virtio: Convert virtio-mmio to DT schema</title>
<updated>2021-06-09T01:02:45Z</updated>
<author>
<name>Rob Herring</name>
<email>robh@kernel.org</email>
</author>
<published>2021-06-07T14:48:11Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=13542a69b918db0118b75d9825bcc775c9c36ed3'/>
<id>urn:sha1:13542a69b918db0118b75d9825bcc775c9c36ed3</id>
<content type='text'>
Convert the virtio-mmio binding to DT schema format.

Cc: "Michael S. Tsirkin" &lt;mst@redhat.com&gt;
Cc: Jason Wang &lt;jasowang@redhat.com&gt;
Cc: Jean-Philippe Brucker &lt;jean-philippe@linaro.org&gt;
Cc: virtualization@lists.linux-foundation.org
Acked-by: Jean-Philippe Brucker &lt;jean-philippe@linaro.org&gt;
Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;
Link: https://lore.kernel.org/r/20210607193928.3092186-1-robh@kernel.org/
</content>
</entry>
<entry>
<title>dt-bindings: virtio: Replace HTTP links with HTTPS ones</title>
<updated>2020-07-21T01:50:05Z</updated>
<author>
<name>Alexander A. Klimov</name>
<email>grandmaster@al2klimov.de</email>
</author>
<published>2020-07-09T06:47:55Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=8f92f6805fdb8166ddd1d41cce2651605481d559'/>
<id>urn:sha1:8f92f6805fdb8166ddd1d41cce2651605481d559</id>
<content type='text'>
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.

Deterministic algorithm:
For each file:
  If not .svg:
    For each line:
      If doesn't contain `\bxmlns\b`:
        For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
	  If neither `\bgnu\.org/license`, nor `\bmozilla\.org/MPL\b`:
            If both the HTTP and HTTPS versions
            return 200 OK and serve the same content:
              Replace HTTP with HTTPS.

Signed-off-by: Alexander A. Klimov &lt;grandmaster@al2klimov.de&gt;
Link: https://lore.kernel.org/r/20200709064755.24051-1-grandmaster@al2klimov.de
Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;
</content>
</entry>
<entry>
<title>dt-bindings: virtio: Add virtio-pci-iommu node</title>
<updated>2019-06-06T21:32:13Z</updated>
<author>
<name>Jean-Philippe Brucker</name>
<email>jean-philippe.brucker@arm.com</email>
</author>
<published>2019-01-15T12:19:54Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=6c9e92ef8bdde13398caae1989b0292524d6475e'/>
<id>urn:sha1:6c9e92ef8bdde13398caae1989b0292524d6475e</id>
<content type='text'>
Some systems implement virtio-iommu as a PCI endpoint. The operating
system needs to discover the relationship between IOMMU and masters long
before the PCI endpoint gets probed. Add a PCI child node to describe the
virtio-iommu device.

The virtio-pci-iommu is conceptually split between a PCI programming
interface and a translation component on the parent bus. The latter
doesn't have a node in the device tree. The virtio-pci-iommu node
describes both, by linking the PCI endpoint to "iommus" property of DMA
master nodes and to "iommu-map" properties of bus nodes.

Reviewed-by: Rob Herring &lt;robh@kernel.org&gt;
Reviewed-by: Eric Auger &lt;eric.auger@redhat.com&gt;
Signed-off-by: Jean-Philippe Brucker &lt;jean-philippe.brucker@arm.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
</content>
</entry>
<entry>
<title>dt-bindings: virtio-mmio: Add IOMMU description</title>
<updated>2019-06-06T21:32:13Z</updated>
<author>
<name>Jean-Philippe Brucker</name>
<email>jean-philippe.brucker@arm.com</email>
</author>
<published>2019-01-15T12:19:53Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=8447d84e35f2c3b2e76f80319d0b547a9521bafa'/>
<id>urn:sha1:8447d84e35f2c3b2e76f80319d0b547a9521bafa</id>
<content type='text'>
The nature of a virtio-mmio node is discovered by the virtio driver at
probe time. However the DMA relation between devices must be described
statically. When a virtio-mmio node is a virtio-iommu device, it needs an
"#iommu-cells" property as specified by bindings/iommu/iommu.txt.

Otherwise, the virtio-mmio device may perform DMA through an IOMMU, which
requires an "iommus" property. Describe these requirements in the
device-tree bindings documentation.

Reviewed-by: Rob Herring &lt;robh@kernel.org&gt;
Reviewed-by: Eric Auger &lt;eric.auger@redhat.com&gt;
Signed-off-by: Jean-Philippe Brucker &lt;jean-philippe.brucker@arm.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
</content>
</entry>
<entry>
<title>virtio: Add platform bus driver for memory mapped virtio device</title>
<updated>2011-11-02T01:11:01Z</updated>
<author>
<name>Pawel Moll</name>
<email>pawel.moll@arm.com</email>
</author>
<published>2011-10-24T13:07:03Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=edfd52e6367270c90f3fd7cc302b375ffa89f91e'/>
<id>urn:sha1:edfd52e6367270c90f3fd7cc302b375ffa89f91e</id>
<content type='text'>
This patch, based on virtio PCI driver, adds support for memory
mapped (platform) virtio device. This should allow environments
like qemu to use virtio-based block &amp; network devices even on
platforms without PCI support.

One can define and register a platform device which resources
will describe memory mapped control registers and "mailbox"
interrupt. Such device can be also instantiated using the Device
Tree node with compatible property equal "virtio,mmio".

Cc: Anthony Liguori &lt;aliguori@us.ibm.com&gt;
Cc: Michael S.Tsirkin &lt;mst@redhat.com&gt;
Signed-off-by: Pawel Moll &lt;pawel.moll@arm.com&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
</feed>
