From: David Lechner <dlechner@baylibre.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] spi: Add spi_bpw_to_bytes() helper and use it
Date: Wed, 16 Apr 2025 09:56:12 -0500 [thread overview]
Message-ID: <bd28d718-ab7e-4470-a4de-22b995db8b94@baylibre.com> (raw)
In-Reply-To: <20250416062013.1826421-2-andriy.shevchenko@linux.intel.com>
On 4/16/25 1:16 AM, Andy Shevchenko wrote:
> This helper converts the given bits per word to bytes. The result
> will always be power-of-two (e.g. for 37 bits it returns 8 bytes)
> or 0 for 0 input.
>
> There are a couple of cases in SPI that are using the same approach
> and at least one more (in IIO) would benefit of it. Add a helper
> for everyone.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/spi/spi.c | 2 +-
> include/linux/spi/spi.h | 15 +++++++++++++++
> 2 files changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index b0e7702951fe..1bc0fdbb1bd7 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -3800,7 +3800,7 @@ int spi_split_transfers_maxwords(struct spi_controller *ctlr,
> size_t maxsize;
> int ret;
>
> - maxsize = maxwords * roundup_pow_of_two(BITS_TO_BYTES(xfer->bits_per_word));
> + maxsize = maxwords * spi_bpw_to_bytes(xfer->bits_per_word);
> if (xfer->len > maxsize) {
> ret = __spi_split_transfer_maxsize(ctlr, msg, &xfer,
> maxsize);
> diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
> index 834a09bd8ccc..abfc7f5e19e4 100644
> --- a/include/linux/spi/spi.h
> +++ b/include/linux/spi/spi.h
> @@ -1340,6 +1340,21 @@ static inline bool spi_is_bpw_supported(struct spi_device *spi, u32 bpw)
> return false;
> }
>
> +/**
> + * spi_bpw_to_bytes - Covert bits per word to bytes
> + * @bpw: Bits per word
> + *
> + * This function converts the given @bpw to bytes. The result is always
> + * power-of-two (e.g. for 37 bits it returns 8 bytes) or 0 for 0 input.
The SPI subsystem currently only supports bpw up to 32, so perhaps not
the best choice of value for the example. I would go with 20 bits getting
rounded up to 4 bytes to match the existing docs for @bits_per_word.
> + *
> + * Returns:
> + * Bytes for the given @bpw.
> + */
> +static inline u32 spi_bpw_to_bytes(u32 bpw)
> +{
> + return roundup_pow_of_two(BITS_TO_BYTES(bpw));
Do we need to #include <linux/log2.h> for roundup_pow_of_two()?
> +}
> +
> /**
> * spi_controller_xfer_timeout - Compute a suitable timeout value
> * @ctlr: SPI device
next prev parent reply other threads:[~2025-04-16 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 6:16 [PATCH v1 0/2] spi: Introduce and use spi_bpw_to_bytes() Andy Shevchenko
2025-04-16 6:16 ` [PATCH v1 1/2] spi: Add spi_bpw_to_bytes() helper and use it Andy Shevchenko
2025-04-16 7:03 ` Mukesh Kumar Savaliya
2025-04-16 7:09 ` Andy Shevchenko
2025-04-16 7:34 ` Mukesh Kumar Savaliya
2025-04-16 14:56 ` David Lechner [this message]
2025-04-16 15:14 ` Andy Shevchenko
2025-04-16 6:16 ` [PATCH v1 2/2] spi: dw: Use spi_bpw_to_bytes() helper Andy Shevchenko
2025-04-18 5:25 ` [PATCH v1 0/2] spi: Introduce and use spi_bpw_to_bytes() Mark Brown
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=bd28d718-ab7e-4470-a4de-22b995db8b94@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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