linux-kernel - Re: [PATCH v2 2/2] spi: aspeed: Add support for non-spi-mem devices

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <e4f133db-928e-49ae-9ee8-99e119d14708@sirena.org.uk>
Date: Mon, 19 Jan 2026 13:37:08 +0000
From: Mark Brown <broonie@...nel.org>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>, clg@...d.org,
	boris.brezillon@...tlin.com, joel@....id.au,
	andrew@...econstruct.com.au, linux-aspeed@...ts.ozlabs.org,
	openbmc@...ts.ozlabs.org, linux-spi@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	BMC-SW@...eedtech.com
Subject: Re: [PATCH v2 2/2] spi: aspeed: Add support for non-spi-mem devices

On Sun, Jan 18, 2026 at 12:48:37AM +0100, Paul Menzel wrote:
> Am 17.01.26 um 14:42 schrieb Chin-Ting Kuo:
> > The ASPEED FMC/SPI controller may be shared by spi-mem devices and
> > other SPI peripherals that do not use the spi-mem framework.
> > 
> > The driver currently assumes spi-mem semantics for all devices,
> > while the controller also supports direct user mode access commonly
> > used by non-spi-mem devices. This mismatch can result in incorrect
> > behavior when different types of devices share the same controller.

Please delete unneeded context from mails when replying.  Doing this
makes it much easier to find your reply in the message, helping ensure
it won't be missed by people scrolling through the irrelevant quoted
material.

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