Skip to contentSkip to conversation

virtio-media: Add device specification

PATCH Superseded Albert Esteve 4 participants 10 messages Mar 4, 2025 – Jul 9, 2025

v8 of 9 Superseded Latest is v9 →

lore
Share & tools
lore
#0 lore raw

v8 cover virtio-media: Add device specification

New attempt of including virtio-media
device specification.

v7->v8:
- Merged DQBUF and DQEVENT into the same
item for unsupported ioctls
- Rewrote/clarified a couple paragraphs
based on previous version reviews.

v6->v7:
- All uses of must referencing
driver or device, put into a
normative section accordingly.
- Switched 'can' with 'may' in
a couple of appearances.
- Clarified UUID memory layout
for VIRTIO_OBJECT memory type.
- Fixed a typo in the driver
normative document.

v5->v6:
- A couple minor typos.
- Change driver-writable for
device-readable to avoid
confusion.

Virtio-media came from a discussion on virtio-dev mailing list, which lead to Alex Courbot presenting virtio-v4l2[1] specification as an alternative to virtio-video.

Later, virtio-v4l2 was renamed to virtio-media[2] and published at:

https://github.com/chromeos/virtio-media

The repository above includes a virtio-media driver able to pass v4l2-compliance when proxying the vivid/vicodec virtual devices or an actual UVC camera using the V4L2 vhost device (available in the repository). It also includes a FFmpeg-based video encoder device. Steps to reproduce are also detailed[3].

Recently, virtio-media has landed in AOSP[4]. Also the driver patch has been sent to the kernel, currently in its v2 [5].

Furthermore, virtio-media got a proposal to reserve device ID 48, which was finally approved for inclusion in v1.4.

There is some overlap with virtio-video in regards to which devices it can handle. However, they take different approaches, potentially making them the preferable choice for different scenarios. Furthermore, virtio-media has matured since it was first presented, and there are public efforts to have upstream driver and devices.

But mainly, given that virtio-media will be the virtualization solution for media devices for ChromeOS, Android, and possibly others, I think is important that it gets standardized and included in the specification, despite the aforementioned overlap.

Full PDF: https://drive.google.com/file/d/1sDZXWVlvPbHKKguhekCXMzkpNZZ0g3hV/view?usp=sharing
PDF with the media section only: https://drive.google.com/file/d/1JjOIzecnkFFlpFBRjPQEUyAOD3BDHAdw/view?usp=sharing

[1] https://mail.google.com/mail/u/0?ui=2&ik=73ebd65ebd&attid=0.1&permmsgid=msg-f:1767388565327924962&th=1887068940754ee2&view=att&disp=inline&realattid=f_libalimc0
[2] https://www.mail-archive.com/[email protected]/msg12665.html
[3] https://github.com/chromeos/virtio-media/blob/main/TRY_IT_OUT.md
[4] https://cs.android.com/android/platform/superproject/main/+/main:external/virtio-media/
[5] https://lore.kernel.org/lkml/[email protected]/T/

Albert Esteve (1):
virtio-media: Add virtio media device specification

 conformance.tex                           |  12 +-
 content.tex                               |   1 +
 device-types/media/description.tex        | 639 ++++++++++++++++++++++
 device-types/media/device-conformance.tex |  15 +
 device-types/media/driver-conformance.tex |  11 +
 5 files changed, 674 insertions(+), 4 deletions(-)
 create mode 100644 device-types/media/description.tex
 create mode 100644 device-types/media/device-conformance.tex
 create mode 100644 device-types/media/driver-conformance.tex
Signature · 1 line
2.48.1
#1 lore raw

PATCH v8 1/1 virtio-media: Add virtio media device specification

Virtio-media is an encapsulation of the V4L2 UAPI into virtio, able to virtualize any video device supported by V4L2.

Note that virtio-media does not require the use of a V4L2 device driver on the host or guest side - V4L2 is only used as a host-guest protocol, and both sides are free to convert it from/to any model that they wish to use.

---
 conformance.tex                           |  12 +-
 content.tex                               |   1 +
 device-types/media/description.tex        | 639 ++++++++++++++++++++++
 device-types/media/device-conformance.tex |  15 +
 device-types/media/driver-conformance.tex |  11 +
 5 files changed, 674 insertions(+), 4 deletions(-)
 create mode 100644 device-types/media/description.tex
 create mode 100644 device-types/media/device-conformance.tex
 create mode 100644 device-types/media/driver-conformance.tex
conformance.tex +8 -4
index dc00e84..2564034 100644
@@ -32,8 +32,9 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \ref{sec:Conformance / Driver Conformance / Memory Driver Conformance},
 \ref{sec:Conformance / Driver Conformance / I2C Adapter Driver Conformance},
 \ref{sec:Conformance / Driver Conformance / SCMI Driver Conformance},
-\ref{sec:Conformance / Driver Conformance / GPIO Driver Conformance} or
-\ref{sec:Conformance / Driver Conformance / PMEM Driver Conformance}.
+\ref{sec:Conformance / Driver Conformance / GPIO Driver Conformance},
+\ref{sec:Conformance / Driver Conformance / PMEM Driver Conformance} or
+\ref{sec:Conformance / Driver Conformance / Media Driver Conformance}.
 
     \item Clause \ref{sec:Conformance / Legacy Interface: Transitional Device and Transitional Driver Conformance}.
   \end{itemize}
@@ -59,8 +60,9 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \ref{sec:Conformance / Device Conformance / Memory Device Conformance},
 \ref{sec:Conformance / Device Conformance / I2C Adapter Device Conformance},
 \ref{sec:Conformance / Device Conformance / SCMI Device Conformance},
-\ref{sec:Conformance / Device Conformance / GPIO Device Conformance} or
-\ref{sec:Conformance / Device Conformance / PMEM Device Conformance}.
+\ref{sec:Conformance / Device Conformance / GPIO Device Conformance},
+\ref{sec:Conformance / Device Conformance / PMEM Device Conformance} or
+\ref{sec:Conformance / Device Conformance / Media Device Conformance}.
 
     \item Clause \ref{sec:Conformance / Legacy Interface: Transitional Device and Transitional Driver Conformance}.
   \end{itemize}
@@ -152,6 +154,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \input{device-types/scmi/driver-conformance.tex}
 \input{device-types/gpio/driver-conformance.tex}
 \input{device-types/pmem/driver-conformance.tex}
+\input{device-types/media/driver-conformance.tex}
 
 \conformance{\section}{Device Conformance}\label{sec:Conformance / Device Conformance}
 
@@ -238,6 +241,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \input{device-types/scmi/device-conformance.tex}
 \input{device-types/gpio/device-conformance.tex}
 \input{device-types/pmem/device-conformance.tex}
+\input{device-types/media/device-conformance.tex}
 
 \conformance{\section}{Legacy Interface: Transitional Device and Transitional Driver Conformance}\label{sec:Conformance / Legacy Interface: Transitional Device and Transitional Driver Conformance}
 A conformant implementation MUST be either transitional or
content.tex +1 -0
index 0a62dce..59925ae 100644
@@ -767,6 +767,7 @@ \chapter{Device Types}\label{sec:Device Types}
 \input{device-types/scmi/description.tex}
 \input{device-types/gpio/description.tex}
 \input{device-types/pmem/description.tex}
+\input{device-types/media/description.tex}
 
 \chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}
 
device-types/media/description.tex new file +639 -0

639 lines not on this page · raw message

device-types/media/device-conformance.tex new file +15 -0
new file mode 100644
index 0000000..99112ff
@@ -0,0 +1,15 @@
+\conformance{\subsection}{Media Device Conformance}\label{sec:Conformance / Device Conformance / Media Device Conformance}
+
+A Media device MUST conform to the following normative statements:
+
+\begin{itemize}
+\item \ref{devicenormative:Device Types / Media Device / Device Operation / Open device}
+\item \ref{devicenormative:Device Types / Media Device / Device Operation / V4L2 ioctls}
+\item \ref{devicenormative:Device Types / Media Device / Device Operation / Pointers in V4l2 ioctls}
+\item \ref{devicenormative:Device Types / Media Device / Device Operation / Unsupported ioctls}
+\item \ref{devicenormative:Device Types / Media Device / Device Operation / Mapping a MMAP buffer}
+\item \ref{devicenormative:Device Types / Media Device / Device Operation / Unmapping a MMAP buffer}
+\item \ref{devicenormative:Device Types / Media Device / Device Operation / Shared Pages}
+\item \ref{devicenormative:Device Types / Media Device / Device Operation / Virtio Object}
+\item \ref{devicenormative:Device Types / Media Device / Device Operation / Device-side error}
+\end{itemize}
device-types/media/driver-conformance.tex new file +11 -0
new file mode 100644
index 0000000..eb380ad
@@ -0,0 +1,11 @@
+\conformance{\subsection}{Media Driver Conformance}\label{sec:Conformance / Driver Conformance / Media Driver Conformance}
+
+A Media driver MUST conform to the following normative statements:
+
+\begin{itemize}
+\item \ref{drivernormative:Device Types / Media Device / Device Operation / Command Virtqueue}
+\item \ref{drivernormative:Device Types / Media Device / Device Operation / Close device}
+\item \ref{drivernormative:Device Types / Media Device / Device Operation / V4L2 ioctls}
+\item \ref{drivernormative:Device Types / Media Device / Device Operation / Device-side error}
+\item \ref{drivernormative:Device Types / Media Device / Device Operation / Dequeue buffer}
+\end{itemize}
Signature · 1 line
2.48.1
Reviewed-by on v8 1/1
#2 lore raw

Re: [PATCH v8 1/1] virtio-media: Add virtio media device specification

Hello Albert,

Quoted 9 lines · Albert Esteve

Virtio-media is an encapsulation of the V4L2 UAPI into virtio, able to virtualize any video device supported by V4L2.

Note that virtio-media does not require the use of a V4L2 device driver on the host or guest side - V4L2 is only used as a host-guest protocol, and both sides are free to convert it from/to any model that they wish to use.

Thank you for your patience with this. I have done a final pass on this version and it looks great to me!

#3 lore raw

Re: [PATCH v8 1/1] virtio-media: Add virtio media device specification

Quoted 14 lines · Alexandre Courbot

Hello Albert,

Quoted 9 lines · Albert Esteve

Virtio-media is an encapsulation of the V4L2 UAPI into virtio, able to virtualize any video device supported by V4L2.

Note that virtio-media does not require the use of a V4L2 device driver on the host or guest side - V4L2 is only used as a host-guest protocol, and both sides are free to convert it from/to any model that they wish to use.

Quoted 5 lines

Thank you for your patience with this. I have done a final pass on this version and it looks great to me!

Thanks! Could we please open a voting ballot for these changes?

#4 lore raw

Re: [PATCH v8 1/1] virtio-media: Add virtio media device specification

Quoted 18 lines · Albert Esteve
Quoted 17 lines · Alexandre Courbot

Hello Albert,

Quoted 9 lines · Albert Esteve

Virtio-media is an encapsulation of the V4L2 UAPI into virtio, able to virtualize any video device supported by V4L2.

Note that virtio-media does not require the use of a V4L2 device driver on the host or guest side - V4L2 is only used as a host-guest protocol, and both sides are free to convert it from/to any model that they wish to use.

Thank you for your patience with this. I have done a final pass on this version and it looks great to me!

Quoted 6 lines
Quoted 2 lines

Thanks! Could we please open a voting ballot for these changes?

What was the result of the ballot?

Signature · 2 lines
Alex Bennée
Virtualisation Tech Lead @ Linaro
#5 lore raw

Re: [PATCH v8 1/1] virtio-media: Add virtio media device specification

Quoted 21 lines · Alex Bennée
Quoted 18 lines · Albert Esteve
Quoted 17 lines · Alexandre Courbot

Hello Albert,

Quoted 9 lines · Albert Esteve

Virtio-media is an encapsulation of the V4L2 UAPI into virtio, able to virtualize any video device supported by V4L2.

Note that virtio-media does not require the use of a V4L2 device driver on the host or guest side - V4L2 is only used as a host-guest protocol, and both sides are free to convert it from/to any model that they wish to use.

Thank you for your patience with this. I have done a final pass on this version and it looks great to me!

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

Thanks! Could we please open a voting ballot for these changes?

What was the result of the ballot?

AFAIU the ballot was approved. There were conflicts with the virtio-1.4 branch, which may have delayed the integration. I've just sent a new version of the patch rebased to virtio-1.4 to try to ease the process.

Quoted 5 lines

--
Alex Bennée
Virtualisation Tech Lead @ Linaro

#6 lore raw

Re: [PATCH v8 1/1] virtio-media: Add virtio media device specification

Quoted 28 lines · Albert Esteve
Quoted 26 lines · Alex Bennée
Quoted 23 lines · Albert Esteve
Quoted 14 lines · Alexandre Courbot

Hello Albert,

Quoted 9 lines · Albert Esteve

Virtio-media is an encapsulation of the V4L2 UAPI into virtio, able to virtualize any video device supported by V4L2.

Note that virtio-media does not require the use of a V4L2 device driver on the host or guest side - V4L2 is only used as a host-guest protocol, and both sides are free to convert it from/to any model that they wish to use.

Quoted 5 lines

Thank you for your patience with this. I have done a final pass on this version and it looks great to me!

Thanks! Could we please open a voting ballot for these changes?

Quoted 8 lines
Quoted 3 lines
Quoted 1 line

What was the result of the ballot?

AFAIU the ballot was approved. There were conflicts with the virtio-1.4 branch, which may have delayed the integration. I've just sent a new version of the patch rebased to virtio-1.4 to try to ease the process.

Adding the diff here on the v8 instead, to avoid having to vote again on a new patch version.
The diff should allow applying the original v8 patch cleanly to virtio-1.4. Let me know if this is enough.

----

content.tex +0 -0
index 59925ae..56b2cb1 100644
@@ -100,7 +100,7 @@ \section{Feature Bits}\label{sec:Basic Facilities

of a Virtio Device / Feature B
\item[0 to 23, and 50 to 127] Feature bits for the specific device type

\item[24 to 41] Feature bits reserved for extensions to the queue and
- feature negotiation mechanisms
+ feature negotiation mechanisms, see \ref{sec:Reserved Feature Bits}

\item[42 to 49, and 128 and above] Feature bits reserved for future extensions. \end{description}
@@ -493,7 +493,7 @@ \section{Driver Notifications} \label{sec:Basic Facilities of a Virtio Device /
\section{Exporting Objects}\label{sec:Basic Facilities of a Virtio
Device / Exporting Objects}

When an object created by one virtio device needs to be
-shared with a seperate virtio device, the first device can +shared with a separate virtio device, the first device can
export the object by generating a UUID which can then be passed to the second device to identify the object.

@@ -503,11 +503,12 @@ \section{Exporting Objects}\label{sec:Basic Facilities of a Virtio Device / Expo
UUIDs as specified by \hyperref[intro:rfc4122]{[RFC4122]}.

\input{admin.tex}
+\input{device-parts.tex}

\chapter{General Initialization And Device
Operation}\label{sec:General Initialization And Device Operation}

We start with an overview of device initialization, then expand on the
-details of the device and how each step is preformed. This section +details of the device and how each step is performed. This section
is best read along with the bus-specific section which describes how to communicate with the specific device.

@@ -649,7 +650,7 @@ \chapter{Device Types}\label{sec:Device Types}

Discovering what devices are available and their type is bus-dependent.

-\begin{tabular} { |l|c| }
+\begin{longtable} { |l|c| }

\hline
Device ID & Virtio Device \\
\hline \hline
@@ -737,9 +738,17 @@ \chapter{Device Types}\label{sec:Device Types}
\hline
44 & ISM device \\
\hline

-45         &   SPI master \\
+45         &   SPI controller \\

\hline
-\end{tabular}
+46 & TEE device \\
+\hline
+47 & CPU balloon device \\
+\hline
+48 & Media device \\
+\hline
+49 & USB controller \\
+\hline
+\end{longtable}

Some of the devices above are unspecified by this document, because they are seen as immature or especially niche. Be warned
@@ -767,6 +776,8 @@ \chapter{Device Types}\label{sec:Device Types}
\input{device-types/scmi/description.tex} \input{device-types/gpio/description.tex} \input{device-types/pmem/description.tex}
+\input{device-types/can/description.tex} +\input{device-types/spi/description.tex}
\input{device-types/media/description.tex}

\chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}

conformance.tex +0 -0
index 2564034..0856353 100644
@@ -33,6 +33,9 @@ \section{Conformance Targets}\label{sec:Conformance

/ Conformance Targets}
\ref{sec:Conformance / Driver Conformance / I2C Adapter Driver Conformance}, \ref{sec:Conformance / Driver Conformance / SCMI Driver Conformance}, \ref{sec:Conformance / Driver Conformance / GPIO Driver Conformance},
+\ref{sec:Conformance / Driver Conformance / PMEM Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / CAN Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / SPI Controller Driver Conformance},
\ref{sec:Conformance / Driver Conformance / PMEM Driver Conformance} or \ref{sec:Conformance / Driver Conformance / Media Driver Conformance}.

@@ -61,7 +64,10 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\ref{sec:Conformance / Device Conformance / I2C Adapter Device Conformance}, \ref{sec:Conformance / Device Conformance / SCMI Device Conformance}, \ref{sec:Conformance / Device Conformance / GPIO Device Conformance},
-\ref{sec:Conformance / Device Conformance / PMEM Device Conformance} or +\ref{sec:Conformance / Device Conformance / PMEM Device Conformance}, +\ref{sec:Conformance / Device Conformance / CAN Device Conformance}, +\ref{sec:Conformance / Device Conformance / SPI Controller Device Conformance}, +\ref{sec:Conformance / Device Conformance / PMEM Device Conformance},
\ref{sec:Conformance / Device Conformance / Media Device Conformance}.

\item Clause \ref{sec:Conformance / Legacy Interface:
Transitional Device and Transitional Driver Conformance}.
@@ -78,6 +84,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Reset} \item \ref{drivernormative:Basic Facilities of a Virtio Device /
Device Configuration Space}
\item \ref{drivernormative:Basic Facilities of a Virtio Device / Virtqueues}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device / Virtqueues / Virtqueue Reset / Virtqueue Reset}
\item \ref{drivernormative:Basic Facilities of a Virtio Device /
Message Framing}
\item \ref{drivernormative:Basic Facilities of a Virtio Device /
Virtqueues / The Virtqueue Descriptor Table}
\item \ref{drivernormative:Basic Facilities of a Virtio Device /
Virtqueues / The Virtqueue Descriptor Table / Indirect Descriptors} @@ -96,6 +103,9 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\item \ref{drivernormative:General Initialization And Device
Operation / Device Initialization}
\item \ref{drivernormative:General Initialization And Device
Operation / Device Cleanup}
\item \ref{drivernormative:Reserved Feature Bits}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device / Device groups / Group administration commands / Device and driver capabilities}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device / Device groups / Group administration commands / Device resource objects}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device / Device groups / Group administration commands / Device parts}
\end{itemize}

\conformance{\subsection}{PCI Driver
Conformance}\label{sec:Conformance / Driver Conformance / PCI Driver Conformance}
@@ -154,6 +164,8 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\input{device-types/scmi/driver-conformance.tex} \input{device-types/gpio/driver-conformance.tex} \input{device-types/pmem/driver-conformance.tex}
+\input{device-types/can/driver-conformance.tex} +\input{device-types/spi/driver-conformance.tex}
\input{device-types/media/driver-conformance.tex}

\conformance{\section}{Device Conformance}\label{sec:Conformance /
Device Conformance}
@@ -165,6 +177,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\item \ref{devicenormative:Basic Facilities of a Virtio Device / Feature Bits} \item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Reset} \item \ref{devicenormative:Basic Facilities of a Virtio Device /
Device Configuration Space}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device / Virtqueues / Virtqueue Reset / Virtqueue Reset}
\item \ref{devicenormative:Basic Facilities of a Virtio Device /
Message Framing}
\item \ref{devicenormative:Basic Facilities of a Virtio Device /
Virtqueues / The Virtqueue Descriptor Table}
\item \ref{devicenormative:Basic Facilities of a Virtio Device /
Virtqueues / The Virtqueue Descriptor Table / Indirect Descriptors} @@ -176,6 +189,9 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\item \ref{devicenormative:Basic Facilities of a Virtio Device /
Packed Virtqueues / Scatter-Gather Support}
\item \ref{devicenormative:Basic Facilities of a Virtio Device /
Shared Memory Regions}
\item \ref{devicenormative:Reserved Feature Bits}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device / Device groups / Group administration commands / Device and driver capabilities}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device / Device groups / Group administration commands / Device resource objects}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device / Device groups / Group administration commands / Device parts}
\end{itemize}

\conformance{\subsection}{PCI Device
Conformance}\label{sec:Conformance / Device Conformance / PCI Device Conformance}
@@ -241,6 +257,8 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\input{device-types/scmi/device-conformance.tex} \input{device-types/gpio/device-conformance.tex} \input{device-types/pmem/device-conformance.tex}
+\input{device-types/can/device-conformance.tex} +\input{device-types/spi/device-conformance.tex}
\input{device-types/media/device-conformance.tex}

\conformance{\section}{Legacy Interface: Transitional Device and
Transitional Driver Conformance}\label{sec:Conformance / Legacy
Interface: Transitional Device and Transitional Driver Conformance}

Quoted 6 lines
Quoted 6 lines

--
Alex Bennée
Virtualisation Tech Lead @ Linaro

#7 lore raw

Re: [PATCH v8 1/1] virtio-media: Add virtio media device specification

Quoted 242 lines · Albert Esteve
Quoted 28 lines · Albert Esteve
Quoted 26 lines · Alex Bennée
Quoted 23 lines · Albert Esteve
Quoted 14 lines · Alexandre Courbot

Hello Albert,

Quoted 9 lines · Albert Esteve

Virtio-media is an encapsulation of the V4L2 UAPI into virtio, able to virtualize any video device supported by V4L2.

Note that virtio-media does not require the use of a V4L2 device driver on the host or guest side - V4L2 is only used as a host-guest protocol, and both sides are free to convert it from/to any model that they wish to use.

Quoted 5 lines

Thank you for your patience with this. I have done a final pass on this version and it looks great to me!

Thanks! Could we please open a voting ballot for these changes?

Quoted 8 lines
Quoted 3 lines
Quoted 1 line

What was the result of the ballot?

AFAIU the ballot was approved. There were conflicts with the virtio-1.4 branch, which may have delayed the integration. I've just sent a new version of the patch rebased to virtio-1.4 to try to ease the process.

Adding the diff here on the v8 instead, to avoid having to vote again on a new patch version.
The diff should allow applying the original v8 patch cleanly to virtio-1.4. Let me know if this is enough.

----

content.tex +0 -0
index 59925ae..56b2cb1 100644
@@ -100,7 +100,7 @@ \section{Feature Bits}\label{sec:Basic Facilities

of a Virtio Device / Feature B
\item[0 to 23, and 50 to 127] Feature bits for the specific device type

\item[24 to 41] Feature bits reserved for extensions to the queue and

content.tex +1 -1
-  feature negotiation mechanisms
+  feature negotiation mechanisms, see \ref{sec:Reserved Feature Bits}
 
 \item[42 to 49, and 128 and above] Feature bits reserved for future extensions.
 \end{description}
@@ -493,7 +493,7 @@ \section{Driver Notifications} \label{sec:Basic

Facilities of a Virtio Device /
\section{Exporting Objects}\label{sec:Basic Facilities of a Virtio
Device / Exporting Objects}

When an object created by one virtio device needs to be

content.tex +1 -1
-shared with a seperate virtio device, the first device can
+shared with a separate virtio device, the first device can
 export the object by generating a UUID which can then
 be passed to the second device to identify the object.
@@ -503,11 +503,12 @@ \section{Exporting Objects}\label{sec:Basic

Facilities of a Virtio Device / Expo
UUIDs as specified by \hyperref[intro:rfc4122]{[RFC4122]}.

\input{admin.tex}
+\input{device-parts.tex}

\chapter{General Initialization And Device
Operation}\label{sec:General Initialization And Device Operation}

We start with an overview of device initialization, then expand on the

content.tex +14 -4
-details of the device and how each step is preformed.  This section
+details of the device and how each step is performed.  This section
 is best read along with the bus-specific section which describes
 how to communicate with the specific device.
@@ -649,7 +650,7 @@ \chapter{Device Types}\label{sec:Device Types}
 
 Discovering what devices are available and their type is bus-dependent.
 
-\begin{tabular} { |l|c| }
+\begin{longtable} { |l|c| }
 \hline
 Device ID  &  Virtio Device    \\
 \hline \hline
@@ -737,9 +738,17 @@ \chapter{Device Types}\label{sec:Device Types}
 \hline
 44         &   ISM device \\
 \hline
-45         &   SPI master \\
+45         &   SPI controller \\
 \hline
-\end{tabular}
+46         &   TEE device \\
+\hline
+47         &   CPU balloon device \\
+\hline
+48         &   Media device \\
+\hline
+49         &   USB controller \\
+\hline
+\end{longtable}
 
 Some of the devices above are unspecified by this document,
 because they are seen as immature or especially niche.  Be warned
@@ -767,6 +776,8 @@ \chapter{Device Types}\label{sec:Device Types}
 \input{device-types/scmi/description.tex}
 \input{device-types/gpio/description.tex}
 \input{device-types/pmem/description.tex}
+\input{device-types/can/description.tex}
+\input{device-types/spi/description.tex}
 \input{device-types/media/description.tex}
 
 \chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}
conformance.tex +7 -1
index 2564034..0856353 100644
@@ -33,6 +33,9 @@ \section{Conformance Targets}\label{sec:Conformance
 / Conformance Targets}
 \ref{sec:Conformance / Driver Conformance / I2C Adapter Driver Conformance},
 \ref{sec:Conformance / Driver Conformance / SCMI Driver Conformance},
 \ref{sec:Conformance / Driver Conformance / GPIO Driver Conformance},
+\ref{sec:Conformance / Driver Conformance / PMEM Driver Conformance},
+\ref{sec:Conformance / Driver Conformance / CAN Driver Conformance},
+\ref{sec:Conformance / Driver Conformance / SPI Controller Driver Conformance},
 \ref{sec:Conformance / Driver Conformance / PMEM Driver Conformance} or
 \ref{sec:Conformance / Driver Conformance / Media Driver Conformance}.
@@ -61,7 +64,10 @@ \section{Conformance Targets}\label{sec:Conformance
 / Conformance Targets}
 \ref{sec:Conformance / Device Conformance / I2C Adapter Device Conformance},
 \ref{sec:Conformance / Device Conformance / SCMI Device Conformance},
 \ref{sec:Conformance / Device Conformance / GPIO Device Conformance},
-\ref{sec:Conformance / Device Conformance / PMEM Device Conformance} or
+\ref{sec:Conformance / Device Conformance / PMEM Device Conformance},
+\ref{sec:Conformance / Device Conformance / CAN Device Conformance},
+\ref{sec:Conformance / Device Conformance / SPI Controller Device Conformance},
+\ref{sec:Conformance / Device Conformance / PMEM Device Conformance},
 \ref{sec:Conformance / Device Conformance / Media Device Conformance}.
 

\item Clause \ref{sec:Conformance / Legacy Interface:
Transitional Device and Transitional Driver Conformance}.

conformance.tex +1 -0
@@ -78,6 +84,7 @@ \section{Conformance Targets}\label{sec:Conformance
 / Conformance Targets}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Reset}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device /
 Device Configuration Space}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Virtqueues}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device /
 Virtqueues / Virtqueue Reset / Virtqueue Reset}

\item \ref{drivernormative:Basic Facilities of a Virtio Device /
Message Framing}
\item \ref{drivernormative:Basic Facilities of a Virtio Device /
Virtqueues / The Virtqueue Descriptor Table}
\item \ref{drivernormative:Basic Facilities of a Virtio Device /
Virtqueues / The Virtqueue Descriptor Table / Indirect Descriptors}

conformance.tex +1 -0
@@ -96,6 +103,9 @@ \section{Conformance Targets}\label{sec:Conformance
 / Conformance Targets}
 \item \ref{drivernormative:General Initialization And Device
 Operation / Device Initialization}
 \item \ref{drivernormative:General Initialization And Device
 Operation / Device Cleanup}
 \item \ref{drivernormative:Reserved Feature Bits}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device /

Device groups / Group administration commands / Device and driver capabilities}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device / Device groups / Group administration commands / Device resource objects}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device / Device groups / Group administration commands / Device parts}
\end{itemize}

\conformance{\subsection}{PCI Driver
Conformance}\label{sec:Conformance / Driver Conformance / PCI Driver Conformance}

conformance.tex +2 -0
@@ -154,6 +164,8 @@ \section{Conformance
 Targets}\label{sec:Conformance / Conformance Targets}
 \input{device-types/scmi/driver-conformance.tex}
 \input{device-types/gpio/driver-conformance.tex}
 \input{device-types/pmem/driver-conformance.tex}
+\input{device-types/can/driver-conformance.tex}
+\input{device-types/spi/driver-conformance.tex}
 \input{device-types/media/driver-conformance.tex}
 

\conformance{\section}{Device Conformance}\label{sec:Conformance /
Device Conformance}

conformance.tex +1 -0
@@ -165,6 +177,7 @@ \section{Conformance
 Targets}\label{sec:Conformance / Conformance Targets}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Feature Bits}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Reset}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device /
 Device Configuration Space}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device /
 Virtqueues / Virtqueue Reset / Virtqueue Reset}

\item \ref{devicenormative:Basic Facilities of a Virtio Device /
Message Framing}
\item \ref{devicenormative:Basic Facilities of a Virtio Device /
Virtqueues / The Virtqueue Descriptor Table}
\item \ref{devicenormative:Basic Facilities of a Virtio Device /
Virtqueues / The Virtqueue Descriptor Table / Indirect Descriptors}

conformance.tex +1 -0
@@ -176,6 +189,9 @@ \section{Conformance
 Targets}\label{sec:Conformance / Conformance Targets}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device /
 Packed Virtqueues / Scatter-Gather Support}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device /
 Shared Memory Regions}
 \item \ref{devicenormative:Reserved Feature Bits}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device /

Device groups / Group administration commands / Device and driver capabilities}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device / Device groups / Group administration commands / Device resource objects}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device / Device groups / Group administration commands / Device parts}
\end{itemize}

\conformance{\subsection}{PCI Device
Conformance}\label{sec:Conformance / Device Conformance / PCI Device Conformance}

conformance.tex +2 -0
@@ -241,6 +257,8 @@ \section{Conformance
 Targets}\label{sec:Conformance / Conformance Targets}
 \input{device-types/scmi/device-conformance.tex}
 \input{device-types/gpio/device-conformance.tex}
 \input{device-types/pmem/device-conformance.tex}
+\input{device-types/can/device-conformance.tex}
+\input{device-types/spi/device-conformance.tex}
 \input{device-types/media/device-conformance.tex}
 
Quoted 4 lines

\conformance{\section}{Legacy Interface: Transitional Device and
Transitional Driver Conformance}\label{sec:Conformance / Legacy
Interface: Transitional Device and Transitional Driver Conformance}

A cleaner attempt, noticed a duplication of one listed item. Also removed the parts of the diff that caused no collision beforehand.

---

content.tex +0 -0
index 59925ae..56b2cb1 100644

+\end{longtable}

Some of the devices above are unspecified by this document, because they are seen as immature or especially niche. Be warned
@@ -767,6 +776,8 @@ \chapter{Device Types}\label{sec:Device Types}
\input{device-types/scmi/description.tex} \input{device-types/gpio/description.tex} \input{device-types/pmem/description.tex}
+\input{device-types/can/description.tex} +\input{device-types/spi/description.tex}
\input{device-types/media/description.tex}

\chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}

conformance.tex +0 -0
index 2564034..85a227f 100644
@@ -33,7 +33,9 @@ \section{Conformance Targets}\label{sec:Conformance

/ Conformance Targets}
\ref{sec:Conformance / Driver Conformance / I2C Adapter Driver Conformance}, \ref{sec:Conformance / Driver Conformance / SCMI Driver Conformance}, \ref{sec:Conformance / Driver Conformance / GPIO Driver Conformance},
-\ref{sec:Conformance / Driver Conformance / PMEM Driver Conformance} or +\ref{sec:Conformance / Driver Conformance / PMEM Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / CAN Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / SPI Controller Driver Conformance} or
\ref{sec:Conformance / Driver Conformance / Media Driver Conformance}.

\item Clause \ref{sec:Conformance / Legacy Interface:
Transitional Device and Transitional Driver Conformance}.
@@ -61,7 +63,9 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\ref{sec:Conformance / Device Conformance / I2C Adapter Device Conformance}, \ref{sec:Conformance / Device Conformance / SCMI Device Conformance}, \ref{sec:Conformance / Device Conformance / GPIO Device Conformance},
-\ref{sec:Conformance / Device Conformance / PMEM Device Conformance} or +\ref{sec:Conformance / Device Conformance / PMEM Device Conformance}, +\ref{sec:Conformance / Device Conformance / CAN Device Conformance}, +\ref{sec:Conformance / Device Conformance / SPI Controller Device Conformance} or
\ref{sec:Conformance / Device Conformance / Media Device Conformance}.

\item Clause \ref{sec:Conformance / Legacy Interface:
Transitional Device and Transitional Driver Conformance}. @@ -154,6 +162,8 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\input{device-types/scmi/driver-conformance.tex} \input{device-types/gpio/driver-conformance.tex} \input{device-types/pmem/driver-conformance.tex}
+\input{device-types/can/driver-conformance.tex} +\input{device-types/spi/driver-conformance.tex}
\input{device-types/media/driver-conformance.tex}

\conformance{\section}{Device Conformance}\label{sec:Conformance /
Device Conformance}
@@ -241,6 +255,8 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\input{device-types/scmi/device-conformance.tex} \input{device-types/gpio/device-conformance.tex} \input{device-types/pmem/device-conformance.tex}
+\input{device-types/can/device-conformance.tex} +\input{device-types/spi/device-conformance.tex}
\input{device-types/media/device-conformance.tex}

\conformance{\section}{Legacy Interface: Transitional Device and
Transitional Driver Conformance}\label{sec:Conformance / Legacy
Interface: Transitional Device and Transitional Driver Conformance}

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

--
Alex Bennée
Virtualisation Tech Lead @ Linaro

#8 lore raw

RE: [PATCH v8 1/1] virtio-media: Add virtio media device specification

Quoted 4 lines

From: Albert Esteve <[email protected]>
Sent: 09 July 2025 05:48 PM

It was simple editorial conflict due to rebase. I merged the change.
Please check the 1.4 branch if everything is right.

#9 lore raw

Re: [PATCH v8 1/1] virtio-media: Add virtio media device specification

Quoted 8 lines · Parav Pandit
Quoted 5 lines

From: Albert Esteve <[email protected]>
Sent: 09 July 2025 05:48 PM

It was simple editorial conflict due to rebase. I merged the change.
Please check the 1.4 branch if everything is right.

Everything looks good to me. Thank you!