From: Fabio Estevam <festevam@gmail.com>
To: Clemens Gruber <clemens.gruber@pqgruber.com>,
Tim Harvey <tharvey@gateworks.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Nandor Han" <nandor.han@ge.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: imx: RS-485 problems during TX, maybe DMA related
Date: Wed, 11 Jan 2017 09:51:29 -0200 [thread overview]
Message-ID: <CAOMZO5CGoq6FKSE6n9CyQycdtuJ6dAjSL7vJU4ZtXjAPWvdAug@mail.gmail.com> (raw)
In-Reply-To: <20170111003319.GA25265@archie.localdomain>
Hi Clemens,
On Tue, Jan 10, 2017 at 10:33 PM, Clemens Gruber
<clemens.gruber@pqgruber.com> wrote:
> Hi Fabio,
>
> On Sun, Jan 08, 2017 at 07:46:29PM -0200, Fabio Estevam wrote:
>> > What's the revision of the i.MX6Q on your board? Mine is 1.5 (TO 1.3)
>>
>> Mine is a mx6solo rev1.1.
>
> Could it be dependent upon SMP? Do you have an i.MX6Q board around to
> try?
Unfortunately the only hardware I can test RS485 is based on mx6solo.
Adding Tim Harvey, who could probably test RS485 on MX6Q.
Regards,
Fabio Estevam
next prev parent reply other threads:[~2017-01-11 11:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 16:00 imx: RS-485 problems during TX, maybe DMA related Clemens Gruber
2017-01-06 21:22 ` Fabio Estevam
2017-01-06 22:50 ` Clemens Gruber
2017-01-07 0:31 ` Fabio Estevam
2017-01-07 13:45 ` Clemens Gruber
2017-01-07 14:57 ` Fabio Estevam
2017-01-07 15:34 ` Clemens Gruber
2017-01-07 16:48 ` Fabio Estevam
2017-01-07 20:59 ` Clemens Gruber
2017-01-07 21:43 ` Fabio Estevam
2017-01-07 23:06 ` Clemens Gruber
2017-01-08 2:30 ` Fabio Estevam
2017-01-08 18:06 ` Clemens Gruber
2017-01-08 21:46 ` Fabio Estevam
2017-01-11 0:33 ` Clemens Gruber
2017-01-11 11:51 ` Fabio Estevam [this message]
2017-01-08 15:12 ` 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=CAOMZO5CGoq6FKSE6n9CyQycdtuJ6dAjSL7vJU4ZtXjAPWvdAug@mail.gmail.com \
--to=festevam@gmail.com \
--cc=clemens.gruber@pqgruber.com \
--cc=gregkh@linuxfoundation.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nandor.han@ge.com \
--cc=s.hauer@pengutronix.de \
--cc=tharvey@gateworks.com \
--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).