From: Haixu Cui <quic_haixcui@quicinc.com>
To: <virtio-comment@lists.oasis-open.org>,
<virtio-dev@lists.oasis-open.org>, <cohuck@redhat.com>
Cc: <quic_ztu@quicinc.com>, Haixu Cui <quic_haixcui@quicinc.com>
Subject: [virtio-dev][PATCH 0/2] virtio-spi: add virtual SPI master
Date: Mon, 5 Jun 2023 17:24:01 +0800 [thread overview]
Message-ID: <20230605092403.17406-1-quic_haixcui@quicinc.com> (raw)
virtio-spi is a virtual SPI(Serial Peripheral Interface) master and
it allows a guset to operate and use the physical SPI master controlled
by the host.
Patch summary:
patch 1 define the DEVICE ID for virtio-spi
patch 2 add the specification for virtio-spi
Haixu Cui (2):
virtio-spi: define the DEVICE ID for virtio SPI master
virtio-spi: add the device specification
content.tex | 2 +
device-types/spi/description.tex | 152 ++++++++++++++++++++++++
device-types/spi/device-conformance.tex | 7 ++
device-types/spi/driver-conformance.tex | 7 ++
4 files changed, 168 insertions(+)
create mode 100644 device-types/spi/description.tex
create mode 100644 device-types/spi/device-conformance.tex
create mode 100644 device-types/spi/driver-conformance.tex
--
2.17.1
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next reply other threads:[~2023-06-05 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 9:24 Haixu Cui [this message]
2023-06-05 9:24 ` [virtio-dev][PATCH 1/2] virtio-spi: define the DEVICE ID for virtio SPI master Haixu Cui
2023-06-05 9:24 ` [virtio-dev][PATCH 2/2] virtio-spi: add the device specification Haixu Cui
-- strict thread matches above, loose matches on Subject: below --
2023-04-17 14:03 [virtio-dev][PATCH 0/2] virtio-spi: add virtual SPI master Haixu Cui
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=20230605092403.17406-1-quic_haixcui@quicinc.com \
--to=quic_haixcui@quicinc.com \
--cc=cohuck@redhat.com \
--cc=quic_ztu@quicinc.com \
--cc=virtio-comment@lists.oasis-open.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 read-only IMAP folder(s) and NNTP newsgroup(s).