From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"leoyang.li@nxp.com" <leoyang.li@nxp.com>,
"york.sun@nxp.com" <york.sun@nxp.com>
Subject: FSL serial 166550 errata broken?
Date: Mon, 25 Sep 2017 16:55:26 +0000 [thread overview]
Message-ID: <1506358524.29657.31.camel@infinera.com> (raw)
We got some "broken" boards(mpx8321) where UART RX is held low(BREAK)
There we get a few:
serial8250: too much work for irq18
and the board freezes.
Looking inte to driver/CPU there is an errtum(A-004737) w.r.t BREAK handlin=
g
and I can see we are hitting the irq function fsl8250_handle_irq() added
in commit: 9deaa53ac7fa373623123aa4f18828dd62292b1a
"serial: add irq handler for Freescale 16550 errata."
For all I can tell this workaround is broken and I cannot figure out why.
Any pointers?
Jocke=
next reply other threads:[~2017-09-25 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 16:55 Joakim Tjernlund [this message]
2017-09-25 17:26 ` FSL serial 166550 errata broken? York Sun
2017-09-27 11:03 ` Joakim Tjernlund
2017-09-27 15:32 ` York Sun
2017-09-28 15:54 ` [EXTERNAL]Re: " Joakim Tjernlund
2017-09-28 18:10 ` Joakim Tjernlund
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=1506358524.29657.31.camel@infinera.com \
--to=joakim.tjernlund@infinera.com \
--cc=leoyang.li@nxp.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=york.sun@nxp.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).