All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>, Parav Pandit <parav@nvidia.com>,
	Albert Esteve <aesteve@redhat.com>,
	"virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>,
	"aiswarya.cyriac@opensynergy.com"
	<aiswarya.cyriac@opensynergy.com>
Cc: "acourbot@chromium.org" <acourbot@chromium.org>
Subject: RE: [PATCH v3] content: Reserve ID for media device
Date: Tue, 01 Oct 2024 10:51:39 +0200	[thread overview]
Message-ID: <87ikucrysk.fsf@redhat.com> (raw)
In-Reply-To: <IA0PR12MB87130D5F5839629436E0A748DC772@IA0PR12MB8713.namprd12.prod.outlook.com>

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?


  reply	other threads:[~2024-10-01  8:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06  7:08 [PATCH v3] content: Reserve ID for media device Albert Esteve
2024-09-25  6:49 ` Albert Esteve
2024-10-01  8:04   ` Parav Pandit
2024-10-01  8:39     ` Parav Pandit
2024-10-01  8:51       ` Cornelia Huck [this message]
2024-10-01  9:07         ` Albert Esteve
2024-10-01  9:09           ` Parav Pandit
2024-10-01  9:12         ` Parav Pandit
2024-10-01 11:05       ` Alexander Gordeev
2024-10-01 11:52         ` Parav Pandit
2024-10-09  8:47           ` Aiswarya Cyriac (QUIC)
2024-10-30  8:15             ` Parav Pandit
2024-10-30 10:31               ` Aiswarya Cyriac (QUIC)
2024-10-30 10:38               ` Aiswarya Cyriac (QUIC)
2024-10-31  5:41                 ` Parav Pandit
2024-11-03  5:09                   ` Parav Pandit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ikucrysk.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=acourbot@chromium.org \
    --cc=aesteve@redhat.com \
    --cc=aiswarya.cyriac@opensynergy.com \
    --cc=parav@nvidia.com \
    --cc=virtio-comment@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.