Received-SPF: pass (google.com: domain of linux-kernel+bounces-22827-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Date: Wed, 10 Jan 2024 21:39:23 +0000
From: Mark Brown <broonie@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Jonathan Cameron <jic23@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Michael Hennerich <michael.hennerich@analog.com>,
	Nuno =?iso-8859-1?Q?S=E1?= <nuno.sa@analog.com>,
	Frank Rowand <frowand.list@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= <u.kleine-koenig@pengutronix.de>,
	Jonathan Corbet <corbet@lwn.net>, linux-spi@vger.kernel.org,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-pwm@vger.kernel.org,
	linux-kernel@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 05/13] spi: axi-spi-engine: add SPI offload support
Message-ID: <a94d7aae-3d5c-4204-83f6-5374c3166f58@sirena.org.uk>
References: <20240109-axi-spi-engine-series-3-v1-0-e42c6a986580@baylibre.com>
 <20240109-axi-spi-engine-series-3-v1-5-e42c6a986580@baylibre.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="vA0E8xm0iXmuRqc+"
Content-Disposition: inline
In-Reply-To: <20240109-axi-spi-engine-series-3-v1-5-e42c6a986580@baylibre.com>


--vA0E8xm0iXmuRqc+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 10, 2024 at 01:49:46PM -0600, David Lechner wrote:
> This adds an implementation of the SPI offload_ops to the AXI SPI Engine
> driver to provide offload support.
>=20
> Offload lookup is done by device property lookup. SPI Engine commands
> and tx data  are recorded by writing to offload-specific FIFOs in the
> SPI Engine hardware.

Glancing through here I'm not seeing anything here that handles DMA
mapping, given that the controller will clearly be doing DMA here that
seems surprising.

--vA0E8xm0iXmuRqc+
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmWfDooACgkQJNaLcl1U
h9CJ8wf+IdN87MPrgtB1OLZ7i6VO0ejFYyduotqQrFiECH4HDV73++1TiR9FGcG/
hqgtxpVCkSyWFqpqDhkdBaOFRZp4YNbTlaOkjkFGXmNQSnBqJwQHbQW0Ipi57mB+
jm+GbuJTZODou/WIWxWBiYF0C4nVQz9XtwU5aOJVuo+2kNTZjcCK+SN8uZIZEw3j
SbyxkVUA/6thCgvZK38hpPPuP8P12Hkdpb1lrA3AdyP3TYQXYOpxmzFciCGk5OM3
DS0wx7m1Cgvq+Dj8XfdxBgpTaBAw9IGfDdEU5ArSKBv9Wrg0tqXkxEsZ4oPD47dQ
uvru/KvjQwUFC4S6UVreNedMuupfKw==
=Wfhe
-----END PGP SIGNATURE-----

--vA0E8xm0iXmuRqc+--