From: eric.nelson@boundarydevices.com (Eric Nelson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] serial: imx: Disable new features of autobaud detection
Date: Wed, 14 May 2014 12:38:11 -0700 [thread overview]
Message-ID: <5373C623.4030203@boundarydevices.com> (raw)
In-Reply-To: <1400093703-10128-1-git-send-email-festevam@gmail.com>
On 05/14/2014 11:55 AM, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Bit 7 of UCR3 is described in the i.MX reference manuals (with the exception
> of i.MX1) as follows:
>
> ADNIMP: Autobaud Detection Not Improved-. Disables new features of
> autobaud detection (See Baud Rate Automatic Detection
> Protocol, for more details).
>
> 0 Autobaud detection new features selected
> 1 Keep old autobaud detection mechanism
>
> The "new features" mechanism occasionally cause the receiver to get out of sync
> and continuously produce received characters of '\xff'.
>
> In order to reproduce the problem:
>
> $ stty -F /dev/ttymxc0 19200
>
> - Change the terminal baudrate to 19200
>
> - Type in the console and it should look good
>
> - Change the terminal baudrate back to 115200
>
> - Type 'b' in the console, then a stream of garbage characters is seen.
>
> Also rename the bit definition as per the reference manual.
>
> Tested on mx6q, mx6dl, mx6solo and mx53.
>
> Based on a patch from Eric Nelson for U-boot.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> drivers/tty/serial/imx.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Tested-by: Eric Nelson <eric.nelson@boundarydevices.com>
prev parent reply other threads:[~2014-05-14 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 18:55 [PATCH] serial: imx: Disable new features of autobaud detection Fabio Estevam
2014-05-14 19:38 ` Eric Nelson [this message]
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=5373C623.4030203@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).