[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<TYZPR06MB5203305392403192577AC26CB288A@TYZPR06MB5203.apcprd06.prod.outlook.com>
Date: Mon, 19 Jan 2026 14:25:23 +0000
From: Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>
To: Mark Brown <broonie@...nel.org>, Paul Menzel <pmenzel@...gen.mpg.de>
CC: "clg@...d.org" <clg@...d.org>, "boris.brezillon@...tlin.com"
<boris.brezillon@...tlin.com>, "joel@....id.au" <joel@....id.au>,
"andrew@...econstruct.com.au" <andrew@...econstruct.com.au>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
"openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, BMC-SW <BMC-SW@...eedtech.com>
Subject: RE: [PATCH v2 2/2] spi: aspeed: Add support for non-spi-mem devices
> -----Original Message-----
> From: Mark Brown <broonie@...nel.org>
> Sent: Monday, January 19, 2026 9:37 PM
> 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.
Okay, thanks for the reminder.
Powered by blists - more mailing lists