From: Marek Vasut <marex@denx.de> To: Fabio Estevam <festevam@gmail.com> Cc: Fabio Estevam <fabio.estevam@nxp.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, Kai Ruhnau <kai.ruhnau@target-sg.com>, "# 4 . 9+" <stable@vger.kernel.org>, Martyn Welch <martyn.welch@collabora.co.uk>, Shawn Guo <shawnguo@kernel.org>, Clemens Gruber <clemens.gruber@pqgruber.com>, Tim Harvey <tharvey@gateworks.com> Subject: Re: [PATCH] serial: imx: Only enable UART DMA on i.MX6Q and i.MX53 Date: Mon, 6 Feb 2017 20:43:22 +0100 [thread overview] Message-ID: <81fbfca6-78d5-73f1-b216-25990d666d77@denx.de> (raw) In-Reply-To: <CAOMZO5AkbtWn65p6mj=7AxCh3-v18XPuRqR07NHCSiQY82QG=g@mail.gmail.com> On 02/06/2017 08:38 PM, Fabio Estevam wrote: > Hi Marek, Hi, > On Mon, Feb 6, 2017 at 5:05 PM, Marek Vasut <marex@denx.de> wrote: > >> Well yes, DMA is broken in 4.9 , that's why it's CC stable 4.9+ :) > > This patch is based on the fact that the UART on the imx6sx is not of > a imx6q UART type, which is not correct. > > Current imx6sx.dtsi misses to add a "fsl,imx6q-uart" compatible > string, just like all other imx6 SoC dtsi. Well given that the DMA does not work on 6SX, I guess it's not really compatible with 6Q. > When we fix the compatible uart problem on imx6sx.dtsi, then DMA will > be enabled and things will break again. > > That's why we need a better fix for this issue: > > 1) Let's see if Clemens' suggestion of using the latest SDMA firmware > can make DMA robust on your usecase. a) This will break if you don't use the latest SDMA firmware. This can be repaired by checking the SDMA firmware version and selectively disabling the DMA for broken versions. b) The DMA should not have been enabled on 4.9 , but it incorrectly is. Enabling it on 4.9 is a feature addition, which shouldn't go into stable kernel. > 2) If the system fails even with the latest SDMA, then the board dts > can disable dma by passing empty dma nodes. This might actually be the thing to do for 4.9 if you want to add the mx6q compatible to mx6sx uart . > Not all mx6 system seem to suffer from such SDMA problem. On a > imx6sx-udoo-neo we could use UART with DMA to connect to the Bluetooth > chip. Clearly some do, so it's probably also a matter of the link partner behavior. -- Best regards, Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] serial: imx: Only enable UART DMA on i.MX6Q and i.MX53 Date: Mon, 6 Feb 2017 20:43:22 +0100 [thread overview] Message-ID: <81fbfca6-78d5-73f1-b216-25990d666d77@denx.de> (raw) In-Reply-To: <CAOMZO5AkbtWn65p6mj=7AxCh3-v18XPuRqR07NHCSiQY82QG=g@mail.gmail.com> On 02/06/2017 08:38 PM, Fabio Estevam wrote: > Hi Marek, Hi, > On Mon, Feb 6, 2017 at 5:05 PM, Marek Vasut <marex@denx.de> wrote: > >> Well yes, DMA is broken in 4.9 , that's why it's CC stable 4.9+ :) > > This patch is based on the fact that the UART on the imx6sx is not of > a imx6q UART type, which is not correct. > > Current imx6sx.dtsi misses to add a "fsl,imx6q-uart" compatible > string, just like all other imx6 SoC dtsi. Well given that the DMA does not work on 6SX, I guess it's not really compatible with 6Q. > When we fix the compatible uart problem on imx6sx.dtsi, then DMA will > be enabled and things will break again. > > That's why we need a better fix for this issue: > > 1) Let's see if Clemens' suggestion of using the latest SDMA firmware > can make DMA robust on your usecase. a) This will break if you don't use the latest SDMA firmware. This can be repaired by checking the SDMA firmware version and selectively disabling the DMA for broken versions. b) The DMA should not have been enabled on 4.9 , but it incorrectly is. Enabling it on 4.9 is a feature addition, which shouldn't go into stable kernel. > 2) If the system fails even with the latest SDMA, then the board dts > can disable dma by passing empty dma nodes. This might actually be the thing to do for 4.9 if you want to add the mx6q compatible to mx6sx uart . > Not all mx6 system seem to suffer from such SDMA problem. On a > imx6sx-udoo-neo we could use UART with DMA to connect to the Bluetooth > chip. Clearly some do, so it's probably also a matter of the link partner behavior. -- Best regards, Marek Vasut
next prev parent reply other threads:[~2017-02-06 19:43 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-02-04 21:39 [PATCH] serial: imx: Only enable UART DMA on i.MX6Q and i.MX53 Marek Vasut 2017-02-04 21:39 ` Marek Vasut [not found] ` <DB6PR0402MB2743C709F162BDE52429DF49E3410@DB6PR0402MB2743.eurprd04.prod.outlook.com> 2017-02-05 16:36 ` Fabio Estevam 2017-02-05 16:36 ` Fabio Estevam 2017-02-05 17:51 ` Clemens Gruber 2017-02-06 19:24 ` Marek Vasut 2017-02-06 19:05 ` Marek Vasut 2017-02-06 19:05 ` Marek Vasut 2017-02-06 19:38 ` Fabio Estevam 2017-02-06 19:38 ` Fabio Estevam 2017-02-06 19:43 ` Marek Vasut [this message] 2017-02-06 19:43 ` Marek Vasut 2017-02-06 23:39 ` Fabio Estevam 2017-02-06 23:39 ` Fabio Estevam
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=81fbfca6-78d5-73f1-b216-25990d666d77@denx.de \ --to=marex@denx.de \ --cc=clemens.gruber@pqgruber.com \ --cc=fabio.estevam@nxp.com \ --cc=festevam@gmail.com \ --cc=kai.ruhnau@target-sg.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=martyn.welch@collabora.co.uk \ --cc=shawnguo@kernel.org \ --cc=stable@vger.kernel.org \ --cc=tharvey@gateworks.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.