From: Andy Shevchenko <andy@kernel.org>
To: Da Xue <da@libre.computer>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>, "Mark Brown" <broonie@kernel.org>,
"Rui Miguel Silva" <rmfrfs@gmail.com>,
"Viresh Kumar" <vireshk@kernel.org>,
"Johan Hovold" <johan@kernel.org>,
"Alex Elder" <elder@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, greybus-dev@lists.linaro.org,
linux-staging@lists.linux.dev
Subject: Re: [RFC] spi: expand bits_per_word_mask to 64 bits
Date: Wed, 11 Jun 2025 11:30:56 +0300 [thread overview]
Message-ID: <aEk-wIJ8FY73NxQG@smile.fi.intel.com> (raw)
In-Reply-To: <20250611000516.1383268-1-da@libre.computer>
On Tue, Jun 10, 2025 at 08:05:15PM -0400, Da Xue wrote:
> Most current controller IP support 64-bit words.
"Most of the current controllers support..."
> Update the mask to u64 from u32.
> drivers/iio/adc/ad7949.c | 2 +-
> drivers/spi/spi-dln2.c | 2 +-
> drivers/spi/spi-ingenic.c | 2 +-
> drivers/spi/spi-sh-msiof.c | 2 +-
> drivers/spi/spi.c | 4 ++--
> drivers/staging/greybus/spilib.c | 2 +-
> include/linux/spi/altera.h | 2 +-
> include/linux/spi/spi.h | 6 +++---
I guess it would be nice to split on per-driver basis, starting from updating
the SPI core. I counted 6 patches in such a case.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-06-11 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 0:05 [RFC] spi: expand bits_per_word_mask to 64 bits Da Xue
2025-06-11 8:30 ` Andy Shevchenko [this message]
2025-06-11 11:12 ` Mark Brown
2025-06-11 14:16 ` David Lechner
2025-06-11 14:21 ` Mark Brown
2025-06-11 14:54 ` Andy Shevchenko
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=aEk-wIJ8FY73NxQG@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=broonie@kernel.org \
--cc=da@libre.computer \
--cc=dlechner@baylibre.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=jic23@kernel.org \
--cc=johan@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nuno.sa@analog.com \
--cc=rmfrfs@gmail.com \
--cc=vireshk@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