From: Alek Du <alek.du@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Brownell <david-b@pacbell.net>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH v3] gpio: add Intel Moorestown Platform Langwell chip gpio driver
Date: Fri, 31 Jul 2009 17:02:10 +0800 [thread overview]
Message-ID: <20090731170210.3372ca73@dxy.sh.intel.com> (raw)
In-Reply-To: <20090730035941.16124ec0.akpm@linux-foundation.org>
Andrew,
Sorry for late response. Yes, you are right, there is no meaning to build it as module, it should be changed to bool.
I will submit a new patch soon, I also need a mask handler to irqchip .... otherwise the free_irq will report a error.
Thanks,
Alek
On Thu, 30 Jul 2009 18:59:41 +0800
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 3 Jul 2009 21:07:06 +0800 Alek Du <alek.du@intel.com> wrote:
>
> > Changes from v2:
> > 1. Add missed MODULE_DEVICE_TABLE
> >
> > Changes from v1:
> > 1. driver name changed from lnw.c ==> langwell_gpio.c
> > 2. removed hard coded driver data, now we get it from PCI bar1 (platform init code fills it)
> > 3. removed alternative function setting code, it should be called in platform init part.
> > 4. misc. style clean
> >
> >
> > >From 8eaad3aac8cffda193adcfc4b9fcbb7c461fd4b9 Mon Sep 17 00:00:00 2001
> > From: Alek Du <alek.du@intel.com>
> > Date: Tue, 30 Jun 2009 12:13:27 +0800
> > Subject: [PATCH] gpio: add Intel Moorestown Platform Langwell chip gpio driver
> >
> > The Langwell chip is the IO hub for Intel Moorestown platform which has a
> > 64-pin gpio block device inside. It is exposed as a dedicated PCI device.
> > We use it to control outside peripheral as well as to do IRQ demuxing. The
> > gpio block uses MSI to send level type interrupt to IOAPIC.
>
> The driver breaks the x86-64 allmodconfig build:
>
> ERROR: "irq_to_desc" [drivers/gpio/langwell_gpio.ko] undefined!
> ERROR: "set_irq_chip_and_handler_name" [drivers/gpio/langwell_gpio.ko] undefined!
> ERROR: "handle_simple_irq" [drivers/gpio/langwell_gpio.ko] undefined!
>
> Does it make any sense to build this driver as a module? If not, it
> should be changed to def_bool. If so...
>
>
>
> kernel/irq/chip.c | 2 ++
> kernel/irq/handle.c | 1 +
> 2 files changed, 3 insertions(+)
>
> diff -puN kernel/irq/handle.c~kernel-irq-export-symbols-needed-by-gpio-add-intel-moorestown-platform-langwell-chip-gpio-driverpatch kernel/irq/handle.c
> --- a/kernel/irq/handle.c~kernel-irq-export-symbols-needed-by-gpio-add-intel-moorestown-platform-langwell-chip-gpio-driverpatch
> +++ a/kernel/irq/handle.c
> @@ -192,6 +192,7 @@ struct irq_desc *irq_to_desc(unsigned in
>
> return NULL;
> }
> +EXPORT_SYMBOL(irq_to_desc);
>
> struct irq_desc * __ref irq_to_desc_alloc_node(unsigned int irq, int node)
> {
> diff -puN kernel/irq/chip.c~kernel-irq-export-symbols-needed-by-gpio-add-intel-moorestown-platform-langwell-chip-gpio-driverpatch kernel/irq/chip.c
> --- a/kernel/irq/chip.c~kernel-irq-export-symbols-needed-by-gpio-add-intel-moorestown-platform-langwell-chip-gpio-driverpatch
> +++ a/kernel/irq/chip.c
> @@ -340,6 +340,7 @@ handle_simple_irq(unsigned int irq, stru
> out_unlock:
> spin_unlock(&desc->lock);
> }
> +EXPORT_SYMBOL(handle_simple_irq);
>
> /**
> * handle_level_irq - Level type irq handler
> @@ -609,6 +610,7 @@ set_irq_chip_and_handler_name(unsigned i
> set_irq_chip(irq, chip);
> __set_irq_handler(irq, handle, 0, name);
> }
> +EXPORT_SYMBOL(set_irq_chip_and_handler_name);
>
> void __init set_irq_noprobe(unsigned int irq)
> {
> _
>
>
next prev parent reply other threads:[~2009-07-31 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 13:07 [PATCH v3] gpio: add Intel Moorestown Platform Langwell chip gpio driver Alek Du
2009-07-30 10:59 ` Andrew Morton
2009-07-31 9:02 ` Alek Du [this message]
2009-07-31 13:22 ` [PATCH] mm gpio: Some fixing for Langwell GPIO driver Alek Du
2009-09-17 23:36 ` [PATCH v3] gpio: add Intel Moorestown Platform Langwell chip gpio driver Andrew Morton
2009-09-18 1:18 ` Alek Du
2009-09-18 3:38 ` Andrew Morton
2009-09-18 7:49 ` Russell King
2009-09-18 7:59 ` Alek Du
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=20090731170210.3372ca73@dxy.sh.intel.com \
--to=alek.du@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.