From: Greg Ungerer <gerg@snapgear.com>
To: Steven King <sfking@fdwdc.com>
Cc: uClinux development list <uclinux-dev@uclinux.org>,
linux-m68k <linux-m68k@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] m68knommu: get rid of __do_IRQ and add support for using gpio irqs.
Date: Mon, 11 Jan 2010 13:48:59 +1000 [thread overview]
Message-ID: <4B4A9FAB.5020109@snapgear.com> (raw)
In-Reply-To: <200912161915.39692.sfking@fdwdc.com>
Hi Steven,
Steven King wrote:
> Since we now have generic irq support for m68knommu and as __do_IRQ is
> supposed to go away real soon now, I added config GENERIC_HARDIRQS_NO__DO_IRQ
> to m68knommu/Kconfig. Unfortunately, that produced an unbootable kernel --
> looking at the code for generic_handle_irq in linux/irq.h, the NO__DO_IRQ
> version unconditionally calls desc->handle_irq, which suggests that an irq's
> handle_irq isnt getting initialized in the early boot and indeed, adding an
> initialization of handle_irq in init_IRQ produced a working system.
>
> I'm not entirely satisfied with that solution as it ignores why we are getting
> an irq when no handler has been setup for it, but in any case, using
> set_irq_chip_and_handler in init_IRQ to initialize all the handlers is the
> right thing to do (or atleast, its what all the other arches do) (and I didnt
> feel like digging out the BDM pod to figure out where the mystery irq is
> coming from).
>
> Then the real reason I was digging into the irq code is to add support for
> using gpio irqs on the gpios of the parts that support that. The following
> patch is against
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git for-next
>
> only the intc-2 gpio irqs have been tested on real hardware.
>
> ------------------------------
>
> Get rid of __do_IRQ; use set_irq_chip_and_handler to initialize irqs. Add
> support for using gpio irqs and setting the edge on external irqs generally.
>
> Signed-off-by: Steven King <sfking@fdwdc.com>
Applied to the for-linus and for-next branches of the m68knommu git
tree.
Thanks
Greg
> --
>
> arch/m68k/include/asm/m520xsim.h | 3 +
> arch/m68k/include/asm/m523xsim.h | 3 +
> arch/m68k/include/asm/m5249sim.h | 4 +-
> arch/m68k/include/asm/m527xsim.h | 3 +
> arch/m68knommu/Kconfig | 4 ++
> arch/m68knommu/platform/5272/intc.c | 39 +++++++++++---
> arch/m68knommu/platform/68328/ints.c | 8 +--
> arch/m68knommu/platform/68360/ints.c | 8 +--
> arch/m68knommu/platform/coldfire/intc-2.c | 76 ++++++++++++++++++++++++--
> arch/m68knommu/platform/coldfire/intc-simr.c | 68 ++++++++++++++++++++++--
> arch/m68knommu/platform/coldfire/intc.c | 59 +++++++++++++++++++--
> 11 files changed, 239 insertions(+), 36 deletions(-)
>
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
prev parent reply other threads:[~2010-01-11 3:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 3:15 [PATCH] m68knommu: get rid of __do_IRQ and add support for using gpio irqs Steven King
2009-12-17 14:03 ` Greg Ungerer
2010-01-11 3:48 ` Greg Ungerer [this message]
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=4B4A9FAB.5020109@snapgear.com \
--to=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sfking@fdwdc.com \
--cc=uclinux-dev@uclinux.org \
/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