public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
	Samuel Ortiz <sameo@linux.intel.com>,
	uclinux-dist-devel@blackfin.uclinux.org,
	linux-kernel@vger.kernel.org, Bryan Wu <cooloney@kernel.org>
Subject: Re: [PATCH v3] mfd: ADP5520 Multifunction LCD Backlight and KeypadInput Device Driver
Date: Tue, 6 Oct 2009 14:58:37 +0100	[thread overview]
Message-ID: <20091006135836.GA3926@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <8A42379416420646B9BFAC9682273B6D0E3F4420@limkexm3.ad.analog.com>

On Tue, Oct 06, 2009 at 01:55:45PM +0100, Hennerich, Michael wrote:
> >From: Mark Brown [mailto:broonie@opensource.wolfsonmicro.com]

> >I'm not sure what the association with virtual gpios is?  This is all
> >separate to gpiolib except in that it would mean that a gpio driver for
> >the device would be able to export these interrupts to its clients.

> This is what I meant.
> So you propose having the MFD Core as well as its subdevs requesting the
> ADP5520 IRQ (client->irq) IRQF_SHARED? I think we already excluded us
> from using this option when we were asked to move to the NEW threaded
> irqs?

No, I'm suggesting implementing an IRQ controller driver for the device
- register an irq_chip for the interrupt controller on it.  Support for
doing this on I2C devices was added at pretty much the same time as the
IRQ_ONESHOT support.  This gives access to all the genirq infrastrure
features rather than having to implement a custom IRQ handling stack.

Like I say, I'm not sure what you meant when you were talking about
virtual gpios.

  reply	other threads:[~2009-10-06 13:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 18:27 [PATCH] mfd: ADP5520 Multifunction LCD Backlight and Keypad Input Device Driver Mike Frysinger
2009-09-23  5:11 ` [PATCH v2] " Mike Frysinger
2009-09-29 21:04   ` [Uclinux-dist-devel] " Mike Frysinger
2009-09-29 21:14     ` Andrew Morton
2009-09-29 21:19       ` Mike Frysinger
2009-09-29 21:31       ` Samuel Ortiz
2009-09-29 21:19   ` Andrew Morton
2009-09-29 21:57     ` Hennerich, Michael
2009-10-01 14:09   ` Samuel Ortiz
2009-10-02  9:38     ` Hennerich, Michael
2009-10-02 13:15       ` Samuel Ortiz
2009-10-02 14:39         ` Hennerich, Michael
2009-10-02 13:48       ` [Uclinux-dist-devel] [PATCH v2] mfd: ADP5520 Multifunction LCDBacklight " Hennerich, Michael
2009-10-02 14:05         ` Samuel Ortiz
2009-10-02 14:27         ` Mark Brown
2009-10-02 14:37           ` [Uclinux-dist-devel] [PATCH v2] mfd: ADP5520 MultifunctionLCDBacklight " Hennerich, Michael
2009-10-02 14:38             ` Mark Brown
2009-10-02 15:24               ` [Uclinux-dist-devel] [PATCH v2] mfd: ADP5520MultifunctionLCDBacklight " Hennerich, Michael
2009-10-06  7:44   ` [PATCH v3] mfd: ADP5520 Multifunction LCD Backlight " Mike Frysinger
2009-10-06 11:55     ` Mark Brown
2009-10-06 12:23       ` [PATCH v3] mfd: ADP5520 Multifunction LCD Backlight and KeypadInput " Hennerich, Michael
2009-10-06 12:36         ` Mark Brown
2009-10-06 12:55           ` Hennerich, Michael
2009-10-06 13:58             ` Mark Brown [this message]
2009-10-06 14:32               ` Hennerich, Michael
2009-10-06 14:48                 ` Mark Brown
2009-10-06 15:05                   ` Hennerich, Michael
2009-10-06 16:05                     ` Mark Brown
2009-10-07  8:50                       ` Hennerich, Michael
2009-10-07 10:06                         ` Mark Brown
2009-10-07 12:11                           ` Hennerich, Michael
2009-10-07 13:03                             ` Mark Brown
2009-10-07 13:01                           ` Hennerich, Michael
2009-10-07 13:19                             ` Mark Brown
2009-10-07 13:35                               ` Hennerich, Michael

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=20091006135836.GA3926@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=cooloney@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.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