Re: [PATCH] spi: spi-imx: spi_imx_transfer_one(): check for DMA transfer first

From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>
Cc: stable@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	David Jander <david@protonic.nl>,
	NXP Linux Team <linux-imx@nxp.com>,
	Frieder Schrempf <frieder.schrempf@kontron.de>,
	kernel@pengutronix.de
Subject: Re: [PATCH] spi: spi-imx: spi_imx_transfer_one(): check for DMA transfer first
Date: Fri, 18 Nov 2022 14:16:26 +0000	[thread overview]
Message-ID: <166878098696.885585.12678167389874876535.b4-ty@kernel.org> (raw)
In-Reply-To: <20221116164930.855362-1-mkl@pengutronix.de>

On Wed, 16 Nov 2022 17:49:30 +0100, Marc Kleine-Budde wrote:
> The SPI framework checks for each transfer (with the struct
> spi_controller::can_dma callback) whether the driver wants to use DMA
> for the transfer. If the driver returns true, the SPI framework will
> map the transfer's data to the device, start the actual transfer and
> map the data back.
> 
> In commit 07e759387788 ("spi: spi-imx: add PIO polling support") the
> spi-imx driver's spi_imx_transfer_one() function was extended. If the
> estimated duration of a transfer does not exceed a configurable
> duration, a polling transfer function is used. This check happens
> before checking if the driver decided earlier for a DMA transfer.
> 
> [...]

Applied to

   broonie/spi.git for-next

Thanks!

[1/1] spi: spi-imx: spi_imx_transfer_one(): check for DMA transfer first
      commit: e85e9e0d8cb759013d6474011c227f92e442d746

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