From: Greg KH <greg@kroah.com>
To: Andres Salomon <dilinger@queued.net>
Cc: Greg KH <gregkh@suse.de>,
devel@driverdev.osuosl.org, dsd@laptop.org,
jon.nettleton@gmail.com, linux-geode@lists.infradead.org,
linux-kernel@vger.kernel.org, cjb@laptop.org
Subject: Re: [PATCH 3/4] cs5535: add some additional cs5535-specific GPIO functionality
Date: Wed, 29 Sep 2010 18:05:01 -0700 [thread overview]
Message-ID: <20100930010501.GA28145@kroah.com> (raw)
In-Reply-To: <20100925190712.6aa5c2fc@debxo>
On Sat, Sep 25, 2010 at 07:07:12PM -0700, Andres Salomon wrote:
>
> This adds (well, re-adds actually) handling for events/IRQs through cs5535
> GPIOs. In the wild and wooly world of CS5535, setup_event() is for
> assigning an IRQ to a GPIO filter/event pair, and set_irq() sets up
> the pair to trigger IRQs.
>
> These should really only be used in highly platform-specific drivers (such
> as OLPC's DCON driver). Sadly, because set_irq() uses MSRs, this causes the
> driver to become X86-specific.
>
> Signed-off-by: Andres Salomon <dilinger@queued.net>
> ---
> drivers/gpio/Kconfig | 2 +-
> drivers/gpio/cs5535-gpio.c | 52 ++++++++++++++++++++++++++++++++++++++++++++
> include/linux/cs5535.h | 2 +
I can't take this change without the gpio subsystem maintainer acking
it. Can you get that approval from them?
I'm guessing that your 4/4 patch here depends on it, right? If so, I'll
hold off on applying that patch until we can figure out how to handle
this, ok?
thanks,
greg k-h
next prev parent reply other threads:[~2010-09-30 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 2:07 [PATCH 3/4] cs5535: add some additional cs5535-specific GPIO functionality Andres Salomon
2010-09-30 1:05 ` Greg KH [this message]
2010-09-30 2:46 ` Andres Salomon
2010-09-30 2:56 ` Greg KH
2010-11-12 17:08 ` Andres Salomon
2010-11-12 18:40 ` Greg KH
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=20100930010501.GA28145@kroah.com \
--to=greg@kroah.com \
--cc=cjb@laptop.org \
--cc=devel@driverdev.osuosl.org \
--cc=dilinger@queued.net \
--cc=dsd@laptop.org \
--cc=gregkh@suse.de \
--cc=jon.nettleton@gmail.com \
--cc=linux-geode@lists.infradead.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 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.