From: Robin Gong <yibin.gong@nxp.com> To: "Igor Plyatov" <plyatov@gmail.com>, "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de> Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>, dl-linux-imx <linux-imx@nxp.com>, Fabio Estevam <festevam@gmail.com>, Pengutronix Kernel Team <kernel@pengutronix.de>, Sascha Hauer <s.hauer@pengutronix.de>, Shawn Guo <shawnguo@kernel.org>, Mark Brown <broonie@kernel.org>, "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>, Vinod Koul <vkoul@kernel.org>, Dan Williams <dan.j.williams@intel.com>, Andy Duan <fugang.duan@nxp.com>, Han Xu <han.xu@nxp.com>, Clark Wang <xiaoning.wang@nxp.com> Subject: RE: Issues with i.MX SPI DMA transfers Date: Thu, 28 Mar 2019 07:21:27 +0000 [thread overview] Message-ID: <VI1PR04MB45433F57929ABE7B5F8803B989590@VI1PR04MB4543.eurprd04.prod.outlook.com> (raw) In-Reply-To: <b8e80127-e377-9ef9-2447-b0126fdad7dc@gmail.com> > -----Original Message----- > From: Igor Plyatov <plyatov@gmail.com> > Sent: 2019年3月28日 15:04 > To: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> > Cc: linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; > linux-spi@vger.kernel.org; dl-linux-imx <linux-imx@nxp.com>; Fabio Estevam > <festevam@gmail.com>; Pengutronix Kernel Team <kernel@pengutronix.de>; > Sascha Hauer <s.hauer@pengutronix.de>; Shawn Guo > <shawnguo@kernel.org>; Mark Brown <broonie@kernel.org>; > dmaengine@vger.kernel.org; Vinod Koul <vkoul@kernel.org>; Dan Williams > <dan.j.williams@intel.com>; Andy Duan <fugang.duan@nxp.com>; Han Xu > <han.xu@nxp.com>; Robin Gong <yibin.gong@nxp.com>; Clark Wang > <xiaoning.wang@nxp.com> > Subject: Re: Issues with i.MX SPI DMA transfers > > Dear Uwe, > > > > Hello Igor, > > > > On Wed, Mar 27, 2019 at 08:40:00PM +0300, Igor Plyatov wrote: > >> please, help to resolve two issues with SPI DMA transfers at i.MX6Q > >> platform. > >> > >> First issue is > >> [ 4465.008003] spi_master spi0: I/O Error in DMA RX > >> > >> Second issue is duplication for one of received bytes. > >> > >> Probably, these issues related to each one. > > This is probably the same problem I hit some time ago. Check ERR009165 > > in the errata. You either need to disable DMA or need a fixed > > sdma-Script. > > disabling of DMA is not an option, because high throughput required for SPI bus > to communicate with DSPs. > > I'm aware of ERR009165, but as I write some minutes earlier to list, > spi0 (alias for ecspi1) and spi1 (alias for ecspi2) work flawless, while > spi4 (alias for ecspi5) fails very fast. > > Does same SDMA script used for all SPI interfaces or scripts are different? No different handle inside sdma script for different ecspi port. Agree Uwe, your duplicate data caught seems like ERR009165. Anyway I'll create ecspi patch for you to try in these days. > > Best wishes. > > -- > > Igor Plyatov
WARNING: multiple messages have this Message-ID (diff)
From: Robin Gong <yibin.gong@nxp.com> To: "Igor Plyatov" <plyatov@gmail.com>, "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de> Cc: Andy Duan <fugang.duan@nxp.com>, Shawn Guo <shawnguo@kernel.org>, Sascha Hauer <s.hauer@pengutronix.de>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>, Vinod Koul <vkoul@kernel.org>, Mark Brown <broonie@kernel.org>, Clark Wang <xiaoning.wang@nxp.com>, dl-linux-imx <linux-imx@nxp.com>, Pengutronix Kernel Team <kernel@pengutronix.de>, "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>, Han Xu <han.xu@nxp.com>, Dan Williams <dan.j.williams@intel.com>, Fabio Estevam <festevam@gmail.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: RE: Issues with i.MX SPI DMA transfers Date: Thu, 28 Mar 2019 07:21:27 +0000 [thread overview] Message-ID: <VI1PR04MB45433F57929ABE7B5F8803B989590@VI1PR04MB4543.eurprd04.prod.outlook.com> (raw) In-Reply-To: <b8e80127-e377-9ef9-2447-b0126fdad7dc@gmail.com> > -----Original Message----- > From: Igor Plyatov <plyatov@gmail.com> > Sent: 2019年3月28日 15:04 > To: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> > Cc: linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; > linux-spi@vger.kernel.org; dl-linux-imx <linux-imx@nxp.com>; Fabio Estevam > <festevam@gmail.com>; Pengutronix Kernel Team <kernel@pengutronix.de>; > Sascha Hauer <s.hauer@pengutronix.de>; Shawn Guo > <shawnguo@kernel.org>; Mark Brown <broonie@kernel.org>; > dmaengine@vger.kernel.org; Vinod Koul <vkoul@kernel.org>; Dan Williams > <dan.j.williams@intel.com>; Andy Duan <fugang.duan@nxp.com>; Han Xu > <han.xu@nxp.com>; Robin Gong <yibin.gong@nxp.com>; Clark Wang > <xiaoning.wang@nxp.com> > Subject: Re: Issues with i.MX SPI DMA transfers > > Dear Uwe, > > > > Hello Igor, > > > > On Wed, Mar 27, 2019 at 08:40:00PM +0300, Igor Plyatov wrote: > >> please, help to resolve two issues with SPI DMA transfers at i.MX6Q > >> platform. > >> > >> First issue is > >> [ 4465.008003] spi_master spi0: I/O Error in DMA RX > >> > >> Second issue is duplication for one of received bytes. > >> > >> Probably, these issues related to each one. > > This is probably the same problem I hit some time ago. Check ERR009165 > > in the errata. You either need to disable DMA or need a fixed > > sdma-Script. > > disabling of DMA is not an option, because high throughput required for SPI bus > to communicate with DSPs. > > I'm aware of ERR009165, but as I write some minutes earlier to list, > spi0 (alias for ecspi1) and spi1 (alias for ecspi2) work flawless, while > spi4 (alias for ecspi5) fails very fast. > > Does same SDMA script used for all SPI interfaces or scripts are different? No different handle inside sdma script for different ecspi port. Agree Uwe, your duplicate data caught seems like ERR009165. Anyway I'll create ecspi patch for you to try in these days. > > Best wishes. > > -- > > Igor Plyatov _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-28 7:21 UTC|newest] Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-27 17:40 Issues with i.MX SPI DMA transfers Igor Plyatov 2019-03-27 17:40 ` Igor Plyatov 2019-03-28 2:37 ` Aisheng Dong 2019-03-28 2:37 ` Aisheng Dong 2019-03-28 2:37 ` Aisheng Dong 2019-03-28 6:58 ` Igor Plyatov 2019-03-28 6:58 ` Igor Plyatov 2019-03-28 6:58 ` Igor Plyatov 2019-03-28 6:52 ` Uwe Kleine-König 2019-03-28 6:52 ` Uwe Kleine-König 2019-03-28 7:04 ` Igor Plyatov 2019-03-28 7:04 ` Igor Plyatov 2019-03-28 7:21 ` Robin Gong [this message] 2019-03-28 7:21 ` Robin Gong 2019-03-28 7:21 ` Robin Gong 2019-03-28 8:22 ` Uwe Kleine-König 2019-03-28 8:22 ` Uwe Kleine-König 2019-03-29 11:57 ` Igor Plyatov 2019-03-29 11:57 ` Igor Plyatov 2019-03-28 9:23 ` Robin Gong 2019-03-28 9:23 ` Robin Gong 2019-03-28 9:23 ` Robin Gong 2019-03-28 11:05 ` Igor Plyatov 2019-03-28 11:05 ` Igor Plyatov 2019-03-28 11:05 ` Igor Plyatov 2019-04-01 7:35 ` Robin Gong 2019-04-01 7:35 ` Robin Gong 2019-04-01 7:35 ` Robin Gong 2019-04-02 7:20 ` Igor Plyatov 2019-04-02 7:20 ` Igor Plyatov 2019-04-02 7:20 ` Igor Plyatov 2019-04-02 8:32 ` Robin Gong 2019-04-02 8:32 ` Robin Gong 2019-04-02 12:15 ` Igor Plyatov 2019-04-02 12:15 ` Igor Plyatov 2019-04-02 12:15 ` Igor Plyatov 2019-04-03 7:38 ` Robin Gong 2019-04-03 7:38 ` Robin Gong 2019-04-03 7:38 ` Robin Gong 2019-04-03 15:51 ` Igor Plyatov 2019-04-03 15:51 ` Igor Plyatov 2019-04-03 15:51 ` Igor Plyatov 2019-04-03 15:51 ` Igor Plyatov 2019-04-18 10:35 ` Marc Gonzalez 2019-04-09 3:26 ` Robin Gong 2019-04-09 3:26 ` Robin Gong 2019-04-09 3:26 ` Robin Gong 2019-04-18 1:19 ` Robin Gong 2019-04-18 1:19 ` Robin Gong 2019-04-18 1:19 ` Robin Gong 2019-04-18 6:30 ` Igor Plyatov 2019-04-18 6:30 ` Igor Plyatov 2019-04-18 8:05 ` Robin Gong 2019-04-18 8:05 ` Robin Gong 2019-04-18 8:05 ` Robin Gong 2019-04-03 17:13 Igor Plyatov 2019-04-03 17:13 ` Igor Plyatov 2019-04-03 17:13 ` Igor Plyatov 2019-04-08 10:18 Robin Gong 2019-04-08 10:18 ` Robin Gong 2019-04-08 10:18 ` Robin Gong
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=VI1PR04MB45433F57929ABE7B5F8803B989590@VI1PR04MB4543.eurprd04.prod.outlook.com \ --to=yibin.gong@nxp.com \ --cc=broonie@kernel.org \ --cc=dan.j.williams@intel.com \ --cc=dmaengine@vger.kernel.org \ --cc=festevam@gmail.com \ --cc=fugang.duan@nxp.com \ --cc=han.xu@nxp.com \ --cc=kernel@pengutronix.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-imx@nxp.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-spi@vger.kernel.org \ --cc=plyatov@gmail.com \ --cc=s.hauer@pengutronix.de \ --cc=shawnguo@kernel.org \ --cc=u.kleine-koenig@pengutronix.de \ --cc=vkoul@kernel.org \ --cc=xiaoning.wang@nxp.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.