From: Denis Turischev <denis@compulab.co.il>
To: LKML <linux-kernel@vger.kernel.org>
Cc: David Brownell <dbrownell@users.sourceforge.net>
Subject: [PATCH 1/2] gpio: SIO IT8761, Poulsbo SCH are I/O mapped
Date: Wed, 30 Jun 2010 18:23:27 +0300 [thread overview]
Message-ID: <4C2B616F.90803@compulab.co.il> (raw)
In-Reply-To: <4B8A2F34.3020505@compulab.co.il>
Super I/O IT8761 and Poulsbo SCH expanders look like I/O mapped
and not memory mapped.
Signed-off-by: Denis Turischev <denis@compulab.co.il>
---
drivers/gpio/Kconfig | 14 ++++++++------
1 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
index 724038d..f666023 100644
--- a/drivers/gpio/Kconfig
+++ b/drivers/gpio/Kconfig
@@ -70,12 +70,6 @@ config GPIO_MAX730X
comment "Memory mapped GPIO expanders:"
-config GPIO_IT8761E
- tristate "IT8761E GPIO support"
- depends on GPIOLIB
- help
- Say yes here to support GPIO functionality of IT8761E super I/O chip.
-
config GPIO_PL061
bool "PrimeCell PL061 GPIO support"
depends on ARM_AMBA
@@ -94,6 +88,14 @@ config GPIO_VR41XX
help
Say yes here to support the NEC VR4100 series General-purpose I/O Uint
+comment "I/O mapped GPIO expanders:"
+
+config GPIO_IT8761E
+ tristate "IT8761E GPIO support"
+ depends on GPIOLIB
+ help
+ Say yes here to support GPIO functionality of IT8761E super I/O chip.
+
config GPIO_SCH
tristate "Intel SCH GPIO"
depends on GPIOLIB && PCI
--
1.7.0.4
next prev parent reply other threads:[~2010-06-30 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 8:54 [RESEND] gpio: introduce it8761e_gpio driver for IT8761E Super I/O chip Denis Turischev
2010-03-02 22:40 ` Andrew Morton
2010-03-17 10:09 ` it8761e_gpio: Fixed bug in gpio numbering Denis Turischev
2010-04-28 8:24 ` Denis Turischev
2010-06-30 15:23 ` Denis Turischev [this message]
2010-06-30 16:17 ` [PATCH 2/2] gpio: introduce f71808e_gpio driver for F71808E Super I/O chip Denis Turischev
2010-06-30 16:37 ` David Brownell
2010-07-01 10:06 ` Denis Turischev
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=4C2B616F.90803@compulab.co.il \
--to=denis@compulab.co.il \
--cc=dbrownell@users.sourceforge.net \
--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.