From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] [POWERPC] mpic: deal with bogus NIRQ in Feature Reporting Register
Date: Wed, 21 May 2008 17:01:48 -0400 [thread overview]
Message-ID: <1211403708.8297.251.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0805211559110.31758@blarg.am.freescale.net>
On Wed, 2008-05-21 at 15:59 -0500, Kumar Gala wrote:
> Some chips (like the SoCs from Freescale) report the wrong value in NIRQ
> and this causes issues if its doesn't match or exceed the value of
> irq_count.
>
> Add a flag that board code can set to just use irq_count instead of
> FRR[NIRQ]. Eventually we'll add a device tree property with the number
> of sources.
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
> Screw up with git on the first version.
>
> - k
>
> arch/powerpc/sysdev/mpic.c | 9 ++++++---
> include/asm-powerpc/mpic.h | 2 ++
> 2 files changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/arch/powerpc/sysdev/mpic.c b/arch/powerpc/sysdev/mpic.c
> index 8619f2a..12e285d 100644
> --- a/arch/powerpc/sysdev/mpic.c
> +++ b/arch/powerpc/sysdev/mpic.c
> @@ -1144,9 +1144,12 @@ struct mpic * __init mpic_alloc(struct device_node *node,
> mpic->num_cpus = ((greg_feature & MPIC_GREG_FEATURE_LAST_CPU_MASK)
> >> MPIC_GREG_FEATURE_LAST_CPU_SHIFT) + 1;
> if (isu_size == 0)
> - mpic->num_sources =
> - ((greg_feature & MPIC_GREG_FEATURE_LAST_SRC_MASK)
> - >> MPIC_GREG_FEATURE_LAST_SRC_SHIFT) + 1;
> + if (flags & MPIC_BROKEN_FRR_NIRQS)
> + mpic->num_sources = mpic->irq_count;
> + else
> + mpic->num_sources =
> + ((greg_feature & MPIC_GREG_FEATURE_LAST_SRC_MASK)
> + >> MPIC_GREG_FEATURE_LAST_SRC_SHIFT) + 1;
>
> /* Map the per-CPU registers */
> for (i = 0; i < mpic->num_cpus; i++) {
> diff --git a/include/asm-powerpc/mpic.h b/include/asm-powerpc/mpic.h
> index 943c5a3..6802570 100644
> --- a/include/asm-powerpc/mpic.h
> +++ b/include/asm-powerpc/mpic.h
> @@ -353,6 +353,8 @@ struct mpic
> #define MPIC_ENABLE_MCK 0x00000200
> /* Disable bias among target selection, spread interrupts evenly */
> #define MPIC_NO_BIAS 0x00000400
> +/* Ignore NIRQS as reported by FRR */
> +#define MPIC_BROKEN_FRR_NIRQS 0x00000800
>
> /* MPIC HW modification ID */
> #define MPIC_REGSET_MASK 0xf0000000
next prev parent reply other threads:[~2008-05-21 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 20:59 [PATCH v2] [POWERPC] mpic: deal with bogus NIRQ in Feature Reporting Register Kumar Gala
2008-05-21 21:01 ` Benjamin Herrenschmidt [this message]
2008-05-23 2:15 ` [PATCH v2] [POWERPC] mpic: deal with bogus NIRQ in FeatureReporting Register Jin Zhengxiong
2008-05-23 3:31 ` Kumar Gala
2008-05-23 8:34 ` Jin Zhengxiong
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=1211403708.8297.251.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@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).