All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Haixu Cui <quic_haixcui@quicinc.com>
Cc: virtio-dev@lists.oasis-open.org,
	virtio-comment@lists.oasis-open.org,
	harald.mommer@opensynergy.com, broonie@kernel.org,
	qiang4.zhang@linux.intel.com, quic_ztu@quicinc.com,
	alex.bennee@linaro.org, vincent.guittot@linaro.org
Subject: Re: [virtio-comment] [PATCH] [PATCH v5] virtio-spi: add the device specification
Date: Wed, 29 Nov 2023 13:42:08 +0100	[thread overview]
Message-ID: <87y1egwx27.fsf@redhat.com> (raw)
In-Reply-To: <20231129113417.7kb6my3mm67zal3q@vireshk-i7>

On Wed, Nov 29 2023, Viresh Kumar <viresh.kumar@linaro.org> wrote:

> On 29-11-23, 18:31, Haixu Cui wrote:
>> Hi Viresh,
>> 
>>     Thank you for your helpful comments. In next patch, I will clearly point
>> this out:
>
> Great, finally we are on the same page. Thanks Haixu.
>
>>     "For full-duplex read and write transfer, both \field{tx_buf} and
>> \field{rx_buf} are used and the buffer size of \field{tx_buf} must be same
>> as \field{rx_buf}."
>
> Suggest rewriting as:
>
> In full-duplex transfer mode, both \field{tx_buf} and \field{rx_buf} are sent by
> the driver, \field{tx_buf} followed by \field{rx_buf}. The length of both the
> buffers MUST be same.

Is that in a non-normative section? (Sorry, I've lost track here...) If
so, I would say:

"The length of both buffers has to be the same."

>
>>     And in drivernormative section, I will add a requirement:
>>     "For full-duplex transfer, Virtio SPI driver MUST guarantee the write
>> transfer size is equal to the read transfer size"
>
> Maybe:
>
> drivernormative:
>
> In full-duplex transfer mode, the Virtio SPI driver MUST guarantee that the
> length of both \field{tx_buf} and \field{rx_buf} are same.

s/are same/is the same/

>
> devicenormative:
>
> In full-duplex transfer mode, the Virtio SPI device MUST verify that the length
> of both \field{tx_buf} and \field{rx_buf} are same. In case of any mismatch, the

s/are same/is the same/

> device MUST fail the transfer and notify the driver.

"notify the driver" == "set an appropriate error value"?

Can this be covered by one of the existing error values?


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: Viresh Kumar <viresh.kumar@linaro.org>,
	Haixu Cui <quic_haixcui@quicinc.com>
Cc: virtio-dev@lists.oasis-open.org,
	virtio-comment@lists.oasis-open.org,
	harald.mommer@opensynergy.com, broonie@kernel.org,
	qiang4.zhang@linux.intel.com, quic_ztu@quicinc.com,
	alex.bennee@linaro.org, vincent.guittot@linaro.org
Subject: [virtio-dev] Re: [virtio-comment] [PATCH] [PATCH v5] virtio-spi: add the device specification
Date: Wed, 29 Nov 2023 13:42:08 +0100	[thread overview]
Message-ID: <87y1egwx27.fsf@redhat.com> (raw)
In-Reply-To: <20231129113417.7kb6my3mm67zal3q@vireshk-i7>

On Wed, Nov 29 2023, Viresh Kumar <viresh.kumar@linaro.org> wrote:

> On 29-11-23, 18:31, Haixu Cui wrote:
>> Hi Viresh,
>> 
>>     Thank you for your helpful comments. In next patch, I will clearly point
>> this out:
>
> Great, finally we are on the same page. Thanks Haixu.
>
>>     "For full-duplex read and write transfer, both \field{tx_buf} and
>> \field{rx_buf} are used and the buffer size of \field{tx_buf} must be same
>> as \field{rx_buf}."
>
> Suggest rewriting as:
>
> In full-duplex transfer mode, both \field{tx_buf} and \field{rx_buf} are sent by
> the driver, \field{tx_buf} followed by \field{rx_buf}. The length of both the
> buffers MUST be same.

Is that in a non-normative section? (Sorry, I've lost track here...) If
so, I would say:

"The length of both buffers has to be the same."

>
>>     And in drivernormative section, I will add a requirement:
>>     "For full-duplex transfer, Virtio SPI driver MUST guarantee the write
>> transfer size is equal to the read transfer size"
>
> Maybe:
>
> drivernormative:
>
> In full-duplex transfer mode, the Virtio SPI driver MUST guarantee that the
> length of both \field{tx_buf} and \field{rx_buf} are same.

s/are same/is the same/

>
> devicenormative:
>
> In full-duplex transfer mode, the Virtio SPI device MUST verify that the length
> of both \field{tx_buf} and \field{rx_buf} are same. In case of any mismatch, the

s/are same/is the same/

> device MUST fail the transfer and notify the driver.

"notify the driver" == "set an appropriate error value"?

Can this be covered by one of the existing error values?


---------------------------------------------------------------------
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-11-29 12:42 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       ` [virtio-comment] " Cornelia Huck
2023-11-27 14:33         ` [virtio-dev] " 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 [this message]
2023-11-29 12:42                     ` 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=87y1egwx27.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alex.bennee@linaro.org \
    --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=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.org \
    --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.