From: Haixu Cui <quic_haixcui@quicinc.com>
To: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
<broonie@kernel.org>, <virtio-dev@lists.linux.dev>,
<viresh.kumar@linaro.org>, <linux-spi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <hdanton@sina.com>,
<qiang4.zhang@linux.intel.com>, <alex.bennee@linaro.org>
Cc: <quic_ztu@quicinc.com>
Subject: Re: [RFC PATCH v5 2/3] virtio-spi: Add virtio-spi.h
Date: Fri, 4 Jul 2025 14:54:08 +0800 [thread overview]
Message-ID: <80b54138-b5ae-49db-8e94-42de6de05bf8@quicinc.com> (raw)
In-Reply-To: <1382320e-e5ae-47c4-be82-ab438032eac4@quicinc.com>
On 6/30/2025 2:59 PM, Mukesh Kumar Savaliya wrote:
>
>
> On 6/20/2025 9:42 AM, Haixu Cui wrote:
>> Add virtio-spi.h header for virtio SPI.
>>
>> Signed-off-by: Haixu Cui <quic_haixcui@quicinc.com>
>> ---
>> include/uapi/linux/virtio_spi.h | 185 ++++++++++++++++++++++++++++++++
>> 1 file changed, 185 insertions(+)
>> create mode 100644 include/uapi/linux/virtio_spi.h
>> + * @max_cs_setup_ns: the maximum delay supported after chipselect is
>> asserted,
> And before clock start. may also sound good, if we can write "delay
> between CS assert to clock start"
I follow the existing comment in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/spi/spi.h?h=v6.16-rc4#n166,
where the cs_setup is described only in terms of the delay after CS is
asserted, without explicitly referencing the clock signal.
To maintain consistency, I kept the comment focused on the relationship
between the delay and the CS signal alone.
next prev parent reply other threads:[~2025-07-04 6:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 4:12 [RFC PATCH v5 0/3] Virtio SPI Linux driver Haixu Cui
2025-06-20 4:12 ` [RFC PATCH v5 1/3] virtio: Add ID for virtio SPI Haixu Cui
2025-06-20 4:12 ` [RFC PATCH v5 2/3] virtio-spi: Add virtio-spi.h Haixu Cui
2025-06-30 6:59 ` Mukesh Kumar Savaliya
2025-07-04 6:54 ` Haixu Cui [this message]
2025-06-20 4:12 ` [RFC PATCH v5 3/3] SPI: Add virtio SPI driver Haixu Cui
2025-06-30 6:54 ` Mukesh Kumar Savaliya
2025-07-04 7:46 ` 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=80b54138-b5ae-49db-8e94-42de6de05bf8@quicinc.com \
--to=quic_haixcui@quicinc.com \
--cc=alex.bennee@linaro.org \
--cc=broonie@kernel.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=qiang4.zhang@linux.intel.com \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_ztu@quicinc.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-dev@lists.linux.dev \
/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
all inboxes | Powered by JetHome®