From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: sameo@linux.intel.com, patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] mfd: arizona: Add additional dummy IRQ callbacks
Date: Thu, 21 Aug 2014 13:05:54 +0100 [thread overview]
Message-ID: <20140821120554.GC7328@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20140821115631.GA4266@lee--X1>
On Thu, Aug 21, 2014 at 12:56:31PM +0100, Lee Jones wrote:
> On Tue, 12 Aug 2014, Charles Keepax wrote:
> > static struct irq_chip arizona_irq_chip = {
> > .name = "arizona",
> > - .irq_disable = arizona_irq_disable,
> > - .irq_enable = arizona_irq_enable,
> > + .irq_disable = arizona_irq_dummy,
> > + .irq_enable = arizona_irq_dummy,
> > + .irq_ack = arizona_irq_dummy,
> > + .irq_mask = arizona_irq_dummy,
> > + .irq_unmask = arizona_irq_dummy,
>
> If you provide .irq_enable(), then .irq_unmask becomes redundant
> and/or is checked for before invoking. There is a chance of
> .irq_mask() being called, but if this is a problem, it should be fixed
> in the IRQ Chip code. There is also one unprotected invocation of
> .irq_ack(), but I think this should be fixed rather than forcing each
> user of IRQ Chip to provide all of these call-backs.
Cool I will look at doing some fixups in the IRQ code and see
where that gets me to.
Thanks,
Charles
next prev parent reply other threads:[~2014-08-21 12:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 13:51 [PATCH 1/4] mfd: arizona: Add additional dummy IRQ callbacks Charles Keepax
2014-08-12 13:51 ` [PATCH 2/4] mfd: arizona: Propagate irq_wake through to parent IRQ Charles Keepax
2014-08-21 11:57 ` Lee Jones
2014-08-12 13:51 ` [PATCH 3/4] mfd: arizona: Avoid use of legacy IRQ mapping Charles Keepax
2014-08-21 11:59 ` Lee Jones
2014-08-12 13:51 ` [PATCH 4/4] mfd: arizona: Mark additional registers as volatile Charles Keepax
2014-08-13 9:22 ` Charles Keepax
2014-08-21 11:56 ` [PATCH 1/4] mfd: arizona: Add additional dummy IRQ callbacks Lee Jones
2014-08-21 12:05 ` Charles Keepax [this message]
2014-09-02 14:09 ` Charles Keepax
2014-09-02 14:26 ` Lee Jones
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=20140821120554.GC7328@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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).