virtio-dev.lists.oasis-open.org archive mirror
 help / color / mirror / Atom feed
From: Haixu Cui <quic_haixcui@quicinc.com>
To: Cornelia Huck <cohuck@redhat.com>,
	<virtio-dev@lists.oasis-open.org>,
	<virtio-comment@lists.oasis-open.org>
Cc: <quic_ztu@quicinc.com>
Subject: Re: [virtio-dev] [PATCH] virtio-spi: add the device specification
Date: Fri, 24 Mar 2023 16:14:19 +0800	[thread overview]
Message-ID: <9cd01fb9-f7a4-7d5a-bfef-6d1eb810e2d2@quicinc.com> (raw)
In-Reply-To: <87h6umta2t.fsf@redhat.com>

Hi Cornelia Huck,
     Thank you for your comments.
     SPI here means 'Serial Peripheral Interface'. And according to your 
suggestion, I submit again to remove the introduction of Virtio ID.

Best Regards
Haixu Cui


On 3/15/2023 9:31 PM, Cornelia Huck wrote:
> On Mon, Feb 27 2023, Haixu Cui <quic_haixcui@quicinc.com> wrote:
> 
>> virtio-spi is a virtual SPI master and it allows a guset to operate and
>> use the physical SPI master controlled by the host.
>>
>> Signed-off-by: Haixu Cui <quic_haixcui@quicinc.com>
>> ---
>>   content.tex                             |   2 +
>>   device-types/spi/description.tex        | 153 ++++++++++++++++++++++++
>>   device-types/spi/device-conformance.tex |   7 ++
>>   device-types/spi/driver-conformance.tex |   7 ++
>>   4 files changed, 169 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
>>
>> diff --git a/content.tex b/content.tex
>> index 0c7cdf8..86bf709 100644
>> --- a/content.tex
>> +++ b/content.tex
>> @@ -2994,6 +2994,8 @@ \chapter{Device Types}\label{sec:Device Types}
>>   \hline
>>   44         &   ISM device \\
>>   \hline
>> +45         &   SPI Master \\
> 
> What is 'SPI'? 'Serial Peripheral Interface', I guess?
> 
> Introduction of the ID should be split out into a separate patch; if
> people agree that this is a useful thing to add, please open a github
> issue and request a vote.
> 
>> +\hline
>>   \end{tabular}
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2023-03-24  8:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27  8:23 [virtio-dev] [PATCH] virtio-spi: add the device specification Haixu Cui
2023-02-27  8:23 ` Haixu Cui
2023-03-15 13:31 ` Cornelia Huck
2023-03-24  8:14   ` Haixu Cui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-24  8:08 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=9cd01fb9-f7a4-7d5a-bfef-6d1eb810e2d2@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).