From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Hilber <peter.hilber@oss.qualcomm.com>
Cc: virtio-comment@lists.linux.dev,
Trilok Soni <trilok.soni@oss.qualcomm.com>
Subject: Re: [PATCH] content: Reserve ID 52 for Snapdragon device
Date: Thu, 27 Aug 2026 20:51:05 +0200 [thread overview]
Message-ID: <78ffb169-e9ce-44f2-b18c-6311354fab3c@siemens.com> (raw)
In-Reply-To: <cptr5hczrpslq7wtrbd2pfbz247k2e3b6rvali2foaueeanymr@n6xtsyl4lq6m>
On 27.08.26 18:17, Peter Hilber wrote:
> On Wed, Aug 26, 2026 at 05:31:54PM +0200, Jan Kiszka wrote:
>> On 26.08.26 13:55, Peter Hilber wrote:
>>> Reserve a device ID for the Snapdragon device. A Virtio Snapdragon
>>> device exposes functionality across Snapdragon SoC subsystems through a
>>> common Virtio-based protocol.
>>>
>>
>> Virtio is supposed to provide generic hardware models, not so much a
>> channel to expose concrete, physical chip IP over it. This looks very
>> weird to me.
>
> The Snapdragon device is not planned to undergo standardization, so it
> should be acceptable as argued by Stefan. Qualcomm has some Linux
> kernel Virtio drivers which are intended for upstreaming, and as such
> need a reserved device ID.
>
Thanks for confirming.
But I'm personally not convinced that this is a pattern the virtio
specification should support, even if we had plenty of free space. It is
one thing to reserve an ID for a conceptually hardware-agnostic device
type where there is at least the possibility to standardize this one
day. But doing that for a single-vendor hardware which is likely not to
survive very long (seen that way too often...), this just seems wrong.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
prev parent reply other threads:[~2026-08-27 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 11:55 [PATCH] content: Reserve ID 52 for Snapdragon device Peter Hilber
2026-08-26 15:31 ` Jan Kiszka
2026-08-26 18:44 ` Stefan Hajnoczi
2026-08-27 13:24 ` Jan Kiszka
2026-08-27 14:49 ` Stefan Hajnoczi
2026-08-27 16:17 ` Peter Hilber
2026-08-27 18:51 ` Jan Kiszka [this message]
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=78ffb169-e9ce-44f2-b18c-6311354fab3c@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=peter.hilber@oss.qualcomm.com \
--cc=trilok.soni@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox