From: Fabio Estevam <festevam@gmail.com>
To: Clemens Gruber <clemens.gruber@pqgruber.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Fabio Estevam" <fabio.estevam@nxp.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Fugang Duan" <fugang.duan@nxp.com>
Subject: Re: [PATCH] serial: imx: disable DMA for RS-485 on i.MX6 SMP
Date: Wed, 21 Jun 2017 11:12:23 -0300 [thread overview]
Message-ID: <CAOMZO5DXxaJ6PveJb9912rog8xvfqgsg3O3u3a-ffWUj9ZnpCg@mail.gmail.com> (raw)
In-Reply-To: <20170621140556.GA766@archie.localdomain>
Hi Clemens,
On Wed, Jun 21, 2017 at 11:05 AM, Clemens Gruber
<clemens.gruber@pqgruber.com> wrote:
>
> I'd also prefer fixing the underlying problem.
Yes, that would be much better.
> If you take a look at the DMA parts in drivers/tty/serial/imx.c, can you
> spot anything SMP-unsafe?
Not really.
> By the way, can you get your hands on an i.MX6Q board with RS-485 to
> reproduce it?
Unfortunately I don't have such hardware. Even the mx6solo board that
I used to have access in the past I do not have it anymore.
> We could try for a few more weeks to find the bug and if we don't find
> it, adding this rs485-enabled-at-boot-time property sounds good!
Sounds like a good plan, thanks.
next prev parent reply other threads:[~2017-06-21 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 15:37 [PATCH] serial: imx: disable DMA for RS-485 on i.MX6 SMP Clemens Gruber
2017-06-20 16:13 ` Fabio Estevam
2017-06-20 23:49 ` Fabio Estevam
2017-07-02 20:47 ` Clemens Gruber
2017-07-02 23:09 ` Fabio Estevam
2017-06-21 14:05 ` [PATCH] " Clemens Gruber
2017-06-21 14:12 ` Fabio Estevam [this message]
2017-06-30 12:15 ` Fabio Estevam
2017-07-02 20:17 ` Clemens Gruber
2017-06-23 9:26 ` AW: [Customers.Eckelmann] " Schenk, Gavin
2017-07-17 11:34 ` 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=CAOMZO5DXxaJ6PveJb9912rog8xvfqgsg3O3u3a-ffWUj9ZnpCg@mail.gmail.com \
--to=festevam@gmail.com \
--cc=clemens.gruber@pqgruber.com \
--cc=fabio.estevam@nxp.com \
--cc=fugang.duan@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).