[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7739e283-799c-7dac-2bcd-fbf17fd4fb93@gmail.com>
Date: Wed, 3 Apr 2019 20:13:49 +0300
From: Igor Plyatov <plyatov@...il.com>
To: Robin Gong <yibin.gong@....com>
Cc: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
"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>,
Clark Wang <xiaoning.wang@....com>
Subject: Re: Issues with i.MX SPI DMA transfers
Dear Robin,
I have made additional tests on another exemplar of board with
absolutely same hardware.
The spidev_test failed on eCSPI2 and eCSPI5 interfaces, but works
successfully on eCSPI1 interface.
So, it looks, issue does not correspond to fixed interface number.
This is generic issue of i.MX6 SOC and hardly broken eCSPI interface
number can change from SOC chip to chip.
Do you have any idea how to improve situation with eCSPI in DMA mode?
Best wishes.
--
Igor Plyatov
Powered by blists - more mailing lists