From: Mark Rutland <mark.rutland@arm.com>
To: Dongsheng Wang <dongsheng.wang@freescale.com>
Cc: "scottwood@freescale.com" <scottwood@freescale.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"galak@codeaurora.org" <galak@codeaurora.org>
Subject: Re: [PATCH 1/2] powerpc/dts: fix lbc lack of error interrupt
Date: Tue, 7 Jan 2014 10:34:47 +0000 [thread overview]
Message-ID: <20140107103447.GC2930@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1389076002-18674-1-git-send-email-dongsheng.wang@freescale.com>
On Tue, Jan 07, 2014 at 06:26:42AM +0000, Dongsheng Wang wrote:
> From: Wang Dongsheng <dongsheng.wang@freescale.com>
>
> P1020, P1021, P1022, P1023 when the lbc get error, the error
> interrupt will be triggered. The corresponding interrupt is
> internal IRQ0. So system have to process the lbc IRQ0 interrupt.
>
> The corresponding lbc general interrupt is internal IRQ3.
>
> Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
>
> diff --git a/arch/powerpc/boot/dts/fsl/p1020si-post.dtsi b/arch/powerpc/boot/dts/fsl/p1020si-post.dtsi
> index 68cc5e7..13f209f 100644
> --- a/arch/powerpc/boot/dts/fsl/p1020si-post.dtsi
> +++ b/arch/powerpc/boot/dts/fsl/p1020si-post.dtsi
> @@ -36,7 +36,8 @@
> #address-cells = <2>;
> #size-cells = <1>;
> compatible = "fsl,p1020-elbc", "fsl,elbc", "simple-bus";
> - interrupts = <19 2 0 0>;
> + interrupts = <19 2 0 0
> + 16 2 0 0>;
Minor nit: please bracket individual list elements like so:
interrupts = <19 2 0 0>,
<16 2 0 0>;
Otherwise this looks fine to me.
Thanks,
Mark.
prev parent reply other threads:[~2014-01-07 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 6:26 [PATCH 1/2] powerpc/dts: fix lbc lack of error interrupt Dongsheng Wang
2014-01-07 10:34 ` Mark Rutland [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=20140107103447.GC2930@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dongsheng.wang@freescale.com \
--cc=galak@codeaurora.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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).