From: Scott Wood <scottwood@freescale.com>
To: Dongsheng Wang <dongsheng.wang@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org, Shaohui Xie <Shaohui.Xie@freescale.com>
Subject: Re: [PATCH 2/2] powerpc/85xx: handle the eLBC error interrupt if it exist in dts
Date: Tue, 7 Jan 2014 00:58:01 -0600 [thread overview]
Message-ID: <1389077881.11795.137.camel@snotra.buserror.net> (raw)
In-Reply-To: <1389076061-20159-1-git-send-email-dongsheng.wang@freescale.com>
On Tue, 2014-01-07 at 14:27 +0800, Dongsheng Wang wrote:
> From: Wang Dongsheng <dongsheng.wang@freescale.com>
AFAICT this patch was originally written by Shaohui Xie.
> On P3041, P1020, P1021, P1022, P1023 eLBC event interrupts are routed
> to Int9(P3041) & Int3(P102x) while ELBC error interrupts are routed to
> Int0, we need to call request_irq for each.
For p3041 I thought that was only on early silicon revs that we don't
support anymore.
As for p102x, have you tested that this is actually what happens? How
would we distinguish eLBC errors from other error sources, given that
there's no EISR0? Do we just hope that no other error interrupts
happen?
-Scott
next prev parent reply other threads:[~2014-01-07 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 6:27 [PATCH 2/2] powerpc/85xx: handle the eLBC error interrupt if it exist in dts Dongsheng Wang
2014-01-07 6:58 ` Scott Wood [this message]
2014-01-07 10:01 ` Dongsheng.Wang
2014-01-07 20:45 ` Scott Wood
2014-01-08 7:12 ` Dongsheng.Wang
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=1389077881.11795.137.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=Shaohui.Xie@freescale.com \
--cc=dongsheng.wang@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.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).