From: Jisheng Zhang <jszhang@marvell.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Jason Cooper <jason@lakedaemon.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch] irqchip/dw-apb-ictl: Fix generic domain chip wreckage
Date: Mon, 6 Jul 2015 21:04:11 +0800 [thread overview]
Message-ID: <20150706210411.6ee1cbe0@xhacker> (raw)
In-Reply-To: <alpine.DEB.2.11.1507061450210.3916@nanos>
On Mon, 6 Jul 2015 14:55:43 +0200
Thomas Gleixner <tglx@linutronix.de> wrote:
> On Mon, 6 Jul 2015, Thomas Gleixner wrote:
> > On Mon, 6 Jul 2015, Jisheng Zhang wrote:
> > > > Thomas Gleixner <tglx@linutronix.de> wrote:
> > > the following patch seems fix the panic, but I dunno whether it's correct or not,
> > > could you please help to check?
> > >
> > > Thanks,
> > > Jisheng
> > >
> > > diff --git a/drivers/irqchip/irq-dw-apb-ictl.c b/drivers/irqchip/irq-dw-apb-ictl.c
> > > index f4a0e11..8d996cb 100644
> > > --- a/drivers/irqchip/irq-dw-apb-ictl.c
> > > +++ b/drivers/irqchip/irq-dw-apb-ictl.c
> > > @@ -30,13 +30,14 @@
> > > static void dw_apb_ictl_handler(unsigned int irq, struct irq_desc *desc)
> > > {
> > > struct irq_domain *d = irq_desc_get_handler_data(desc);
> > > - struct irq_chip_generic *gc = irq_get_domain_generic_chip(d, 0);
> > > + struct irq_chip_generic *gc;
> > > struct irq_chip *chip = irq_desc_get_chip(desc);
> > > int n;
> > >
> > > chained_irq_enter(chip, desc);
> > >
> > > - for (n = 0; n < d->gc->num_chips; n++, gc++) {
> > > + for (n = 0; n < d->gc->num_chips; n++) {
> > > + gc = irq_get_domain_generic_chip(d, n * 32);
> > > u32 stat = readl_relaxed(gc->reg_base + APB_INT_FINALSTATUS_L);
> >
> > Yes it's correct. Seems I tried to be overly clever by avoiding the
> > lookup of the second chip. Will fold back.
>
> Hmm. That does not make sense because the real issue is here:
>
> - for (i = 0; i < nrirqs / 32; i++) {
> + for (i = 0; i < DIV_ROUND_UP(nrirqs, 32); i++) {
>
OOPS, we need the above DIV_ROUND_UP fix. But...
On Berlin SoC, nrirqs = 64, so it doesn't make difference and we get the same
panic.
Thanks,
Jisheng
next prev parent reply other threads:[~2015-07-06 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 10:18 [patch] irqchip/dw-apb-ictl: Fix generic domain chip wreckage Thomas Gleixner
2015-07-06 12:07 ` Jisheng Zhang
2015-07-06 12:31 ` Jisheng Zhang
2015-07-06 12:36 ` Thomas Gleixner
2015-07-06 12:45 ` Jisheng Zhang
2015-07-06 12:55 ` Thomas Gleixner
2015-07-06 13:04 ` Jisheng Zhang [this message]
2015-07-06 13:24 ` Thomas Gleixner
2015-07-06 13:32 ` Thomas Gleixner
2015-07-06 13:43 ` Jisheng Zhang
2015-07-11 21:30 ` [tip:irq/core] " tip-bot for Thomas Gleixner
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=20150706210411.6ee1cbe0@xhacker \
--to=jszhang@marvell.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tglx@linutronix.de \
/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