[PATCH v3] content: Reserve ID for media device

[PATCH v3] content: Reserve ID for media device

[Albert Esteve]

Reserve device ID 49 for media device.
Compatible with video encoder, video decoder,
and capture devices.

Signed-off-by: Albert Esteve <aesteve@redhat.com>
---
 content.tex | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content.tex b/content.tex
index 0a62dce..6d6b3d8 100644
--- a/content.tex
+++ b/content.tex
@@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
 \hline
 45         &   SPI master \\
 \hline
+49         &   Media device \\
+\hline
 \end{tabular}
 
 Some of the devices above are unspecified by this document,
-- 
2.45.2

Re: [PATCH v3] content: Reserve ID for media device

[Albert Esteve]

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve <aesteve@redhat.com> wrote:

> Reserve device ID 49 for media device.
> Compatible with video encoder, video decoder,
> and capture devices.
>
> Signed-off-by: Albert Esteve <aesteve@redhat.com>
> ---
>  content.tex | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/content.tex b/content.tex
> index 0a62dce..6d6b3d8 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
>  \hline
>  45         &   SPI master \\
>  \hline
> +49         &   Media device \\
> +\hline
>  \end{tabular}
>
>  Some of the devices above are unspecified by this document,
> --
> 2.45.2
>
>
Dear TC,

It has been a while since I posted and there has been no
comments/objections.
I would like to start a vote for issue #202.

 Fixes: https://github.com/oasis-tcs/virtio-spec/issues/202

Thanks!

[-- Attachment #2: Type: text/html, Size: 1570 bytes --]

RE: [PATCH v3] content: Reserve ID for media device

[Parav Pandit]

Hi Albert,

From: Albert Esteve <aesteve@redhat.com> 
Sent: Wednesday, September 25, 2024 12:20 PM


On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve <mailto:aesteve@redhat.com> wrote:
Reserve device ID 49 for media device.
Compatible with video encoder, video decoder,
and capture devices.

Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
---
 content.tex | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content.tex b/content.tex
index 0a62dce..6d6b3d8 100644
--- a/content.tex
+++ b/content.tex
@@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
 \hline
 45         &   SPI master \\
 \hline
+49         &   Media device \\
+\hline
 \end{tabular}

The id 48 request was made several months ago in May-24 for usb, no further interest has been shown on it.
Better to avoid holes in the device id assignment.
So id 48 would be better to use for media that has interest.
Added virtio-usb proposer to thread to see if it is still interesting, in that case 49 seems good here.

Given the voting has started, I am not sure if the real id value matters as long as one of the unique id is reserved.

And do not prefer to restart the voting for such a small change either on my late observation of this hole.

I think when the maintainer merges the proposed patch to assign id 48, should be fine.

Michael,
Are you ok this way? Or you have better suggestion?

Aishwarya,
Is virtio-usb still interesting? If so, can you please request for the vote? So that we avoid the hole in device id assignment.

RE: [PATCH v3] content: Reserve ID for media device

[Parav Pandit]

> From: Parav Pandit <parav@nvidia.com>
> Sent: Tuesday, October 1, 2024 1:35 PM
> To: Albert Esteve <aesteve@redhat.com>; virtio-comment@lists.linux.dev;
> aiswarya.cyriac@opensynergy.com
> Cc: acourbot@chromium.org
> Subject: RE: [PATCH v3] content: Reserve ID for media device
> 
> Hi Albert,
> 
> From: Albert Esteve <aesteve@redhat.com>
> Sent: Wednesday, September 25, 2024 12:20 PM
> 
> 
> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve <mailto:aesteve@redhat.com>
> wrote:
> Reserve device ID 49 for media device.
> Compatible with video encoder, video decoder,
> and capture devices.
> 
> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
> ---
>  content.tex | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/content.tex b/content.tex
> index 0a62dce..6d6b3d8 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
>  \hline
>  45         &   SPI master \\
>  \hline
> +49         &   Media device \\
> +\hline
>  \end{tabular}
> 
> The id 48 request was made several months ago in May-24 for usb, no further
> interest has been shown on it.
> Better to avoid holes in the device id assignment.
> So id 48 would be better to use for media that has interest.
> Added virtio-usb proposer to thread to see if it is still interesting, in that case
> 49 seems good here.
> 
> Given the voting has started, I am not sure if the real id value matters as long
> as one of the unique id is reserved.
> 
> And do not prefer to restart the voting for such a small change either on my
> late observation of this hole.
> 
> I think when the maintainer merges the proposed patch to assign id 48,
> should be fine.
> 
> Michael,
> Are you ok this way? Or you have better suggestion?
> 
> Aishwarya,
> Is virtio-usb still interesting? If so, can you please request for the vote? So that
> we avoid the hole in device id assignment.
I received auto reply from Aishwarya's employer that they are not reachable due to acquisition.
So not sure if virtio-usb and 48 is still relevant.

RE: [PATCH v3] content: Reserve ID for media device

[Cornelia Huck]

On Tue, Oct 01 2024, Parav Pandit <parav@nvidia.com> wrote:

>> From: Parav Pandit <parav@nvidia.com>
>> Sent: Tuesday, October 1, 2024 1:35 PM
>> To: Albert Esteve <aesteve@redhat.com>; virtio-comment@lists.linux.dev;
>> aiswarya.cyriac@opensynergy.com
>> Cc: acourbot@chromium.org
>> Subject: RE: [PATCH v3] content: Reserve ID for media device
>> 
>> Hi Albert,
>> 
>> From: Albert Esteve <aesteve@redhat.com>
>> Sent: Wednesday, September 25, 2024 12:20 PM
>> 
>> 
>> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve <mailto:aesteve@redhat.com>
>> wrote:
>> Reserve device ID 49 for media device.
>> Compatible with video encoder, video decoder,
>> and capture devices.
>> 
>> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
>> ---
>>  content.tex | 2 ++
>>  1 file changed, 2 insertions(+)
>> 
>> diff --git a/content.tex b/content.tex
>> index 0a62dce..6d6b3d8 100644
>> --- a/content.tex
>> +++ b/content.tex
>> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
>>  \hline
>>  45         &   SPI master \\
>>  \hline
>> +49         &   Media device \\
>> +\hline
>>  \end{tabular}
>> 
>> The id 48 request was made several months ago in May-24 for usb, no further
>> interest has been shown on it.
>> Better to avoid holes in the device id assignment.
>> So id 48 would be better to use for media that has interest.
>> Added virtio-usb proposer to thread to see if it is still interesting, in that case
>> 49 seems good here.
>> 
>> Given the voting has started, I am not sure if the real id value matters as long
>> as one of the unique id is reserved.
>> 
>> And do not prefer to restart the voting for such a small change either on my
>> late observation of this hole.
>> 
>> I think when the maintainer merges the proposed patch to assign id 48,
>> should be fine.
>> 
>> Michael,
>> Are you ok this way? Or you have better suggestion?
>> 
>> Aishwarya,
>> Is virtio-usb still interesting? If so, can you please request for the vote? So that
>> we avoid the hole in device id assignment.
> I received auto reply from Aishwarya's employer that they are not reachable due to acquisition.
> So not sure if virtio-usb and 48 is still relevant.

OTOH, a gap in the id list doesn't really matter?

Re: [PATCH v3] content: Reserve ID for media device

[Albert Esteve]

[-- Attachment #1: Type: text/plain, Size: 2767 bytes --]

Hi,

I really wouldn't mind resending, but given that the voting has started,
not sure if it is worth canceling/changing it now.

But we can perhaps try to move the next device that tries to standardize to
fit in the gap that this patch created.


On Tue, Oct 1, 2024 at 10:51 AM Cornelia Huck <cohuck@redhat.com> wrote:

> On Tue, Oct 01 2024, Parav Pandit <parav@nvidia.com> wrote:
>
> >> From: Parav Pandit <parav@nvidia.com>
> >> Sent: Tuesday, October 1, 2024 1:35 PM
> >> To: Albert Esteve <aesteve@redhat.com>; virtio-comment@lists.linux.dev;
> >> aiswarya.cyriac@opensynergy.com
> >> Cc: acourbot@chromium.org
> >> Subject: RE: [PATCH v3] content: Reserve ID for media device
> >>
> >> Hi Albert,
> >>
> >> From: Albert Esteve <aesteve@redhat.com>
> >> Sent: Wednesday, September 25, 2024 12:20 PM
> >>
> >>
> >> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve <mailto:aesteve@redhat.com
> >
> >> wrote:
> >> Reserve device ID 49 for media device.
> >> Compatible with video encoder, video decoder,
> >> and capture devices.
> >>
> >> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
> >> ---
> >>  content.tex | 2 ++
> >>  1 file changed, 2 insertions(+)
> >>
> >> diff --git a/content.tex b/content.tex
> >> index 0a62dce..6d6b3d8 100644
> >> --- a/content.tex
> >> +++ b/content.tex
> >> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
> >>  \hline
> >>  45         &   SPI master \\
> >>  \hline
> >> +49         &   Media device \\
> >> +\hline
> >>  \end{tabular}
> >>
> >> The id 48 request was made several months ago in May-24 for usb, no
> further
> >> interest has been shown on it.
> >> Better to avoid holes in the device id assignment.
> >> So id 48 would be better to use for media that has interest.
> >> Added virtio-usb proposer to thread to see if it is still interesting,
> in that case
> >> 49 seems good here.
> >>
> >> Given the voting has started, I am not sure if the real id value
> matters as long
> >> as one of the unique id is reserved.
> >>
> >> And do not prefer to restart the voting for such a small change either
> on my
> >> late observation of this hole.
> >>
> >> I think when the maintainer merges the proposed patch to assign id 48,
> >> should be fine.
> >>
> >> Michael,
> >> Are you ok this way? Or you have better suggestion?
> >>
> >> Aishwarya,
> >> Is virtio-usb still interesting? If so, can you please request for the
> vote? So that
> >> we avoid the hole in device id assignment.
> > I received auto reply from Aishwarya's employer that they are not
> reachable due to acquisition.
> > So not sure if virtio-usb and 48 is still relevant.
>
> OTOH, a gap in the id list doesn't really matter?
>
>

[-- Attachment #2: Type: text/html, Size: 4489 bytes --]

RE: [PATCH v3] content: Reserve ID for media device

[Parav Pandit]

Hi Albert,

Please fix your email client to send text only email.
It gets hard to continue the conversation.

I don’t see the need to cancel voting. When merging the patch, we can use 48.

From: Albert Esteve <aesteve@redhat.com> 
Sent: Tuesday, October 1, 2024 2:38 PM
To: Cornelia Huck <cohuck@redhat.com>
Cc: Parav Pandit <parav@nvidia.com>; virtio-comment@lists.linux.dev; aiswarya.cyriac@opensynergy.com; acourbot@chromium.org
Subject: Re: [PATCH v3] content: Reserve ID for media device

Hi,

I really wouldn't mind resending, but given that the voting has started, not sure if it is worth canceling/changing it now.

But we can perhaps try to move the next device that tries to standardize to fit in the gap that this patch created.


On Tue, Oct 1, 2024 at 10:51 AM Cornelia Huck <mailto:cohuck@redhat.com> wrote:
On Tue, Oct 01 2024, Parav Pandit <mailto:parav@nvidia.com> wrote:

>> From: Parav Pandit <mailto:parav@nvidia.com>
>> Sent: Tuesday, October 1, 2024 1:35 PM
>> To: Albert Esteve <mailto:aesteve@redhat.com>; mailto:virtio-comment@lists.linux.dev;
>> mailto:aiswarya.cyriac@opensynergy.com
>> Cc: mailto:acourbot@chromium.org
>> Subject: RE: [PATCH v3] content: Reserve ID for media device
>> 
>> Hi Albert,
>> 
>> From: Albert Esteve <mailto:aesteve@redhat.com>
>> Sent: Wednesday, September 25, 2024 12:20 PM
>> 
>> 
>> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve <mailto:mailto:aesteve@redhat.com>
>> wrote:
>> Reserve device ID 49 for media device.
>> Compatible with video encoder, video decoder,
>> and capture devices.
>> 
>> Signed-off-by: Albert Esteve <mailto:mailto:aesteve@redhat.com>
>> ---
>>  content.tex | 2 ++
>>  1 file changed, 2 insertions(+)
>> 
>> diff --git a/content.tex b/content.tex
>> index 0a62dce..6d6b3d8 100644
>> --- a/content.tex
>> +++ b/content.tex
>> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
>>  \hline
>>  45         &   SPI master \\
>>  \hline
>> +49         &   Media device \\
>> +\hline
>>  \end{tabular}
>> 
>> The id 48 request was made several months ago in May-24 for usb, no further
>> interest has been shown on it.
>> Better to avoid holes in the device id assignment.
>> So id 48 would be better to use for media that has interest.
>> Added virtio-usb proposer to thread to see if it is still interesting, in that case
>> 49 seems good here.
>> 
>> Given the voting has started, I am not sure if the real id value matters as long
>> as one of the unique id is reserved.
>> 
>> And do not prefer to restart the voting for such a small change either on my
>> late observation of this hole.
>> 
>> I think when the maintainer merges the proposed patch to assign id 48,
>> should be fine.
>> 
>> Michael,
>> Are you ok this way? Or you have better suggestion?
>> 
>> Aishwarya,
>> Is virtio-usb still interesting? If so, can you please request for the vote? So that
>> we avoid the hole in device id assignment.
> I received auto reply from Aishwarya's employer that they are not reachable due to acquisition.
> So not sure if virtio-usb and 48 is still relevant.

OTOH, a gap in the id list doesn't really matter?

RE: [PATCH v3] content: Reserve ID for media device

[Parav Pandit]

> From: Cornelia Huck <cohuck@redhat.com>
> Sent: Tuesday, October 1, 2024 2:22 PM
> 
> On Tue, Oct 01 2024, Parav Pandit <parav@nvidia.com> wrote:
> 
> >> From: Parav Pandit <parav@nvidia.com>
> >> Sent: Tuesday, October 1, 2024 1:35 PM
> >> To: Albert Esteve <aesteve@redhat.com>;
> >> virtio-comment@lists.linux.dev; aiswarya.cyriac@opensynergy.com
> >> Cc: acourbot@chromium.org
> >> Subject: RE: [PATCH v3] content: Reserve ID for media device
> >>
> >> Hi Albert,
> >>
> >> From: Albert Esteve <aesteve@redhat.com>
> >> Sent: Wednesday, September 25, 2024 12:20 PM
> >>
> >>
> >> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve
> >> <mailto:aesteve@redhat.com>
> >> wrote:
> >> Reserve device ID 49 for media device.
> >> Compatible with video encoder, video decoder, and capture devices.
> >>
> >> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
> >> ---
> >>  content.tex | 2 ++
> >>  1 file changed, 2 insertions(+)
> >>
> >> diff --git a/content.tex b/content.tex index 0a62dce..6d6b3d8 100644
> >> --- a/content.tex
> >> +++ b/content.tex
> >> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
> >>  \hline
> >>  45         &   SPI master \\
> >>  \hline
> >> +49         &   Media device \\
> >> +\hline
> >>  \end{tabular}
> >>
> >> The id 48 request was made several months ago in May-24 for usb, no
> >> further interest has been shown on it.
> >> Better to avoid holes in the device id assignment.
> >> So id 48 would be better to use for media that has interest.
> >> Added virtio-usb proposer to thread to see if it is still
> >> interesting, in that case
> >> 49 seems good here.
> >>
> >> Given the voting has started, I am not sure if the real id value
> >> matters as long as one of the unique id is reserved.
> >>
> >> And do not prefer to restart the voting for such a small change
> >> either on my late observation of this hole.
> >>
> >> I think when the maintainer merges the proposed patch to assign id
> >> 48, should be fine.
> >>
> >> Michael,
> >> Are you ok this way? Or you have better suggestion?
> >>
> >> Aishwarya,
> >> Is virtio-usb still interesting? If so, can you please request for
> >> the vote? So that we avoid the hole in device id assignment.
> > I received auto reply from Aishwarya's employer that they are not reachable
> due to acquisition.
> > So not sure if virtio-usb and 48 is still relevant.
> 
> OTOH, a gap in the id list doesn't really matter?

It is elegant to keep the continuous range where one can verify the valid device ids without adding exception code to omit ids with hole.
The future proposers do not need to parse past emails to find out which ids are WIP that they need to omit when sending patches.
I don’t think the id in the patch really matters as long as next free id is assigned.

Re: [PATCH v3] content: Reserve ID for media device

[Alexander Gordeev]

On 01/10/2024 10:39, Parav Pandit wrote:
> 
> 
>> From: Parav Pandit <parav@nvidia.com>
>> Sent: Tuesday, October 1, 2024 1:35 PM
>> To: Albert Esteve <aesteve@redhat.com>; virtio-comment@lists.linux.dev;
>> aiswarya.cyriac@opensynergy.com
>> Cc: acourbot@chromium.org
>> Subject: RE: [PATCH v3] content: Reserve ID for media device
>>
>> Hi Albert,
>>
>> From: Albert Esteve <aesteve@redhat.com>
>> Sent: Wednesday, September 25, 2024 12:20 PM
>>
>>
>> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve <mailto:aesteve@redhat.com>
>> wrote:
>> Reserve device ID 49 for media device.
>> Compatible with video encoder, video decoder,
>> and capture devices.
>>
>> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
>> ---
>>  content.tex | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/content.tex b/content.tex
>> index 0a62dce..6d6b3d8 100644
>> --- a/content.tex
>> +++ b/content.tex
>> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
>>  \hline
>>  45         &   SPI master \\
>>  \hline
>> +49         &   Media device \\
>> +\hline
>>  \end{tabular}
>>
>> The id 48 request was made several months ago in May-24 for usb, no further
>> interest has been shown on it.
>> Better to avoid holes in the device id assignment.
>> So id 48 would be better to use for media that has interest.
>> Added virtio-usb proposer to thread to see if it is still interesting, in that case
>> 49 seems good here.
>>
>> Given the voting has started, I am not sure if the real id value matters as long
>> as one of the unique id is reserved.
>>
>> And do not prefer to restart the voting for such a small change either on my
>> late observation of this hole.
>>
>> I think when the maintainer merges the proposed patch to assign id 48,
>> should be fine.
>>
>> Michael,
>> Are you ok this way? Or you have better suggestion?
>>
>> Aishwarya,
>> Is virtio-usb still interesting? If so, can you please request for the vote? So that
>> we avoid the hole in device id assignment.
> I received auto reply from Aishwarya's employer that they are not reachable due to acquisition.
> So not sure if virtio-usb and 48 is still relevant.

Indeed we were acquired by Qualcomm.
AFAIK the work on virtio-usb is ongoing. Aiswarya is on vacation now, she'll be back next week.
I added her new email address.

RE: [PATCH v3] content: Reserve ID for media device

[Parav Pandit]

> From: Alexander Gordeev <quic_agordeev@quicinc.com>
> Sent: Tuesday, October 1, 2024 4:36 PM
> 
> On 01/10/2024 10:39, Parav Pandit wrote:
> >
> >
> >> From: Parav Pandit <parav@nvidia.com>
> >> Sent: Tuesday, October 1, 2024 1:35 PM
> >> To: Albert Esteve <aesteve@redhat.com>;
> >> virtio-comment@lists.linux.dev; aiswarya.cyriac@opensynergy.com
> >> Cc: acourbot@chromium.org
> >> Subject: RE: [PATCH v3] content: Reserve ID for media device
> >>
> >> Hi Albert,
> >>
> >> From: Albert Esteve <aesteve@redhat.com>
> >> Sent: Wednesday, September 25, 2024 12:20 PM
> >>
> >>
> >> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve
> >> <mailto:aesteve@redhat.com>
> >> wrote:
> >> Reserve device ID 49 for media device.
> >> Compatible with video encoder, video decoder, and capture devices.
> >>
> >> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
> >> ---
> >>  content.tex | 2 ++
> >>  1 file changed, 2 insertions(+)
> >>
> >> diff --git a/content.tex b/content.tex index 0a62dce..6d6b3d8 100644
> >> --- a/content.tex
> >> +++ b/content.tex
> >> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
> >>  \hline
> >>  45         &   SPI master \\
> >>  \hline
> >> +49         &   Media device \\
> >> +\hline
> >>  \end{tabular}
> >>
> >> The id 48 request was made several months ago in May-24 for usb, no
> >> further interest has been shown on it.
> >> Better to avoid holes in the device id assignment.
> >> So id 48 would be better to use for media that has interest.
> >> Added virtio-usb proposer to thread to see if it is still
> >> interesting, in that case
> >> 49 seems good here.
> >>
> >> Given the voting has started, I am not sure if the real id value
> >> matters as long as one of the unique id is reserved.
> >>
> >> And do not prefer to restart the voting for such a small change
> >> either on my late observation of this hole.
> >>
> >> I think when the maintainer merges the proposed patch to assign id
> >> 48, should be fine.
> >>
> >> Michael,
> >> Are you ok this way? Or you have better suggestion?
> >>
> >> Aishwarya,
> >> Is virtio-usb still interesting? If so, can you please request for
> >> the vote? So that we avoid the hole in device id assignment.
> > I received auto reply from Aishwarya's employer that they are not reachable
> due to acquisition.
> > So not sure if virtio-usb and 48 is still relevant.
> 
> Indeed we were acquired by Qualcomm.
> AFAIK the work on virtio-usb is ongoing. Aiswarya is on vacation now, she'll be
> back next week.
> I added her new email address.
Ok So we won't have the hole beyond few weeks. That is good.

Thanks.

RE: [PATCH v3] content: Reserve ID for media device

[Aiswarya Cyriac (QUIC)]

Hi Parav,

> -----Original Message-----
> From: Parav Pandit <parav@nvidia.com>
> Sent: Tuesday, October 1, 2024 1:53 PM
> To: Alexander Gordeev (QUIC) <quic_agordeev@quicinc.com>; Albert Esteve
> <aesteve@redhat.com>; virtio-comment@lists.linux.dev; Aiswarya Cyriac
> (QUIC) <quic_acyriac@quicinc.com>
> Cc: acourbot@chromium.org
> Subject: RE: [PATCH v3] content: Reserve ID for media device
> 
> 
> > From: Alexander Gordeev <quic_agordeev@quicinc.com>
> > Sent: Tuesday, October 1, 2024 4:36 PM
> >
> > On 01/10/2024 10:39, Parav Pandit wrote:
> > >
> > >
> > >> From: Parav Pandit <parav@nvidia.com>
> > >> Sent: Tuesday, October 1, 2024 1:35 PM
> > >> To: Albert Esteve <aesteve@redhat.com>;
> > >> virtio-comment@lists.linux.dev; aiswarya.cyriac@opensynergy.com
> > >> Cc: acourbot@chromium.org
> > >> Subject: RE: [PATCH v3] content: Reserve ID for media device
> > >>
> > >> Hi Albert,
> > >>
> > >> From: Albert Esteve <aesteve@redhat.com>
> > >> Sent: Wednesday, September 25, 2024 12:20 PM
> > >>
> > >>
> > >> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve
> > >> <mailto:aesteve@redhat.com>
> > >> wrote:
> > >> Reserve device ID 49 for media device.
> > >> Compatible with video encoder, video decoder, and capture devices.
> > >>
> > >> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
> > >> ---
> > >>  content.tex | 2 ++
> > >>  1 file changed, 2 insertions(+)
> > >>
> > >> diff --git a/content.tex b/content.tex index 0a62dce..6d6b3d8
> > >> 100644
> > >> --- a/content.tex
> > >> +++ b/content.tex
> > >> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
> > >>  \hline
> > >>  45         &   SPI master \\
> > >>  \hline
> > >> +49         &   Media device \\
> > >> +\hline
> > >>  \end{tabular}
> > >>
> > >> The id 48 request was made several months ago in May-24 for usb, no
> > >> further interest has been shown on it.
> > >> Better to avoid holes in the device id assignment.
> > >> So id 48 would be better to use for media that has interest.
> > >> Added virtio-usb proposer to thread to see if it is still
> > >> interesting, in that case
> > >> 49 seems good here.
> > >>
> > >> Given the voting has started, I am not sure if the real id value
> > >> matters as long as one of the unique id is reserved.
> > >>
> > >> And do not prefer to restart the voting for such a small change
> > >> either on my late observation of this hole.
> > >>
> > >> I think when the maintainer merges the proposed patch to assign id
> > >> 48, should be fine.
> > >>
> > >> Michael,
> > >> Are you ok this way? Or you have better suggestion?
> > >>
> > >> Aishwarya,
> > >> Is virtio-usb still interesting? If so, can you please request for
> > >> the vote? So that we avoid the hole in device id assignment.
> > > I received auto reply from Aishwarya's employer that they are not
> > > reachable
> > due to acquisition.
> > > So not sure if virtio-usb and 48 is still relevant.
> >

We are interested in the virtio-usb device and would like to reserve ID 48 for it.
However, I plan to push a version 2 patch to ensure the reservation covers not just the virtio-usb host controller, but the virtio-usb device.

Thank you

> > Indeed we were acquired by Qualcomm.
> > AFAIK the work on virtio-usb is ongoing. Aiswarya is on vacation now,
> > she'll be back next week.
> > I added her new email address.
> Ok So we won't have the hole beyond few weeks. That is good.
> 
> Thanks.

RE: [PATCH v3] content: Reserve ID for media device

[Parav Pandit]

Hi Aiswarya,

> From: Aiswarya Cyriac (QUIC) <quic_acyriac@quicinc.com>
> Sent: Wednesday, October 9, 2024 2:17 PM
> To: Parav Pandit <parav@nvidia.com>; Alexander Gordeev (QUIC)
> <quic_agordeev@quicinc.com>; Albert Esteve <aesteve@redhat.com>; virtio-
> comment@lists.linux.dev; Aiswarya Cyriac (QUIC)
> <quic_acyriac@quicinc.com>
> Cc: acourbot@chromium.org
> Subject: RE: [PATCH v3] content: Reserve ID for media device
> 
> Hi Parav,
> 
> > -----Original Message-----
> > From: Parav Pandit <parav@nvidia.com>
> > Sent: Tuesday, October 1, 2024 1:53 PM
> > To: Alexander Gordeev (QUIC) <quic_agordeev@quicinc.com>; Albert
> > Esteve <aesteve@redhat.com>; virtio-comment@lists.linux.dev; Aiswarya
> > Cyriac
> > (QUIC) <quic_acyriac@quicinc.com>
> > Cc: acourbot@chromium.org
> > Subject: RE: [PATCH v3] content: Reserve ID for media device
> >
> >
> > > From: Alexander Gordeev <quic_agordeev@quicinc.com>
> > > Sent: Tuesday, October 1, 2024 4:36 PM
> > >
> > > On 01/10/2024 10:39, Parav Pandit wrote:
> > > >
> > > >
> > > >> From: Parav Pandit <parav@nvidia.com>
> > > >> Sent: Tuesday, October 1, 2024 1:35 PM
> > > >> To: Albert Esteve <aesteve@redhat.com>;
> > > >> virtio-comment@lists.linux.dev; aiswarya.cyriac@opensynergy.com
> > > >> Cc: acourbot@chromium.org
> > > >> Subject: RE: [PATCH v3] content: Reserve ID for media device
> > > >>
> > > >> Hi Albert,
> > > >>
> > > >> From: Albert Esteve <aesteve@redhat.com>
> > > >> Sent: Wednesday, September 25, 2024 12:20 PM
> > > >>
> > > >>
> > > >> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve
> > > >> <mailto:aesteve@redhat.com>
> > > >> wrote:
> > > >> Reserve device ID 49 for media device.
> > > >> Compatible with video encoder, video decoder, and capture devices.
> > > >>
> > > >> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
> > > >> ---
> > > >>  content.tex | 2 ++
> > > >>  1 file changed, 2 insertions(+)
> > > >>
> > > >> diff --git a/content.tex b/content.tex index 0a62dce..6d6b3d8
> > > >> 100644
> > > >> --- a/content.tex
> > > >> +++ b/content.tex
> > > >> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device
> > > >> Types}
> > > >>  \hline
> > > >>  45         &   SPI master \\
> > > >>  \hline
> > > >> +49         &   Media device \\
> > > >> +\hline
> > > >>  \end{tabular}
> > > >>
> > > >> The id 48 request was made several months ago in May-24 for usb,
> > > >> no further interest has been shown on it.
> > > >> Better to avoid holes in the device id assignment.
> > > >> So id 48 would be better to use for media that has interest.
> > > >> Added virtio-usb proposer to thread to see if it is still
> > > >> interesting, in that case
> > > >> 49 seems good here.
> > > >>
> > > >> Given the voting has started, I am not sure if the real id value
> > > >> matters as long as one of the unique id is reserved.
> > > >>
> > > >> And do not prefer to restart the voting for such a small change
> > > >> either on my late observation of this hole.
> > > >>
> > > >> I think when the maintainer merges the proposed patch to assign
> > > >> id 48, should be fine.
> > > >>
> > > >> Michael,
> > > >> Are you ok this way? Or you have better suggestion?
> > > >>
> > > >> Aishwarya,
> > > >> Is virtio-usb still interesting? If so, can you please request
> > > >> for the vote? So that we avoid the hole in device id assignment.
> > > > I received auto reply from Aishwarya's employer that they are not
> > > > reachable
> > > due to acquisition.
> > > > So not sure if virtio-usb and 48 is still relevant.
> > >
> 
> We are interested in the virtio-usb device and would like to reserve ID 48 for it.
> However, I plan to push a version 2 patch to ensure the reservation covers not
> just the virtio-usb host controller, but the virtio-usb device.
> 
Any plan to request for virtio-usb device in next two weeks?
If not, then virtio-media can proceed with ID 48 (this is the first free id) and later when you are ready, virtio-usb can pick the next free ID.
This will help to not create any holes for some indefinite time in the ID list.

RE: [PATCH v3] content: Reserve ID for media device

[Aiswarya Cyriac (QUIC)]

Hi Parav,

> -----Original Message-----
> From: Parav Pandit <parav@nvidia.com>
> Sent: Wednesday, October 30, 2024 9:15 AM
> To: Aiswarya Cyriac (QUIC) <quic_acyriac@quicinc.com>; Alexander Gordeev
> (QUIC) <quic_agordeev@quicinc.com>; Albert Esteve <aesteve@redhat.com>;
> virtio-comment@lists.linux.dev
> Cc: acourbot@chromium.org
> Subject: RE: [PATCH v3] content: Reserve ID for media device
> 
> WARNING: This email originated from outside of Qualcomm. Please be wary
> of any links or attachments, and do not enable macros.
> 
> Hi Aiswarya,
> 
> > From: Aiswarya Cyriac (QUIC) <quic_acyriac@quicinc.com>
> > Sent: Wednesday, October 9, 2024 2:17 PM
> > To: Parav Pandit <parav@nvidia.com>; Alexander Gordeev (QUIC)
> > <quic_agordeev@quicinc.com>; Albert Esteve <aesteve@redhat.com>;
> > virtio- comment@lists.linux.dev; Aiswarya Cyriac (QUIC)
> > <quic_acyriac@quicinc.com>
> > Cc: acourbot@chromium.org
> > Subject: RE: [PATCH v3] content: Reserve ID for media device
> >
> > Hi Parav,
> >
> > > -----Original Message-----
> > > From: Parav Pandit <parav@nvidia.com>
> > > Sent: Tuesday, October 1, 2024 1:53 PM
> > > To: Alexander Gordeev (QUIC) <quic_agordeev@quicinc.com>; Albert
> > > Esteve <aesteve@redhat.com>; virtio-comment@lists.linux.dev;
> > > Aiswarya Cyriac
> > > (QUIC) <quic_acyriac@quicinc.com>
> > > Cc: acourbot@chromium.org
> > > Subject: RE: [PATCH v3] content: Reserve ID for media device
> > >
> > >
> > > > From: Alexander Gordeev <quic_agordeev@quicinc.com>
> > > > Sent: Tuesday, October 1, 2024 4:36 PM
> > > >
> > > > On 01/10/2024 10:39, Parav Pandit wrote:
> > > > >
> > > > >
> > > > >> From: Parav Pandit <parav@nvidia.com>
> > > > >> Sent: Tuesday, October 1, 2024 1:35 PM
> > > > >> To: Albert Esteve <aesteve@redhat.com>;
> > > > >> virtio-comment@lists.linux.dev; aiswarya.cyriac@opensynergy.com
> > > > >> Cc: acourbot@chromium.org
> > > > >> Subject: RE: [PATCH v3] content: Reserve ID for media device
> > > > >>
> > > > >> Hi Albert,
> > > > >>
> > > > >> From: Albert Esteve <aesteve@redhat.com>
> > > > >> Sent: Wednesday, September 25, 2024 12:20 PM
> > > > >>
> > > > >>
> > > > >> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve
> > > > >> <mailto:aesteve@redhat.com>
> > > > >> wrote:
> > > > >> Reserve device ID 49 for media device.
> > > > >> Compatible with video encoder, video decoder, and capture devices.
> > > > >>
> > > > >> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
> > > > >> ---
> > > > >>  content.tex | 2 ++
> > > > >>  1 file changed, 2 insertions(+)
> > > > >>
> > > > >> diff --git a/content.tex b/content.tex index 0a62dce..6d6b3d8
> > > > >> 100644
> > > > >> --- a/content.tex
> > > > >> +++ b/content.tex
> > > > >> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device
> > > > >> Types}  \hline
> > > > >>  45         &   SPI master \\
> > > > >>  \hline
> > > > >> +49         &   Media device \\
> > > > >> +\hline
> > > > >>  \end{tabular}
> > > > >>
> > > > >> The id 48 request was made several months ago in May-24 for
> > > > >> usb, no further interest has been shown on it.
> > > > >> Better to avoid holes in the device id assignment.
> > > > >> So id 48 would be better to use for media that has interest.
> > > > >> Added virtio-usb proposer to thread to see if it is still
> > > > >> interesting, in that case
> > > > >> 49 seems good here.
> > > > >>
> > > > >> Given the voting has started, I am not sure if the real id
> > > > >> value matters as long as one of the unique id is reserved.
> > > > >>
> > > > >> And do not prefer to restart the voting for such a small change
> > > > >> either on my late observation of this hole.
> > > > >>
> > > > >> I think when the maintainer merges the proposed patch to assign
> > > > >> id 48, should be fine.
> > > > >>
> > > > >> Michael,
> > > > >> Are you ok this way? Or you have better suggestion?
> > > > >>
> > > > >> Aishwarya,
> > > > >> Is virtio-usb still interesting? If so, can you please request
> > > > >> for the vote? So that we avoid the hole in device id assignment.
> > > > > I received auto reply from Aishwarya's employer that they are
> > > > > not reachable
> > > > due to acquisition.
> > > > > So not sure if virtio-usb and 48 is still relevant.
> > > >
> >
> > We are interested in the virtio-usb device and would like to reserve ID 48 for
> it.
> > However, I plan to push a version 2 patch to ensure the reservation
> > covers not just the virtio-usb host controller, but the virtio-usb device.
> >
> Any plan to request for virtio-usb device in next two weeks?
> If not, then virtio-media can proceed with ID 48 (this is the first free id) and
> later when you are ready, virtio-usb can pick the next free ID.
> This will help to not create any holes for some indefinite time in the ID list.
[>

RE: [PATCH v3] content: Reserve ID for media device

[Aiswarya Cyriac (QUIC)]

Hi Parav,

> -----Original Message-----
> From: Parav Pandit <parav@nvidia.com>
> Sent: Wednesday, October 30, 2024 9:15 AM
> To: Aiswarya Cyriac (QUIC) <quic_acyriac@quicinc.com>; Alexander Gordeev
> (QUIC) <quic_agordeev@quicinc.com>; Albert Esteve <aesteve@redhat.com>;
> virtio-comment@lists.linux.dev
> Cc: acourbot@chromium.org
> Subject: RE: [PATCH v3] content: Reserve ID for media device
> 
> Hi Aiswarya,
> 
> > From: Aiswarya Cyriac (QUIC) <quic_acyriac@quicinc.com>
> > Sent: Wednesday, October 9, 2024 2:17 PM
> > To: Parav Pandit <parav@nvidia.com>; Alexander Gordeev (QUIC)
> > <quic_agordeev@quicinc.com>; Albert Esteve <aesteve@redhat.com>;
> > virtio- comment@lists.linux.dev; Aiswarya Cyriac (QUIC)
> > <quic_acyriac@quicinc.com>
> > Cc: acourbot@chromium.org
> > Subject: RE: [PATCH v3] content: Reserve ID for media device
> >
> > Hi Parav,
> >
> > > -----Original Message-----
> > > From: Parav Pandit <parav@nvidia.com>
> > > Sent: Tuesday, October 1, 2024 1:53 PM
> > > To: Alexander Gordeev (QUIC) <quic_agordeev@quicinc.com>; Albert
> > > Esteve <aesteve@redhat.com>; virtio-comment@lists.linux.dev;
> > > Aiswarya Cyriac
> > > (QUIC) <quic_acyriac@quicinc.com>
> > > Cc: acourbot@chromium.org
> > > Subject: RE: [PATCH v3] content: Reserve ID for media device
> > >
> > >
> > > > From: Alexander Gordeev <quic_agordeev@quicinc.com>
> > > > Sent: Tuesday, October 1, 2024 4:36 PM
> > > >
> > > > On 01/10/2024 10:39, Parav Pandit wrote:
> > > > >
> > > > >
> > > > >> From: Parav Pandit <parav@nvidia.com>
> > > > >> Sent: Tuesday, October 1, 2024 1:35 PM
> > > > >> To: Albert Esteve <aesteve@redhat.com>;
> > > > >> virtio-comment@lists.linux.dev; aiswarya.cyriac@opensynergy.com
> > > > >> Cc: acourbot@chromium.org
> > > > >> Subject: RE: [PATCH v3] content: Reserve ID for media device
> > > > >>
> > > > >> Hi Albert,
> > > > >>
> > > > >> From: Albert Esteve <aesteve@redhat.com>
> > > > >> Sent: Wednesday, September 25, 2024 12:20 PM
> > > > >>
> > > > >>
> > > > >> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve
> > > > >> <mailto:aesteve@redhat.com>
> > > > >> wrote:
> > > > >> Reserve device ID 49 for media device.
> > > > >> Compatible with video encoder, video decoder, and capture devices.
> > > > >>
> > > > >> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
> > > > >> ---
> > > > >>  content.tex | 2 ++
> > > > >>  1 file changed, 2 insertions(+)
> > > > >>
> > > > >> diff --git a/content.tex b/content.tex index 0a62dce..6d6b3d8
> > > > >> 100644
> > > > >> --- a/content.tex
> > > > >> +++ b/content.tex
> > > > >> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device
> > > > >> Types}
> > > > >>  \hline
> > > > >>  45         &   SPI master \\
> > > > >>  \hline
> > > > >> +49         &   Media device \\ \hline
> > > > >>  \end{tabular}
> > > > >>
> > > > >> The id 48 request was made several months ago in May-24 for
> > > > >> usb, no further interest has been shown on it.
> > > > >> Better to avoid holes in the device id assignment.
> > > > >> So id 48 would be better to use for media that has interest.
> > > > >> Added virtio-usb proposer to thread to see if it is still
> > > > >> interesting, in that case
> > > > >> 49 seems good here.
> > > > >>
> > > > >> Given the voting has started, I am not sure if the real id
> > > > >> value matters as long as one of the unique id is reserved.
> > > > >>
> > > > >> And do not prefer to restart the voting for such a small change
> > > > >> either on my late observation of this hole.
> > > > >>
> > > > >> I think when the maintainer merges the proposed patch to assign
> > > > >> id 48, should be fine.
> > > > >>
> > > > >> Michael,
> > > > >> Are you ok this way? Or you have better suggestion?
> > > > >>
> > > > >> Aishwarya,
> > > > >> Is virtio-usb still interesting? If so, can you please request
> > > > >> for the vote? So that we avoid the hole in device id assignment.
> > > > > I received auto reply from Aishwarya's employer that they are
> > > > > not reachable
> > > > due to acquisition.
> > > > > So not sure if virtio-usb and 48 is still relevant.
> > > >
> >
> > We are interested in the virtio-usb device and would like to reserve ID 48 for
> it.
> > However, I plan to push a version 2 patch to ensure the reservation
> > covers not just the virtio-usb host controller, but the virtio-usb device.
> >
> Any plan to request for virtio-usb device in next two weeks?
> If not, then virtio-media can proceed with ID 48 (this is the first free id) and
> later when you are ready, virtio-usb can pick the next free ID.
> This will help to not create any holes for some indefinite time in the ID list.

Thank you for checking with me again.
Unfortunately, the process of updating the patch is taking longer than expected and we may not be able to update the patch in next 2 weeks.
I am ready to reserve the next free ID later.

Thanks,
Aiswarya

RE: [PATCH v3] content: Reserve ID for media device

[Parav Pandit]

> From: Aiswarya Cyriac (QUIC) <quic_acyriac@quicinc.com>
> Sent: Wednesday, October 30, 2024 4:08 PM
> 
> Hi Parav,
> 
> > -----Original Message-----
> > From: Parav Pandit <parav@nvidia.com>
> > Sent: Wednesday, October 30, 2024 9:15 AM
> > To: Aiswarya Cyriac (QUIC) <quic_acyriac@quicinc.com>; Alexander
> > Gordeev
> > (QUIC) <quic_agordeev@quicinc.com>; Albert Esteve
> > <aesteve@redhat.com>; virtio-comment@lists.linux.dev
> > Cc: acourbot@chromium.org
> > Subject: RE: [PATCH v3] content: Reserve ID for media device
> >
> > Hi Aiswarya,
> >
> > > From: Aiswarya Cyriac (QUIC) <quic_acyriac@quicinc.com>
> > > Sent: Wednesday, October 9, 2024 2:17 PM
> > > To: Parav Pandit <parav@nvidia.com>; Alexander Gordeev (QUIC)
> > > <quic_agordeev@quicinc.com>; Albert Esteve <aesteve@redhat.com>;
> > > virtio- comment@lists.linux.dev; Aiswarya Cyriac (QUIC)
> > > <quic_acyriac@quicinc.com>
> > > Cc: acourbot@chromium.org
> > > Subject: RE: [PATCH v3] content: Reserve ID for media device
> > >
> > > Hi Parav,
> > >
> > > > -----Original Message-----
> > > > From: Parav Pandit <parav@nvidia.com>
> > > > Sent: Tuesday, October 1, 2024 1:53 PM
> > > > To: Alexander Gordeev (QUIC) <quic_agordeev@quicinc.com>; Albert
> > > > Esteve <aesteve@redhat.com>; virtio-comment@lists.linux.dev;
> > > > Aiswarya Cyriac
> > > > (QUIC) <quic_acyriac@quicinc.com>
> > > > Cc: acourbot@chromium.org
> > > > Subject: RE: [PATCH v3] content: Reserve ID for media device
> > > >
> > > >
> > > > > From: Alexander Gordeev <quic_agordeev@quicinc.com>
> > > > > Sent: Tuesday, October 1, 2024 4:36 PM
> > > > >
> > > > > On 01/10/2024 10:39, Parav Pandit wrote:
> > > > > >
> > > > > >
> > > > > >> From: Parav Pandit <parav@nvidia.com>
> > > > > >> Sent: Tuesday, October 1, 2024 1:35 PM
> > > > > >> To: Albert Esteve <aesteve@redhat.com>;
> > > > > >> virtio-comment@lists.linux.dev;
> > > > > >> aiswarya.cyriac@opensynergy.com
> > > > > >> Cc: acourbot@chromium.org
> > > > > >> Subject: RE: [PATCH v3] content: Reserve ID for media device
> > > > > >>
> > > > > >> Hi Albert,
> > > > > >>
> > > > > >> From: Albert Esteve <aesteve@redhat.com>
> > > > > >> Sent: Wednesday, September 25, 2024 12:20 PM
> > > > > >>
> > > > > >>
> > > > > >> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve
> > > > > >> <mailto:aesteve@redhat.com>
> > > > > >> wrote:
> > > > > >> Reserve device ID 49 for media device.
> > > > > >> Compatible with video encoder, video decoder, and capture
> devices.
> > > > > >>
> > > > > >> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
> > > > > >> ---
> > > > > >>  content.tex | 2 ++
> > > > > >>  1 file changed, 2 insertions(+)
> > > > > >>
> > > > > >> diff --git a/content.tex b/content.tex index 0a62dce..6d6b3d8
> > > > > >> 100644
> > > > > >> --- a/content.tex
> > > > > >> +++ b/content.tex
> > > > > >> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device
> > > > > >> Types}
> > > > > >>  \hline
> > > > > >>  45         &   SPI master \\
> > > > > >>  \hline
> > > > > >> +49         &   Media device \\ \hline
> > > > > >>  \end{tabular}
> > > > > >>
> > > > > >> The id 48 request was made several months ago in May-24 for
> > > > > >> usb, no further interest has been shown on it.
> > > > > >> Better to avoid holes in the device id assignment.
> > > > > >> So id 48 would be better to use for media that has interest.
> > > > > >> Added virtio-usb proposer to thread to see if it is still
> > > > > >> interesting, in that case
> > > > > >> 49 seems good here.
> > > > > >>
> > > > > >> Given the voting has started, I am not sure if the real id
> > > > > >> value matters as long as one of the unique id is reserved.
> > > > > >>
> > > > > >> And do not prefer to restart the voting for such a small
> > > > > >> change either on my late observation of this hole.
> > > > > >>
> > > > > >> I think when the maintainer merges the proposed patch to
> > > > > >> assign id 48, should be fine.
> > > > > >>
> > > > > >> Michael,
> > > > > >> Are you ok this way? Or you have better suggestion?
> > > > > >>
> > > > > >> Aishwarya,
> > > > > >> Is virtio-usb still interesting? If so, can you please
> > > > > >> request for the vote? So that we avoid the hole in device id
> assignment.
> > > > > > I received auto reply from Aishwarya's employer that they are
> > > > > > not reachable
> > > > > due to acquisition.
> > > > > > So not sure if virtio-usb and 48 is still relevant.
> > > > >
> > >
> > > We are interested in the virtio-usb device and would like to reserve
> > > ID 48 for
> > it.
> > > However, I plan to push a version 2 patch to ensure the reservation
> > > covers not just the virtio-usb host controller, but the virtio-usb device.
> > >
> > Any plan to request for virtio-usb device in next two weeks?
> > If not, then virtio-media can proceed with ID 48 (this is the first
> > free id) and later when you are ready, virtio-usb can pick the next free ID.
> > This will help to not create any holes for some indefinite time in the ID list.
> 
> Thank you for checking with me again.
> Unfortunately, the process of updating the patch is taking longer than
> expected and we may not be able to update the patch in next 2 weeks.
> I am ready to reserve the next free ID later.
> 
Thanks for the quick confirmation.
In that case virtio-media can pick the first free id.
Will change accordingly.

> Thanks,
> Aiswarya

RE: [PATCH v3] content: Reserve ID for media device

[Parav Pandit]

> From: Parav Pandit <parav@nvidia.com>
> Sent: Thursday, October 31, 2024 11:11 AM
> 
> > From: Aiswarya Cyriac (QUIC) <quic_acyriac@quicinc.com>
> > Sent: Wednesday, October 30, 2024 4:08 PM
> >
> > Hi Parav,
> >
> > > -----Original Message-----
> > > From: Parav Pandit <parav@nvidia.com>
> > > Sent: Wednesday, October 30, 2024 9:15 AM
> > > To: Aiswarya Cyriac (QUIC) <quic_acyriac@quicinc.com>; Alexander
> > > Gordeev
> > > (QUIC) <quic_agordeev@quicinc.com>; Albert Esteve
> > > <aesteve@redhat.com>; virtio-comment@lists.linux.dev
> > > Cc: acourbot@chromium.org
> > > Subject: RE: [PATCH v3] content: Reserve ID for media device
> > >
> > > Hi Aiswarya,
> > >
> > > > From: Aiswarya Cyriac (QUIC) <quic_acyriac@quicinc.com>
> > > > Sent: Wednesday, October 9, 2024 2:17 PM
> > > > To: Parav Pandit <parav@nvidia.com>; Alexander Gordeev (QUIC)
> > > > <quic_agordeev@quicinc.com>; Albert Esteve <aesteve@redhat.com>;
> > > > virtio- comment@lists.linux.dev; Aiswarya Cyriac (QUIC)
> > > > <quic_acyriac@quicinc.com>
> > > > Cc: acourbot@chromium.org
> > > > Subject: RE: [PATCH v3] content: Reserve ID for media device
> > > >
> > > > Hi Parav,
> > > >
> > > > > -----Original Message-----
> > > > > From: Parav Pandit <parav@nvidia.com>
> > > > > Sent: Tuesday, October 1, 2024 1:53 PM
> > > > > To: Alexander Gordeev (QUIC) <quic_agordeev@quicinc.com>; Albert
> > > > > Esteve <aesteve@redhat.com>; virtio-comment@lists.linux.dev;
> > > > > Aiswarya Cyriac
> > > > > (QUIC) <quic_acyriac@quicinc.com>
> > > > > Cc: acourbot@chromium.org
> > > > > Subject: RE: [PATCH v3] content: Reserve ID for media device
> > > > >
> > > > >
> > > > > > From: Alexander Gordeev <quic_agordeev@quicinc.com>
> > > > > > Sent: Tuesday, October 1, 2024 4:36 PM
> > > > > >
> > > > > > On 01/10/2024 10:39, Parav Pandit wrote:
> > > > > > >
> > > > > > >
> > > > > > >> From: Parav Pandit <parav@nvidia.com>
> > > > > > >> Sent: Tuesday, October 1, 2024 1:35 PM
> > > > > > >> To: Albert Esteve <aesteve@redhat.com>;
> > > > > > >> virtio-comment@lists.linux.dev;
> > > > > > >> aiswarya.cyriac@opensynergy.com
> > > > > > >> Cc: acourbot@chromium.org
> > > > > > >> Subject: RE: [PATCH v3] content: Reserve ID for media
> > > > > > >> device
> > > > > > >>
> > > > > > >> Hi Albert,
> > > > > > >>
> > > > > > >> From: Albert Esteve <aesteve@redhat.com>
> > > > > > >> Sent: Wednesday, September 25, 2024 12:20 PM
> > > > > > >>
> > > > > > >>
> > > > > > >> On Fri, Sep 6, 2024 at 9:08 AM Albert Esteve
> > > > > > >> <mailto:aesteve@redhat.com>
> > > > > > >> wrote:
> > > > > > >> Reserve device ID 49 for media device.
> > > > > > >> Compatible with video encoder, video decoder, and capture
> > devices.
> > > > > > >>
> > > > > > >> Signed-off-by: Albert Esteve <mailto:aesteve@redhat.com>
> > > > > > >> ---
> > > > > > >>  content.tex | 2 ++
> > > > > > >>  1 file changed, 2 insertions(+)
> > > > > > >>
> > > > > > >> diff --git a/content.tex b/content.tex index
> > > > > > >> 0a62dce..6d6b3d8
> > > > > > >> 100644
> > > > > > >> --- a/content.tex
> > > > > > >> +++ b/content.tex
> > > > > > >> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device
> > > > > > >> Types}
> > > > > > >>  \hline
> > > > > > >>  45         &   SPI master \\
> > > > > > >>  \hline
> > > > > > >> +49         &   Media device \\ \hline
> > > > > > >>  \end{tabular}
> > > > > > >>
> > > > > > >> The id 48 request was made several months ago in May-24 for
> > > > > > >> usb, no further interest has been shown on it.
> > > > > > >> Better to avoid holes in the device id assignment.
> > > > > > >> So id 48 would be better to use for media that has interest.
> > > > > > >> Added virtio-usb proposer to thread to see if it is still
> > > > > > >> interesting, in that case
> > > > > > >> 49 seems good here.
> > > > > > >>
> > > > > > >> Given the voting has started, I am not sure if the real id
> > > > > > >> value matters as long as one of the unique id is reserved.
> > > > > > >>
> > > > > > >> And do not prefer to restart the voting for such a small
> > > > > > >> change either on my late observation of this hole.
> > > > > > >>
> > > > > > >> I think when the maintainer merges the proposed patch to
> > > > > > >> assign id 48, should be fine.
> > > > > > >>
> > > > > > >> Michael,
> > > > > > >> Are you ok this way? Or you have better suggestion?
> > > > > > >>
> > > > > > >> Aishwarya,
> > > > > > >> Is virtio-usb still interesting? If so, can you please
> > > > > > >> request for the vote? So that we avoid the hole in device
> > > > > > >> id
> > assignment.
> > > > > > > I received auto reply from Aishwarya's employer that they
> > > > > > > are not reachable
> > > > > > due to acquisition.
> > > > > > > So not sure if virtio-usb and 48 is still relevant.
> > > > > >
> > > >
> > > > We are interested in the virtio-usb device and would like to
> > > > reserve ID 48 for
> > > it.
> > > > However, I plan to push a version 2 patch to ensure the
> > > > reservation covers not just the virtio-usb host controller, but the virtio-
> usb device.
> > > >
> > > Any plan to request for virtio-usb device in next two weeks?
> > > If not, then virtio-media can proceed with ID 48 (this is the first
> > > free id) and later when you are ready, virtio-usb can pick the next free ID.
> > > This will help to not create any holes for some indefinite time in the ID
> list.
> >
> > Thank you for checking with me again.
> > Unfortunately, the process of updating the patch is taking longer than
> > expected and we may not be able to update the patch in next 2 weeks.
> > I am ready to reserve the next free ID later.
> >
> Thanks for the quick confirmation.
> In that case virtio-media can pick the first free id.
> Will change accordingly.
> 
> > Thanks,
> > Aiswarya

Applied by assigning the first free id 48.