From: Alek Du <alek.du@intel.com>
To: Ben Dooks <ben-linux@fluff.org>
Cc: Florian Fainelli <florian@openwrt.org>,
Ben Dooks <ben-linux@fluff.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpiolib: Add gpio_detect, gpio_debounce and gpio_alt_func features to GPIOLIB
Date: Tue, 16 Jun 2009 16:51:35 +0800 [thread overview]
Message-ID: <20090616165135.2ef993a4@dxy.sh.intel.com> (raw)
In-Reply-To: <20090616084524.GC14476@trinity.fluff.org>
On Tue, 16 Jun 2009 16:45:24 +0800
Ben Dooks <ben-linux@fluff.org> wrote:
under set_type callback.
>
> Somehow you are still missing my point, this is the way it can be done
> at the moment, without any extension to the API!
>
> int attach_my_gpio_irq(int gpio, void *irqpw)
> {
> int ret;
> int irq;
>
> irq = gpio_to_irq(gpio);
> if (irq < 0) {
> printk(KERN_ERR "%s: no gpio irq available\n", __func__);
> return irq;
> }
>
> ret = request_irq(irq, my_irq_handler, IRQF_TRIGGER_FALLING,
> "mygpio", irqpw);
> if (ret < 0)
> printk(KERN_ERR "%s: cannot request irq\n", __func__);
>
> return ret;
> }
>
I mean, in the set_type of the irq_chip driver, you need to call something like rb532_gpio_set_ilevel.
The GPIO driver needs to export rb532_gpio_set_ilevel, and this is specific to each GPIO driver. Ideally,
I should always call gpio_detect(gpio, ...) here.
static int rb532_set_type(unsigned int irq_nr, unsigned type)
{
int gpio = irq_nr - GPIO_MAPPED_IRQ_BASE;
int group = irq_to_group(irq_nr);
if (group != GPIO_MAPPED_IRQ_GROUP || irq_nr > (GROUP4_IRQ_BASE + 13))
return (type == IRQ_TYPE_LEVEL_HIGH) ? 0 : -EINVAL;
switch (type) {
case IRQ_TYPE_LEVEL_HIGH:
rb532_gpio_set_ilevel(1, gpio);
break;
case IRQ_TYPE_LEVEL_LOW:
rb532_gpio_set_ilevel(0, gpio);
break;
default:
return -EINVAL;
}
return 0;
}
next prev parent reply other threads:[~2009-06-16 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 9:15 [PATCH] gpiolib: Add gpio_detect, gpio_debounce and gpio_alt_func features to GPIOLIB Alek Du
2009-06-15 9:50 ` Ben Dooks
2009-06-15 10:02 ` Mark Brown
2009-06-15 11:19 ` Alek Du
2009-06-15 12:56 ` Florian Fainelli
2009-06-15 12:50 ` Ben Dooks
2009-06-15 13:07 ` Mark Brown
2009-06-15 11:29 ` Alek Du
2009-06-15 12:51 ` Ben Dooks
2009-06-15 13:04 ` Florian Fainelli
2009-06-15 13:09 ` Ben Dooks
2009-06-16 1:28 ` Alek Du
2009-06-16 8:39 ` Ben Dooks
2009-06-17 6:59 ` [PATCH v2] gpiolib: Add " Alek Du
2009-06-17 9:36 ` Ben Nizette
2009-06-16 1:21 ` [PATCH] gpiolib: Add gpio_detect, " Alek Du
2009-06-16 8:45 ` Ben Dooks
2009-06-16 8:51 ` Alek Du [this message]
2009-06-16 9:02 ` Ben Dooks
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=20090616165135.2ef993a4@dxy.sh.intel.com \
--to=alek.du@intel.com \
--cc=ben-linux@fluff.org \
--cc=florian@openwrt.org \
--cc=linux-kernel@vger.kernel.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