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: Re: FSL serial 166550 errata broken?
Date: Wed, 27 Sep 2017 11:03:06 +0000 [thread overview]
Message-ID: <1506510185.2325.4.camel@infinera.com> (raw)
In-Reply-To: <VI1PR04MB207821E9B5E0FE0BB629E1FA9A7A0@VI1PR04MB2078.eurprd04.prod.outlook.com>
On Mon, 2017-09-25 at 17:26 +0000, York Sun wrote:
> On 09/25/2017 09:55 AM, Joakim Tjernlund wrote:
> > 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.
> >=20
> > Looking inte to driver/CPU there is an errtum(A-004737) w.r.t BREAK han=
dling
> > and I can see we are hitting the irq function fsl8250_handle_irq() adde=
d
> > 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 wh=
y.
> > Any pointers?
> >=20
>=20
> Jocke,
>=20
> Did you mean MPC8321?
>=20
> I personally don't have experience debugging this erratum. Have you=20
> tried to contact the patch author Paul Gortmaker to see how he managed=20
> to get it work?
No, but I just found out it is u-boot related. If I use an very old u-boot =
it works.
Between then and now we did a massive upgrade of u-boot and now if breaks. =
And no,
bisect not possible due to local u-boot mods :)
Any idea what could be different? I cannot see and I have tested
what I could see/think of but now I am out of ideas.
Jocke
next prev parent reply other threads:[~2017-09-27 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 16:55 FSL serial 166550 errata broken? Joakim Tjernlund
2017-09-25 17:26 ` York Sun
2017-09-27 11:03 ` Joakim Tjernlund [this message]
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=1506510185.2325.4.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).