From: Cornelia Huck <cohuck@redhat.com>
To: Haixu Cui <quic_haixcui@quicinc.com>,
virtio-dev@lists.oasis-open.org,
virtio-comment@lists.oasis-open.org,
harald.mommer@opensynergy.com, broonie@kernel.org,
qiang4.zhang@linux.intel.com
Cc: quic_ztu@quicinc.com
Subject: Re: [virtio-comment] Re: [PATCH] [PATCH v5] virtio-spi: add the device specification
Date: Mon, 27 Nov 2023 15:33:18 +0100 [thread overview]
Message-ID: <87fs0rxo41.fsf@redhat.com> (raw)
In-Reply-To: <87il5nxof1.fsf@redhat.com>
On Mon, Nov 27 2023, Cornelia Huck <cohuck@redhat.com> wrote:
> On Mon, Nov 27 2023, Haixu Cui <quic_haixcui@quicinc.com> wrote:
>
>> On 11/24/2023 11:46 PM, Cornelia Huck wrote:
>>> On Fri, Nov 24 2023, Haixu Cui <quic_haixcui@quicinc.com> wrote:
>>>> +The \field{chip_select_max_number} is the maximum number of chipselect the host SPI controller supports.
>>>
>>> "chipselect" is probably a known term for people familiar with SPI -- is
>>> there any definition of those terms that the spec can point to?
>>
>> Just as Mark said, there is no formal spec for SPI, so no standard spec
>> for such terms referring to. The same for CPHA/CPOL/LSB/MSB, please see
>> below.
>
> If we have nothing to point to, it is probably best to simply
> expand/explain the terms on their first usage.
>
>>> Can we point to some documentation that explains CPHA and CPOL?
>>
>> Here. No standard SPI spec to point to. CPOL/CPHA have definitions in
>> wikipedia(Clock polarity and phase chapter):
>>
>> https://en.wikipedia.org/wiki/Serial_Peripheral_Interface
>>
>> How about copying some concise information from wikipedia as Note? Or is
>> referring to such webpage acceptable in this spec.
>
> Not sure if we can do an outright copy (licence compatibility), but
> paraphrasing should be fine. (I'd rather not directly reference the
> site, because the content is not guaranteed to be stable, but we could
> maybe add it as "further reading".)
Looking again, the kernel doc referenced by Mark
(https://www.kernel.org/doc/html/v6.6/driver-api/spi.html) might also be
a good candidate, especially as we can refer to a specific version.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com>
To: Haixu Cui <quic_haixcui@quicinc.com>,
virtio-dev@lists.oasis-open.org,
virtio-comment@lists.oasis-open.org,
harald.mommer@opensynergy.com, broonie@kernel.org,
qiang4.zhang@linux.intel.com
Cc: quic_ztu@quicinc.com
Subject: [virtio-dev] Re: [virtio-comment] Re: [PATCH] [PATCH v5] virtio-spi: add the device specification
Date: Mon, 27 Nov 2023 15:33:18 +0100 [thread overview]
Message-ID: <87fs0rxo41.fsf@redhat.com> (raw)
In-Reply-To: <87il5nxof1.fsf@redhat.com>
On Mon, Nov 27 2023, Cornelia Huck <cohuck@redhat.com> wrote:
> On Mon, Nov 27 2023, Haixu Cui <quic_haixcui@quicinc.com> wrote:
>
>> On 11/24/2023 11:46 PM, Cornelia Huck wrote:
>>> On Fri, Nov 24 2023, Haixu Cui <quic_haixcui@quicinc.com> wrote:
>>>> +The \field{chip_select_max_number} is the maximum number of chipselect the host SPI controller supports.
>>>
>>> "chipselect" is probably a known term for people familiar with SPI -- is
>>> there any definition of those terms that the spec can point to?
>>
>> Just as Mark said, there is no formal spec for SPI, so no standard spec
>> for such terms referring to. The same for CPHA/CPOL/LSB/MSB, please see
>> below.
>
> If we have nothing to point to, it is probably best to simply
> expand/explain the terms on their first usage.
>
>>> Can we point to some documentation that explains CPHA and CPOL?
>>
>> Here. No standard SPI spec to point to. CPOL/CPHA have definitions in
>> wikipedia(Clock polarity and phase chapter):
>>
>> https://en.wikipedia.org/wiki/Serial_Peripheral_Interface
>>
>> How about copying some concise information from wikipedia as Note? Or is
>> referring to such webpage acceptable in this spec.
>
> Not sure if we can do an outright copy (licence compatibility), but
> paraphrasing should be fine. (I'd rather not directly reference the
> site, because the content is not guaranteed to be stable, but we could
> maybe add it as "further reading".)
Looking again, the kernel doc referenced by Mark
(https://www.kernel.org/doc/html/v6.6/driver-api/spi.html) might also be
a good candidate, especially as we can refer to a specific version.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-11-27 14:33 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 7:20 [virtio-comment] [PATCH] [PATCH v5] virtio-spi: add the device specification Haixu Cui
2023-11-24 7:20 ` [virtio-dev] " Haixu Cui
2023-11-24 15:46 ` [virtio-comment] " Cornelia Huck
2023-11-24 15:46 ` [virtio-dev] " Cornelia Huck
2023-11-27 13:14 ` [virtio-comment] " Haixu Cui
2023-11-27 13:14 ` [virtio-dev] " Haixu Cui
2023-11-27 14:26 ` [virtio-comment] " Cornelia Huck
2023-11-27 14:26 ` [virtio-dev] " Cornelia Huck
2023-11-27 14:33 ` Cornelia Huck [this message]
2023-11-27 14:33 ` [virtio-dev] Re: [virtio-comment] " Cornelia Huck
2023-11-28 12:23 ` Haixu Cui
2023-11-28 12:23 ` [virtio-dev] " Haixu Cui
2023-11-28 12:32 ` Haixu Cui
2023-11-28 12:32 ` [virtio-dev] " Haixu Cui
2023-11-27 10:17 ` [virtio-comment] " Viresh Kumar
2023-11-27 10:17 ` [virtio-dev] " Viresh Kumar
2023-11-28 12:58 ` Haixu Cui
2023-11-28 12:58 ` [virtio-dev] " Haixu Cui
2023-11-29 7:30 ` Viresh Kumar
2023-11-29 7:30 ` [virtio-dev] " Viresh Kumar
2023-11-29 8:19 ` Haixu Cui
2023-11-29 8:19 ` [virtio-dev] " Haixu Cui
2023-11-29 8:33 ` Cornelia Huck
2023-11-29 8:33 ` [virtio-dev] " Cornelia Huck
2023-11-29 8:54 ` Haixu Cui
2023-11-29 8:54 ` [virtio-dev] " Haixu Cui
2023-11-29 10:00 ` Viresh Kumar
2023-11-29 10:00 ` [virtio-dev] " Viresh Kumar
2023-11-29 10:31 ` Haixu Cui
2023-11-29 10:31 ` [virtio-dev] " Haixu Cui
2023-11-29 11:34 ` Viresh Kumar
2023-11-29 11:34 ` [virtio-dev] " Viresh Kumar
2023-11-29 12:42 ` Cornelia Huck
2023-11-29 12:42 ` [virtio-dev] " Cornelia Huck
2023-11-30 4:13 ` Viresh Kumar
2023-11-30 4:13 ` [virtio-dev] " Viresh Kumar
2023-11-30 7:36 ` Haixu Cui
2023-11-30 7:36 ` [virtio-dev] " Haixu Cui
2023-11-30 7:32 ` Haixu Cui
2023-11-30 7:32 ` [virtio-dev] " Haixu Cui
2023-11-30 16:43 ` Jonathon Reinhart
[not found] ` <ZWCbm4pDET31Rn7z@finisterre.sirena.org.uk>
2023-11-27 12:20 ` [virtio-comment] " Haixu Cui
2023-11-27 12:20 ` [virtio-dev] " 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=87fs0rxo41.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=broonie@kernel.org \
--cc=harald.mommer@opensynergy.com \
--cc=qiang4.zhang@linux.intel.com \
--cc=quic_haixcui@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.