> -----Original Message-----
> From: Kumar Gala [mailto:ga...@kernel.crashing.org]
> Sent: Monday, August 06, 2012 9:23 PM
> To: Sethi Varun-B16395
> Cc: linuxppc-dev@lists.ozlabs.org; Hamciuc Bogdan-BHAMCIU1
> Subject: Re: [PATCH 3/3 v4] powerpc/mpic: FSL MPIC error interrupt
> support.
> 
> 
> On Aug 6, 2012, at 7:44 AM, Varun Sethi wrote:
> 
> > All SOC device error interrupts are muxed and delivered to the core as
> > a single MPIC error interrupt. Currently all the device drivers
> > requiring access to device errors have to register for the MPIC error
> > interrupt as a shared interrupt.
> >
> > With this patch we add interrupt demuxing capability in the mpic
> > driver, allowing device drivers to register for their individual error
> interrupts.
> > This is achieved by handling error interrupts in a cascaded fashion.
> >
> > MPIC error interrupt is handled by the "error_int_handler", which
> > subsequently demuxes it using the EISR and delivers it to the
> > respective drivers.
> >
> > The error interrupt capability is dependent on the MPIC EIMR register,
> > which was introduced in FSL MPIC version 4.1 (P4080 rev2). So, error
> > interrupt demuxing capability is dependent on the MPIC version and can
> > be used for versions >= 4.1.
> >
> > Signed-off-by: Varun Sethi <varun.se...@freescale.com>
> > Signed-off-by: Bogdan Hamciuc <bogdan.hamc...@freescale.com> [In the
> > initial version of the patch we were using handle_simple_irq as the
> > handler for cascaded error interrupts, this resulted in issues in case
> > of threaded isrs (with RT kernel). This issue was debugged by Bogdan
> > and decision was taken to use the handle_level_irq handler]
> > ---
> > arch/powerpc/include/asm/mpic.h    |   16 ++++
> > arch/powerpc/sysdev/Makefile       |    2 +-
> > arch/powerpc/sysdev/fsl_mpic_err.c |  153
> ++++++++++++++++++++++++++++++++++++
> > arch/powerpc/sysdev/mpic.c         |   45 ++++++++++-
> > arch/powerpc/sysdev/mpic.h         |   22 +++++
> > 5 files changed, 236 insertions(+), 2 deletions(-) create mode 100644
> > arch/powerpc/sysdev/fsl_mpic_err.c
> >
> > diff --git a/arch/powerpc/include/asm/mpic.h
> > b/arch/powerpc/include/asm/mpic.h index e14d35d..6c8e53b 100644
> > --- a/arch/powerpc/include/asm/mpic.h
> > +++ b/arch/powerpc/include/asm/mpic.h
> > @@ -118,6 +118,9 @@
> > #define MPIC_MAX_CPUS               32
> > #define MPIC_MAX_ISU                32
> >
> > +#define MPIC_MAX_ERR      32
> > +#define MPIC_FSL_ERR_INT  16
> > +
> > /*
> >  * Tsi108 implementation of MPIC has many differences from the
> > original one  */ @@ -270,6 +273,7 @@ struct mpic
> >     struct irq_chip         hc_ipi;
> > #endif
> >     struct irq_chip         hc_tm;
> > +   struct irq_chip         hc_err;
> >     const char              *name;
> >     /* Flags */
> >     unsigned int            flags;
> > @@ -283,6 +287,8 @@ struct mpic
> >     /* vector numbers used for internal sources (ipi/timers) */
> >     unsigned int            ipi_vecs[4];
> >     unsigned int            timer_vecs[8];
> > +   /* vector numbers used for FSL MPIC error interrupts */
> > +   unsigned int            err_int_vecs[MPIC_MAX_ERR];
> >
> >     /* Spurious vector to program into unused sources */
> >     unsigned int            spurious_vec;
> > @@ -306,6 +312,11 @@ struct mpic
> >     struct mpic_reg_bank    cpuregs[MPIC_MAX_CPUS];
> >     struct mpic_reg_bank    isus[MPIC_MAX_ISU];
> >
> > +   /* ioremap'ed base for error interrupt registers */
> > +   u32 __iomem     *err_regs;
> > +   /* error interrupt config */
> > +   u32                     err_int_config_done;
> 
> I thought we were going to remove this as it don't really provide any
> value.
> 
[Sethi Varun-B16395] We need a way to determine that irq handle got registered 
for 
Mpic error interrupt, only then can we go ahead and assign individual (cascaded)
error interrupts. Initially we were doing the same thing while translating 
error interrupt specifier, now we are registering the handler in mpic_init.

-Varun 

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Reply via email to