[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4498d3df-762b-4ecf-a196-605c096913e0@gmx.net>
Date: Thu, 1 Feb 2024 18:56:52 +0100
From: Stefan Wahren <wahrenst@....net>
To: Ralf Schlatterbeck <rsc@...tux.com>, Mark Brown <broonie@...nel.org>,
Shawn Guo <shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>, NXP Linux Team <linux-imx@....com>,
Vinod Koul <vkoul@...nel.org>, Miquel Raynal <miquel.raynal@...tlin.com>,
linux-spi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] spi-mxs: Fix chipselect glitch
Am 01.02.24 um 14:15 schrieb Ralf Schlatterbeck:
> There was a change in the mxs-dma engine that uses a new custom flag.
> The change was not applied to the mxs spi driver.
> This results in chipselect being deasserted too early.
> This fixes the chipselect problem by using the new flag in the mxs-spi
> driver.
>
> Fixes: ceeeb99cd821 ("dmaengine: mxs: rename custom flag")
> Signed-off-by: Ralf Schlatterbeck <rsc@...tux.com>
Tested-by: Stefan Wahren <wahrenst@....net>
Thanks
Powered by blists - more mailing lists