[<prev] [next>] [day] [month] [year] [list]
Message-ID: <VI1PR04MB45434A8AB7BC8B3DADBFCD5D89010@VI1PR04MB4543.eurprd04.prod.outlook.com>
Date: Thu, 23 May 2019 02:18:10 +0000
From: Robin Gong <yibin.gong@....com>
To: Lucas Stach <l.stach@...gutronix.de>,
"robh@...nel.org" <robh@...nel.org>,
"broonie@...nel.org" <broonie@...nel.org>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"festevam@...il.com" <festevam@...il.com>,
"mark.rutland@....com" <mark.rutland@....com>,
"vkoul@...nel.org" <vkoul@...nel.org>,
"dan.j.williams@...el.com" <dan.j.williams@...el.com>,
"u.kleine-koenig@...gutronix.de" <u.kleine-koenig@...gutronix.de>,
"plyatov@...il.com" <plyatov@...il.com>,
"catalin.marinas@....com" <catalin.marinas@....com>
CC: "linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"kernel@...gutronix.de" <kernel@...gutronix.de>
Subject: RE:Re: [PATCH v4 00/14] add ecspi ERR009165 for i.mx6/7 soc family
> -----Original Message-----
> From: Lucas Stach <l.stach@...gutronix.de>
> Sent: 2019年5月22日 18:10
> Hi Robin,
>
> Am Mittwoch, den 22.05.2019, 09:59 +0000 schrieb Robin Gong:
> > There is ecspi ERR009165 on i.mx6/7 soc family, which cause FIFO
> > transfer to be send twice in DMA mode. Please get more information from:
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>
> I haven't tested this so asking the obvious question: what happens when this
> series is applied without the RAM script being present on the system? Will it
> render SPI unusable? I guess so since it changes the flow between the SPI core
> and DMA controller. Can we somehow detect that SDMA isn't using the correct
> RAM script and fall back to PIO mode in the SPI driver in that case?
>
> Currently using the RAM script is not an option in a lot of use-cases, as it still
> breaks serial DMA support. The fix for the serial issue really needs to be
> remove the broken serial script from the RAM firmware, not change the serial
> driver to deal with the broken behavior introduced by the RAM script.
Okay, I'll try to merge another patch which fix UART driver function broken issue with ram script so that no any broken for this patch set.
>
> Regards,
> Lucas
Powered by blists - more mailing lists