From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AFAF5C4167B for ; Mon, 27 Nov 2023 14:33:31 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id 026BE217B4 for ; Mon, 27 Nov 2023 14:33:31 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id D7E85986553 for ; Mon, 27 Nov 2023 14:33:30 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id BDBD29863BE; Mon, 27 Nov 2023 14:33:30 +0000 (UTC) Mailing-List: contact virtio-comment-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id A3F459863A4 for ; Mon, 27 Nov 2023 14:33:30 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: IdzK68UgPHqwjDQh2ZswJg-1 From: Cornelia Huck To: Haixu Cui , 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 In-Reply-To: <87il5nxof1.fsf@redhat.com> Organization: "Red Hat GmbH, Sitz: Werner-von-Siemens-Ring 12, D-85630 Grasbrunn, Handelsregister: Amtsgericht =?utf-8?Q?M=C3=BCnchen=2C?= HRB 153243, =?utf-8?Q?Gesch=C3=A4ftsf=C3=BChrer=3A?= Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross" References: <20231124072015.12655-1-quic_haixcui@quicinc.com> <87ttpbxiga.fsf@redhat.com> <87il5nxof1.fsf@redhat.com> User-Agent: Notmuch/0.37 (https://notmuchmail.org) Date: Mon, 27 Nov 2023 15:33:18 +0100 Message-ID: <87fs0rxo41.fsf@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.10 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: Re: [virtio-comment] Re: [PATCH] [PATCH v5] virtio-spi: add the device specification On Mon, Nov 27 2023, Cornelia Huck wrote: > On Mon, Nov 27 2023, Haixu Cui wrote: > >> On 11/24/2023 11:46 PM, Cornelia Huck wrote: >>> On Fri, Nov 24 2023, Haixu Cui 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/ From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 66025C4167B for ; Mon, 27 Nov 2023 14:33:25 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id C1CC52A8F0 for ; Mon, 27 Nov 2023 14:33:24 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 9F04D9863BD for ; Mon, 27 Nov 2023 14:33:24 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id 7E63A9863A1; Mon, 27 Nov 2023 14:33:24 +0000 (UTC) Mailing-List: contact virtio-dev-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 6E85E9863A4 for ; Mon, 27 Nov 2023 14:33:24 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: IdzK68UgPHqwjDQh2ZswJg-1 From: Cornelia Huck To: Haixu Cui , 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 In-Reply-To: <87il5nxof1.fsf@redhat.com> Organization: "Red Hat GmbH, Sitz: Werner-von-Siemens-Ring 12, D-85630 Grasbrunn, Handelsregister: Amtsgericht =?utf-8?Q?M=C3=BCnchen=2C?= HRB 153243, =?utf-8?Q?Gesch=C3=A4ftsf=C3=BChrer=3A?= Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross" References: <20231124072015.12655-1-quic_haixcui@quicinc.com> <87ttpbxiga.fsf@redhat.com> <87il5nxof1.fsf@redhat.com> User-Agent: Notmuch/0.37 (https://notmuchmail.org) Date: Mon, 27 Nov 2023 15:33:18 +0100 Message-ID: <87fs0rxo41.fsf@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.10 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: [virtio-dev] Re: [virtio-comment] Re: [PATCH] [PATCH v5] virtio-spi: add the device specification On Mon, Nov 27 2023, Cornelia Huck wrote: > On Mon, Nov 27 2023, Haixu Cui wrote: > >> On 11/24/2023 11:46 PM, Cornelia Huck wrote: >>> On Fri, Nov 24 2023, Haixu Cui 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