From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Francesco Valla" <francesco@valla.it>,
"Mark Brown" <broonie@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Haixu Cui" <quic_haixcui@quicinc.com>,
"Jason Wang" <jasowangio@gmail.com>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev
Subject: Re: [PATCH v2 0/2] Add devicetree bindings for spi-virtio
Date: Thu, 29 Oct 2026 09:21:59 +0100 [thread overview]
Message-ID: <20261029-tactful-able-moose-e61a2d@quoll> (raw)
In-Reply-To: <20261027090324-mutt-send-email-mst@kernel.org>
On Tue, Oct 27, 2026 at 09:07:47AM -0400, Michael S. Tsirkin wrote:
> On Tue, Oct 27, 2026 at 01:46:35PM +0100, Francesco Valla wrote:
> > Hello Michael,
> >
> > On Tue, Oct 27, 2026 at 06:50:51AM -0400, Michael S. Tsirkin wrote:
> > > On Tue, Oct 27, 2026 at 08:26:32AM +0100, Francesco Valla wrote:
> > > > When a virtio transport exposes a non-discoverable bus, the devicetree
> > > > can be used to declare its child devices (if any) and/or other
> > > > properties. To allow for that, the virtio framework searches for a node
> > > > with a suitable compatible in virtio_device_of_init() when registering
> > > > a device [1]; such compatible takes the form "virtio,deviceXX", where
> > > > XX is the hexadecimal representation of the virtio device ID as defined
> > > > by the virtio specification.
> > > >
> > > > This patchset thus does not introduce a new functionality, but allows
> > > > proper validation of nodes tied to spi-virtio devices, aligning SPI to
> > > > what is already being done for e.g. I2C and GPIO virtio devices.
> > > > It was sent initially as part of a different patchset [2], but since it
> > > > complements a functionality that is de-facto already there and is useful
> > > > beyond that specific use case it was sent separately (also following the
> > > > maintainer's feedback there to separate it from remoteproc-specific
> > > > changes).
> > > >
> > > > This was tested both with virtio-mmio using qemu-system-aarch64 and with
> > > > remoteproc-virtio with a Zephyr backend (with relevant remoteproc-virtio
> > > > parts still not not upstreamed - see [2]).
> > > >
> > > > I added myself as reviewer for the spi-virtio driver to be CC'd on any
> > > > patch involving the new bindings.
> > > >
> > > > Thank you!
> > > >
> > > > Regards,
> > > > Francesco
> > > >
> > > > [1] https://elixir.bootlin.com/linux/v7.2.8/source/drivers/virtio/virtio.c#L488
> > > > [2] https://lore.kernel.org/linux-remoteproc/20260916-remoteproc_virtio_map-v1-0-dac8c5eb4aa9@valla.it/
> > > >
> > > > Signed-off-by: Francesco Valla <francesco@valla.it>
> > > > ---
> > >
> > > I hope this can be merged through the devicetree maintainers,
> > > I have no idea.
> > > MAINTAINERS changes needs an ack from existing maintainers, of
> > > course.
> > >
> >
> > This might prove... difficult. My e-mails to the maintainer (Haixu Cui
> > @quicinc.com) continue to be bounced back by the Qualcomm postmaster
> > with a RecipientNotFound error. Maybe someone from Qualcomm can give me
> > a lead on how to contact them?
>
> Indeed, so it did for me. Oh that's no good at all.
>
> Mark, what's your take? The maintainer is MIA but we have a volunteer
> maintainer here.
>
> As far as I'm concerned
>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
All @quicinc.com emails stopped working long time ago and Qualcomm
engineers were asked to update their emails. Most did the update, so if
nothing happened here, let's make it orphaned and then Francesco can
take it over.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-10-29 8:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 7:26 [PATCH v2 0/2] Add devicetree bindings for spi-virtio Francesco Valla
2026-10-27 7:26 ` [PATCH v2 1/2] dt-bindings: spi: add spi-virtio Francesco Valla
2026-10-29 8:29 ` Krzysztof Kozlowski
2026-10-29 10:53 ` Mark Brown
2026-10-29 10:55 ` Krzysztof Kozlowski
2026-10-27 7:26 ` [PATCH v2 2/2] MAINTAINERS: add Francesco as spi-virtio reviewer Francesco Valla
2026-10-29 8:26 ` Krzysztof Kozlowski
2026-10-29 10:13 ` Michael S. Tsirkin
2026-10-27 10:50 ` [PATCH v2 0/2] Add devicetree bindings for spi-virtio Michael S. Tsirkin
2026-10-27 12:46 ` Francesco Valla
2026-10-27 13:07 ` Michael S. Tsirkin
2026-10-29 8:21 ` Krzysztof Kozlowski [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=20261029-tactful-able-moose-e61a2d@quoll \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eperezma@redhat.com \
--cc=francesco@valla.it \
--cc=jasowangio@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mst@redhat.com \
--cc=quic_haixcui@quicinc.com \
--cc=robh@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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