linux-kernel - Re: [PATCH v4 2/6] spi: spi-fsl-dspi: Store status directly in cur

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <a1f01911-8cba-418a-8393-1d6ad3badb2f@sirena.org.uk>
Date: Mon, 21 Jul 2025 15:04:33 +0100
From: Mark Brown <broonie@...nel.org>
To: James Clark <james.clark@...aro.org>
Cc: Vladimir Oltean <olteanv@...il.com>,
	Vladimir Oltean <vladimir.oltean@....com>,
	Arnd Bergmann <arnd@...db.de>,
	Larisa Grigore <larisa.grigore@....com>,
	Frank Li <Frank.li@....com>, Christoph Hellwig <hch@....de>,
	linux-spi@...r.kernel.org, imx@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 2/6] spi: spi-fsl-dspi: Store status directly in
 cur_msg->status

On Mon, Jul 21, 2025 at 03:02:09PM +0100, James Clark wrote:

> I'm also not sure if it would fit with can_dma as that starts mapping stuff
> in the core layer. We want to avoid that because we need to write that
> control word for each SPI word. We could still change mode conditionally in
> the DSPI driver though, or make can_dma more flexible. But on top of this
> for sure.

Even if you need to open code the infrastructure the idea of a copybreak
should still be useful.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)