From: Paul Cercueil <paul.cercueil@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Bharat Bhushan <bbhushan2@marvell.com>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>,
Tanmay Jagdale <tanmay@marvell.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/5] spi: cadence-xspi: Reconfigure to STIG mode before SPI message
Date: Mon, 09 Nov 2026 16:08:54 +0100 [thread overview]
Message-ID: <8fd61964a9a8193e4b4ec386b3f9aee69ff6b75e.camel@bootlin.com> (raw)
In-Reply-To: <179405331442.3424803.15701905615212408804.b4-review@b4>
Hi Mark,
Le samedi 07 novembre 2026 à 12:08 +0000, Mark Brown a écrit :
> > The .transfer_one_message() function uses the STIG mode, therefore the
> > xSPI needs to be configured to STIG mode before starting any transfer.
> >
> > Without this, .transfer_one_message() simply won't work, at least on the
> > CN10K SoC.
>
> > @@ -1112,6 +1123,11 @@ static int cdns_xspi_transfer_one_message_b0(struct
> > spi_controller *controller,
> > int current_transfer_len;
> > int cs = spi_get_chipselect(spi, 0);
> > int cs_change = 0;
> > + int ret;
> > +
> > + ret = cdns_xspi_set_stig_mode(cdns_xspi);
> > + if (ret)
> > + return ret;
>
> If we return an error we need to also set m->status otherwise it'll be
> stuck at -EINPROGESS and we will get confused. This is a preexisting
> bug in other bits of the function :/
ACK.
So I'll fix that first, in the v2.
Cheers,
-Paul
next prev parent reply other threads:[~2026-11-09 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 10:06 [PATCH 0/5] spi: cadence-xspi: Fixes and misc. changes Paul Cercueil
2026-11-04 10:06 ` [PATCH 1/5] spi: cadence-xspi: Reconfigure to STIG mode before SPI message Paul Cercueil
2026-11-07 12:08 ` Mark Brown
2026-11-09 15:08 ` Paul Cercueil [this message]
2026-11-04 10:06 ` [PATCH 2/5] spi: cadence-xspi: Inform SPI core about size transferred Paul Cercueil
2026-11-04 10:06 ` [PATCH 3/5] spi: cadence-xspi: Drop useless cdns_xspi->cur_cs Paul Cercueil
2026-11-04 10:06 ` [PATCH 4/5] spi: cadence-xspi: Rework resource discovery Paul Cercueil
2026-11-07 12:08 ` Mark Brown
2026-11-04 10:06 ` [PATCH 5/5] spi: cadence-xspi: Add workaround for old Marvell firmwares Paul Cercueil
2026-11-07 12:08 ` Mark Brown
2026-11-07 13:21 ` Jisheng Zhang
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=8fd61964a9a8193e4b4ec386b3f9aee69ff6b75e.camel@bootlin.com \
--to=paul.cercueil@bootlin.com \
--cc=bbhushan2@marvell.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=sgoutham@marvell.com \
--cc=stable@vger.kernel.org \
--cc=tanmay@marvell.com \
--cc=thomas.petazzoni@bootlin.com \
/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®