From: Marek Vasut <marex@denx.de>
To: Huang Shijie <shijie8@gmail.com>
Cc: "Janusz Użycki" <j.uzycki@elproma.com.pl>,
"Richard Genoud" <richard.genoud@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
"Jiri Slaby" <jslaby@suse.cz>,
"Fabio Estevam" <festevam@gmail.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 2/4] serial: mxs-auart: use mctrl_gpio helpers for handling modem signals
Date: Fri, 7 Nov 2014 09:03:11 +0100 [thread overview]
Message-ID: <201411070903.11645.marex@denx.de> (raw)
In-Reply-To: <CAMiH66FKJm8hcgtR=-ZzzpCq+PQ8xkixbUnMzRPVd_cM_6VM1w@mail.gmail.com>
On Friday, November 07, 2014 at 02:34:31 AM, Huang Shijie wrote:
> why change them to gpio? If we change them to gpio. Could the DMA still
> works fine?
> did you test the DMA with this patch?
>
> Add Marek for this patch too.
I didn't look too deep into the patch, so here's just my experience:
1) The AUART block signals and GPIO block signals are not sychronised using the
same clock. Therefore, the latency between toggling of the AUART lines and
the GPIO-driven pins will not be deterministic and will vary. There might be
a way to approximate that, but that's definitelly not a reliable solution.
This is very bad for example if you drive RS485 DIR line with the RTS pin as
a GPIO ; the RTS pin will toggle at non-deterministic time compared to the
end of UART transmission. This will trigger bit-loss on the RS485 line and
you just don't want that.
2) Speaking of RS485, there's [1] and [2]. which I believe apply to any combo
of UART+GPIO toggling.
So I hate to bring the bad news , but UART+GPIO combo toggling is really a bad
bad idea.
HTH
[1] http://comments.gmane.org/gmane.linux.serial/6770
[2] http://article.gmane.org/gmane.linux.serial/3619/
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-11-07 8:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 16:53 [PATCH v4 0/4] serial: mxs-auart: gpios as modem signals Janusz Uzycki
2014-10-10 16:53 ` [PATCH v4 1/4] serial: mxs-auart: clean get_mctrl and set_mctrl Janusz Uzycki
2014-10-24 15:31 ` Richard Genoud
2014-10-10 16:53 ` [PATCH v4 2/4] serial: mxs-auart: use mctrl_gpio helpers for handling modem signals Janusz Uzycki
2014-10-24 15:32 ` Richard Genoud
2014-10-24 15:51 ` Janusz Użycki
2014-10-31 8:48 ` Richard Genoud
2014-11-06 11:13 ` Janusz Użycki
[not found] ` <CAMiH66FKJm8hcgtR=-ZzzpCq+PQ8xkixbUnMzRPVd_cM_6VM1w@mail.gmail.com>
2014-11-07 8:03 ` Marek Vasut [this message]
2014-11-07 10:04 ` Janusz Użycki
2014-11-07 11:02 ` Marek Vasut
2014-11-07 13:23 ` Janusz Użycki
2014-11-07 14:48 ` Marek Vasut
2014-11-07 16:29 ` Janusz Użycki
2014-11-08 11:22 ` Marek Vasut
2014-11-08 13:38 ` Janusz Użycki
2014-10-10 16:53 ` [PATCH v4 3/4] serial: mxs-auart: add interrupts for modem control lines Janusz Uzycki
2014-10-10 16:53 ` [PATCH v4 4/4] serial: mxs-auart: enable PPS support Janusz Uzycki
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=201411070903.11645.marex@denx.de \
--to=marex@denx.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=j.uzycki@elproma.com.pl \
--cc=jslaby@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=richard.genoud@gmail.com \
--cc=shijie8@gmail.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: 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).