[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ec3fdef9-8f74-1a5a-e34a-d66b9e28dc5d@gmail.com>
Date: Thu, 28 Mar 2019 09:58:52 +0300
From: Igor Plyatov <plyatov@...il.com>
To: Aisheng Dong <aisheng.dong@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>,
Fabio Estevam <festevam@...il.com>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Sascha Hauer <s.hauer@...gutronix.de>,
Shawn Guo <shawnguo@...nel.org>,
Mark Brown <broonie@...nel.org>,
"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
Vinod Koul <vkoul@...nel.org>,
Dan Williams <dan.j.williams@...el.com>,
Andy Duan <fugang.duan@....com>, Han Xu <han.xu@....com>,
Robin Gong <yibin.gong@....com>,
Clark Wang <xiaoning.wang@....com>
Subject: Re: Issues with i.MX SPI DMA transfers
Dear developers,
I have update about these issues.
12 hours testing show very fast (some seconds) appearance of byte
duplication at interface spi4 (alias for ecspi5), while interfaces spi0
(alias for ecspi1) and spi1 (alias for ecspi2) work flawless (at least
without any other OS load).
Looks like, ecspi5 has some different configuration in SPI or SDMA
drivers or bug in SDMA script.
Any ideas?
Best wishes.
--
Igor Plyatov
Powered by blists - more mailing lists