From: Kevin Mehall <km@kevinmehall.net>
To: Mark Brown <broonie@kernel.org>, Chen-Yu Tsai <wens@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Mirko Vogt <mirko-dev|linux@nanl.de>,
Ralf Schlatterbeck <rsc@runtux.com>,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] spi: sun6i: Fix chip select handling around autosuspend
Date: Thu, 23 Apr 2026 11:39:59 -0600 [thread overview]
Message-ID: <20260423174001.2797797-1-km@kevinmehall.net> (raw)
Move the initialization of the SUN6I_TFR_CTL_REG bits out of
sun6i_spi_transfer_one() into earlier callbacks to fix two bugs:
- With a native chip select, the setup_delay is not correctly applied to
the first transfer after autosuspend.
- With a GPIO chip select, the CS is asserted before SCK is driven to the
correct initial level per the SPI mode. When the mode is set, it can
cause an extra SCK transition with CS low and corrupt the transfer.
Changes since the previous single patch:
- Move the line that sets `SUN6I_TFR_CTL_CS_MANUAL` into
`sun6i_spi_set_cs()` rather than into `sun6i_spi_prepare_message()`.
This change is now a separate commit.
Kevin Mehall (2):
spi: sun6i: Honor CS setup delay on the first transfer with native CS
spi: sun6i: Set SPI mode in prepare_message
drivers/spi/spi-sun6i.c | 74 +++++++++++++++++++++++++----------------
1 file changed, 45 insertions(+), 29 deletions(-)
base-commit: 028ef9c96e96197026887c0f092424679298aae8
--
2.53.0
next reply other threads:[~2026-04-23 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 17:39 Kevin Mehall [this message]
2026-04-23 17:40 ` [PATCH v2 1/2] spi: sun6i: Honor CS setup delay on the first transfer with native CS Kevin Mehall
2026-04-23 18:40 ` Kevin Mehall
2026-04-23 18:50 ` Mark Brown
2026-04-23 17:40 ` [PATCH v2 2/2] spi: sun6i: Set SPI mode in prepare_message Kevin Mehall
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=20260423174001.2797797-1-km@kevinmehall.net \
--to=km@kevinmehall.net \
--cc=broonie@kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mirko-dev|linux@nanl.de \
--cc=rsc@runtux.com \
--cc=samuel@sholland.org \
--cc=wens@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