From: Samuel Ortiz <sameo@linux.intel.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Paul Mundt <lethal@linux-sh.org>,
Rabin Vincent <rabin.vincent@stericsson.com>
Subject: [PATCH] mfd: Use dummy_irq_chip for tc3589x
Date: Mon, 20 Dec 2010 13:09:20 +0100 [thread overview]
Message-ID: <20101220120918.GF11095@sortiz-mobl> (raw)
This also converts tc3589x to the new irq API.
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
---
Linus, this should go through your ux500-core branch as this is where the
tc3589x rename happens.
(Patch resent with Linus Walleij's correct email address)
---
drivers/mfd/tc3589x.c | 13 +------------
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git a/drivers/mfd/tc3589x.c b/drivers/mfd/tc3589x.c
index 32291fe..112efd3 100644
--- a/drivers/mfd/tc3589x.c
+++ b/drivers/mfd/tc3589x.c
@@ -170,17 +170,6 @@ again:
return IRQ_HANDLED;
}
-static void tc3589x_irq_dummy(unsigned int irq)
-{
- /* No mask/unmask at this level */
-}
-
-static struct irq_chip tc3589x_irq_chip = {
- .name = "tc3589x",
- .mask = tc3589x_irq_dummy,
- .unmask = tc3589x_irq_dummy,
-};
-
static int tc3589x_irq_init(struct tc3589x *tc3589x)
{
int base = tc3589x->irq_base;
@@ -188,7 +177,7 @@ static int tc3589x_irq_init(struct tc3589x *tc3589x)
for (irq = base; irq < base + TC3589x_NR_INTERNAL_IRQS; irq++) {
set_irq_chip_data(irq, tc3589x);
- set_irq_chip_and_handler(irq, &tc3589x_irq_chip,
+ set_irq_chip_and_handler(irq, &dummy_irq_chip,
handle_edge_irq);
set_irq_nested_thread(irq, 1);
#ifdef CONFIG_ARM
--
1.7.2.3
--
Intel Open Source Technology Centre
http://oss.intel.com/
next reply other threads:[~2010-12-20 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 12:09 Samuel Ortiz [this message]
2010-12-20 12:35 ` [PATCH] mfd: Use dummy_irq_chip for tc3589x Linus WALLEIJ
2010-12-20 13:11 ` Samuel Ortiz
-- strict thread matches above, loose matches on Subject: below --
2010-12-20 12:01 Samuel Ortiz
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=20101220120918.GF11095@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=lethal@linux-sh.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin.vincent@stericsson.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 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.