From: Alex Elder <elder@ieee.org>
To: Mark Brown <broonie@kernel.org>, Guodong Xu <guodong@riscstar.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Yixun Lan <dlan@kernel.org>,
Alex Elder <elder@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org, Alex Elder <elder@riscstar.com>
Subject: Re: [PATCH v9 2/3] spi: spacemit: introduce SpacemiT K1 SPI controller driver
Date: Wed, 29 Apr 2026 14:06:11 -0500 [thread overview]
Message-ID: <856f4e8d-ff7c-4744-9624-e838c758f009@ieee.org> (raw)
In-Reply-To: <ae_8n0I_ORDLib1y@sirena.co.uk>
On 4/27/26 7:17 PM, Mark Brown wrote:
> On Mon, Apr 27, 2026 at 10:01:28PM -0400, Guodong Xu wrote:
>
>> +static int k1_spi_transfer_one(struct spi_controller *host,
>> + struct spi_device *spi,
>> + struct spi_transfer *transfer)
>> +{
>
>> + /* Record how many words the len bytes represent */
>> + count = transfer->len / drv_data->bytes;
>> + drv_data->rx_resid = count;
>> + drv_data->tx_resid = count;
>
> This is setting up _resid with a number of words.
Guodong, see below, but I think the above should be:
drv_data->rx_resid = transfer->len;
drv_data->tx_resid = transfer->len;
>> +static void k1_spi_write_word(struct k1_spi_driver_data *drv_data)
>> +{
>> + struct spi_transfer *transfer = drv_data->transfer;
>> + u32 bytes = drv_data->bytes;
>> + u32 val;
>> +
>> + if (transfer->tx_buf) {
>> + const void *buf;
>> +
>> + buf = transfer->tx_buf + (transfer->len - drv_data->tx_resid);
>
> This is using _resid as a byte count. It'll be fine for 8 bits per word
> (which is by far the most common thing).
You're right, this is a really great observation.
The best thing is probably to just have the *_resid symbols
represent bytes. (Their definitions in the structure say
that as well.)
k1_spi_write_word() decrements tx_resid by the number of
bytes transferred, so that's OK.
But the FIFO handles words, and k1_spi_write() limits the number
of *words* transferred, so the "count" calculation there needs to
take the word size into account. Something like:
/**/ unsigned int resid_words;
unsigned int count;
/* Get the number of open slots in the FIFO; zero means all */
count = FIELD_GET(SSP_STATUS_TFL, val) ? : K1_SPI_FIFO_SIZE;
/*
* Limit how much we try to send at a time, to reduce the
* chance the other side can overrun our RX FIFO.
*/
/**/ resid_words = drv_data->tx_resid / drv_data->bytes;
/**/ count = min3(count, K1_SPI_THRESH, resid_words);
do
k1_spi_write_word(drv_data);
while (--count);
return !drv_data->tx_resid;
And we have the same problem in k1_spi_read(). There you can
probably change this:
count = min(count, drv_data->rx_resid);
to this
count = min(count, drv_data->rx_resid / drv_data->bytes);
You'll want to review and test yourself, but scanning through the
code this is what I see.
-Alex
next prev parent reply other threads:[~2026-04-29 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 2:01 [PATCH v9 0/3] spi: support the SpacemiT K1 SPI controller Guodong Xu
2026-04-28 2:01 ` [PATCH v9 1/3] spi: dt-bindings: add SpacemiT K1 SPI support Guodong Xu
2026-04-28 2:01 ` [PATCH v9 2/3] spi: spacemit: introduce SpacemiT K1 SPI controller driver Guodong Xu
2026-04-28 0:17 ` Mark Brown
2026-04-29 19:06 ` Alex Elder [this message]
2026-04-28 2:01 ` [PATCH v9 3/3] riscv: dts: spacemit: define a SPI controller node Guodong Xu
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=856f4e8d-ff7c-4744-9624-e838c758f009@ieee.org \
--to=elder@ieee.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=elder@kernel.org \
--cc=elder@riscstar.com \
--cc=guodong@riscstar.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@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