From: Florian Fainelli <f.fainelli@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, jason@lakedaemon.net,
computersforpeace@gmail.com
Subject: Re: [PATCH 1/2] irqchip: add Broadcom BCM7120-style Level 2 interrupt controller
Date: Wed, 03 Sep 2014 09:39:40 -0700 [thread overview]
Message-ID: <5407444C.2080107@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1409031413230.3333@nanos>
On 09/03/2014 05:18 AM, Thomas Gleixner wrote:
> On Thu, 28 Aug 2014, Florian Fainelli wrote:
>> +static void bcm7120_l2_intc_irq_handle(unsigned int irq, struct irq_desc *desc)
>> +{
>> + struct bcm7120_l2_intc_data *b = irq_desc_get_handler_data(desc);
>> + struct irq_chip *chip = irq_desc_get_chip(desc);
>> + struct irq_chip_generic *gc = irq_get_domain_generic_chip(b->domain, 0);
>> + u32 status;
>> +
>> + chained_irq_enter(chip, desc);
>> +
>> + irq_gc_lock(gc);
>> + status = __raw_readl(b->base + IRQSTAT);
>> + irq_gc_unlock(gc);
>
> Why do you need locking around the status read out?
I was worried about potential concurrency issues, but I suppose that
this is just extra carefulness that brings nothing.
>
>> + for (irq = 0; irq < num_parent_irqs; irq++) {
>> + ret = bcm7120_l2_intc_init_one(dn, data, irq, map_mask);
>> + if (ret)
>> + continue;
>
> What's the exact purpose of this "if (ret)" construct?
It's pretty much useless the way it is now, I will rework that.
Thanks for the review!
--
Florian
next prev parent reply other threads:[~2014-09-03 16:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 22:35 [PATCH 0/2] irqchip: Broadcom BCM7120-style Level 2 interrupt controller Florian Fainelli
2014-08-28 22:35 ` [PATCH 1/2] irqchip: add " Florian Fainelli
2014-09-03 12:18 ` Thomas Gleixner
2014-09-03 16:39 ` Florian Fainelli [this message]
2014-08-28 22:35 ` [PATCH 2/2] Documentation: bcm7120-l2: Add Broadcom BCM7120-style L2 binding Florian Fainelli
[not found] ` <1409265326-7579-3-git-send-email-f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-03 12:13 ` Thomas Gleixner
2014-09-03 12:13 ` Thomas Gleixner
2014-09-03 12:43 ` Mark Rutland
2014-09-03 16:59 ` Florian Fainelli
[not found] ` <5407490E.7060505-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-05 9:05 ` Mark Rutland
2014-09-05 9:05 ` Mark Rutland
2014-09-05 18:01 ` Florian Fainelli
[not found] ` <5409FA82.6000703-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-05 19:21 ` Thomas Gleixner
2014-09-05 19:21 ` Thomas Gleixner
2014-09-05 19:57 ` Florian Fainelli
2014-09-05 19:57 ` Florian Fainelli
2014-09-05 20:44 ` Thomas Gleixner
2014-09-05 21:15 ` Florian Fainelli
2014-09-05 21:15 ` Florian Fainelli
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=5407444C.2080107@gmail.com \
--to=f.fainelli@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.