From: Harald Mommer <Harald.Mommer@opensynergy.com>
To: virtio-dev@lists.oasis-open.org,
Haixu Cui <quic_haixcui@quicinc.com>,
Mark Brown <broonie@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: quic_ztu@quicinc.com, Matti Moell <Matti.Moell@opensynergy.com>,
Mikhail Golubev <Mikhail.Golubev@opensynergy.com>
Subject: [RFC PATCH v2 0/3] Virtio SPI Linux driver compliant to draft spec V10
Date: Thu, 4 Jan 2024 14:01:26 +0100 [thread overview]
Message-ID: <20240104130129.17823-1-Harald.Mommer@opensynergy.com> (raw)
This is the 2nd RFC version of a virtio SPI Linux driver which is
intended to be compliant with the proposed virtio SPI draft
specification V10.
The 1st RFC version sent out publicly was compliant to the virtio draft
specification V4.
Changes between 1st and 2nd virtio SPI driver RFC:
- Update to be compliant to virtio SPI draft specification V10.
- Incorporated review comments gotten from the community.
A proposal for a performance enhancement having more than only one SPI
message in flight had to be kept out. The more complicated code would
have caused an unacceptable project risk now.
The virtio SPI driver was smoke tested on qemu using OpenSynergy's
proprietary virtio SPI device doing a SPI backend simulation on top of
next-20240103 and an adapted version on Linux 6.1 with target hardware
providing a physical SPI backend device.
next reply other threads:[~2024-01-04 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 13:01 Harald Mommer [this message]
2024-01-04 13:01 ` [RFC PATCH v2 1/3] virtio: Add ID for virtio SPI Harald Mommer
2024-01-29 6:30 ` Viresh Kumar
2024-01-04 13:01 ` [RFC PATCH v2 2/3] virtio-spi: Add virtio-spi.h (V10 draft specification) Harald Mommer
2024-01-29 6:39 ` Viresh Kumar
2024-01-04 13:01 ` [RFC PATCH v2 3/3] SPI: Add virtio SPI driver " Harald Mommer
2024-01-29 7:06 ` Viresh Kumar
2024-01-30 14:24 ` Harald Mommer
2024-01-30 3:21 ` Haixu Cui
2024-02-01 17:26 ` [virtio-dev] " Harald Mommer
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=20240104130129.17823-1-Harald.Mommer@opensynergy.com \
--to=harald.mommer@opensynergy.com \
--cc=Matti.Moell@opensynergy.com \
--cc=Mikhail.Golubev@opensynergy.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=quic_haixcui@quicinc.com \
--cc=quic_ztu@quicinc.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-dev@lists.oasis-open.org \
/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;
as well as URLs for NNTP newsgroup(s).