From: Mark Brown <broonie@kernel.org>
To: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Patrice Chotard <patrice.chotard@foss.st.com>
Cc: linux-spi@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] spi: stm32: Update for OSPI and QSPI drivers
Date: Mon, 15 Dec 2025 22:59:30 +0900 [thread overview]
Message-ID: <176580717045.161463.13864912582865667097.b4-ty@kernel.org> (raw)
In-Reply-To: <20251205-upstream_qspi_ospi_updates-v1-0-7e6c8b9f5141@foss.st.com>
On Fri, 05 Dec 2025 10:04:50 +0100, Patrice Chotard wrote:
> This serie applies the following updates on the spi-stm32-ospi and
> spi-stm32-qspi dirvers :
>
> _ Update FIFO accesses using u16 and u32 when possible instead of u8
> only to optimize throughput.
> _ Replace Transmit Complete and Transmit Error interrupt management by
> usage of read_poll_timeout_atomic() to optimize throughtput.
> _ Simplify Status Match interrupt check.
> _ Set DMA burst configuration dynamically.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/8] spi: stm32-ospi: Set DMA maxburst dynamically
commit: e35a7607e05d59d35e937b80532ae93d1dd2493f
[2/8] spi: stm32-ospi: Optimize FIFO accesses using u16 or u32
commit: cfe58ffc95a601988702df6f3462cb54dde467e9
[3/8] spi: stm32-ospi: Remove CR_TCIE and CR_TEIE irq usage
commit: f6ed06926b510f54a0817567ffd458194ed90bd6
[4/8] spi: stm32-ospi: Simplify SMIE interrupt test
commit: e2f0ea18e560e5fa6180f52dffe434525a0cf86b
[5/8] spi: stm32-qspi: Set DMA maxburst dynamically
commit: 4ef80c71c62ab841db9b1a9d74ffe043c60f6222
[6/8] spi: stm32-qspi: Optimize FIFO accesses using u16 or u32
commit: 1ca91281649547efa4be34584a304974c9601df1
[7/8] spi: stm32-qspi: Remove CR_TCIE and CR_TEIE irq usage
commit: c5f76d888810bca2d46297a7b942e10bc8cc69dd
[8/8] spi: stm32-qspi: Simplify SMIE interrupt test
commit: fee876b2ec75dcc18fdea154eae1f5bf14d82659
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2025-12-15 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 9:04 Patrice Chotard
2025-12-05 9:04 ` [PATCH 1/8] spi: stm32-ospi: Set DMA maxburst dynamically Patrice Chotard
2025-12-05 9:04 ` [PATCH 2/8] spi: stm32-ospi: Optimize FIFO accesses using u16 or u32 Patrice Chotard
2025-12-05 15:04 ` Mark Brown
2025-12-05 9:04 ` [PATCH 3/8] spi: stm32-ospi: Remove CR_TCIE and CR_TEIE irq usage Patrice Chotard
2025-12-06 5:19 ` kernel test robot
2025-12-06 7:18 ` kernel test robot
2025-12-05 9:04 ` [PATCH 4/8] spi: stm32-ospi: Simplify SMIE interrupt test Patrice Chotard
2025-12-05 9:04 ` [PATCH 5/8] spi: stm32-qspi: Set DMA maxburst dynamically Patrice Chotard
2025-12-05 9:04 ` [PATCH 6/8] spi: stm32-qspi: Optimize FIFO accesses using u16 or u32 Patrice Chotard
2025-12-05 9:04 ` [PATCH 7/8] spi: stm32-qspi: Remove CR_TCIE and CR_TEIE irq usage Patrice Chotard
2025-12-05 9:04 ` [PATCH 8/8] spi: stm32-qspi: Simplify SMIE interrupt test Patrice Chotard
2025-12-15 13:59 ` Mark Brown [this message]
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=176580717045.161463.13864912582865667097.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrice.chotard@foss.st.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®