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, viresh.kumar@linaro.org
Cc: quic_ztu@quicinc.com
Subject: Re: [virtio-dev] [PATCH V6 2/2] virtio-spi: add the device specification
Date: Wed, 06 Dec 2023 15:33:51 +0100 [thread overview]
Message-ID: <8734wfienk.fsf@redhat.com> (raw)
In-Reply-To: <9bf22a9a-1885-411e-951e-a22bf828da88@quicinc.com>
On Mon, Dec 04 2023, Haixu Cui <quic_haixcui@quicinc.com> wrote:
> Hi Huck,
>
> On 12/1/2023 7:01 PM, Cornelia Huck wrote:
>> On Fri, Dec 01 2023, Haixu Cui <quic_haixcui@quicinc.com> wrote:
>>
>>>>> +Note: chipselect is an electrical signal controlled by the SPI controller, used to select the
>>>>> +SPI slaves connected to the controller.
>>>>
>>>> I wonder whether another term is now more commonly used... the Wikipedia
>>>> article uses main/sub, is there a term that is usually used together
>>>> with "controller"?
>>>
>>> In Wikipedia,
>>>
>>> "Historically, this arrangement has been called master/slave. But to
>>> avoid referencing slavery, alternative names discussed in § Alternative
>>> namings have been used."
>>>
>>> I am not quite sure if main/sub is widely used, but in latest Linux,
>>> still use master/slave but master is gradually replaced by "controller".
>>>
>>> So I think "controller" here does make sense. What is your suggestion?
>>
>> "controller" is fine, I'm just wondering if "slave" has started to be
>> replaced with something else as well... if it hasn't, we probably need
>> to stick with it to avoid confusing readers.
>>
>
> slave is still being used, but it's better to be used along with "master".
>
> Here I prefer using "SPI peripherals" instead of "SPI slaves". Looking
> forward to your advice. Thank you so much.
"SPI peripherals" sounds good to me.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2023-12-06 14:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 9:22 [virtio-dev] [PATCH V6 0/2] virtio-spi: add virtual SPI controller Haixu Cui
2023-11-30 9:22 ` [virtio-dev] [PATCH V6 1/2] content: Rename SPI master to " Haixu Cui
2023-11-30 10:04 ` Viresh Kumar
2023-11-30 9:22 ` [virtio-dev] [PATCH V6 2/2] virtio-spi: add the device specification Haixu Cui
2023-11-30 11:19 ` Viresh Kumar
2023-12-01 4:05 ` Haixu Cui
2023-12-01 4:32 ` Viresh Kumar
2023-12-01 5:35 ` Haixu Cui
2023-12-01 5:44 ` Viresh Kumar
2023-12-01 5:49 ` Haixu Cui
2023-11-30 11:38 ` Cornelia Huck
2023-12-01 4:25 ` Haixu Cui
2023-12-01 11:01 ` Cornelia Huck
2023-12-04 2:24 ` Haixu Cui
2023-12-06 14:33 ` Cornelia Huck [this message]
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=8734wfienk.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=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 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).