From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Thangaraj Samynathan <thangaraj.s@microchip.com>
Cc: unglinuxdriver@microchip.com
Subject: Re: [PATCH v1 for-next] spi: spi-pci1xxxx: enable concurrent DMA read/write across SPI transfers
Date: Mon, 30 Jun 2025 15:59:43 +0100 [thread overview]
Message-ID: <175129558329.1416517.3510577981745100807.b4-ty@kernel.org> (raw)
In-Reply-To: <20250630073233.7356-1-thangaraj.s@microchip.com>
On Mon, 30 Jun 2025 13:02:33 +0530, Thangaraj Samynathan wrote:
> Refactor the pci1xxxx SPI driver to allow overlapping DMA read and
> write operations across SPI transfers. This improves throughput and
> reduces idle time between SPI transactions.
>
> Transfer sequence:
> - Start with a DMA read to load TX data from host to device buffer.
> - After DMA read completes, trigger the SPI transfer.
> - On SPI completion:
> - Start DMA write to copy received data from RX buffer to host.
> - Start the next DMA read to prepare TX data for the following transfer.
> - Begin the next SPI transfer after both DMA write and read complete.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: spi-pci1xxxx: enable concurrent DMA read/write across SPI transfers
commit: 7e1c28fbf235791cb5046fafdac5bc16fe8e788d
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-06-30 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 7:32 [PATCH v1 for-next] spi: spi-pci1xxxx: enable concurrent DMA read/write across SPI transfers Thangaraj Samynathan
2025-06-30 14: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=175129558329.1416517.3510577981745100807.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=thangaraj.s@microchip.com \
--cc=unglinuxdriver@microchip.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