From: Randy Dunlap <randy.dunlap@oracle.com>
To: Gregory Bean <gbean@codeaurora.org>
Cc: akpm@linux-foundation.org, david-b@pacbell.net,
khali@linux-fr.org, linux-i2c@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] gpio: sx150x: Add Semtech I2C sx150x gpio expander driver.
Date: Thu, 22 Jul 2010 10:17:53 -0700 [thread overview]
Message-ID: <20100722101753.c73604eb.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1279818771-9428-1-git-send-email-gbean@codeaurora.org>
On Thu, 22 Jul 2010 10:12:51 -0700 Gregory Bean wrote:
> drivers/gpio/Kconfig | 11 +
> drivers/gpio/Makefile | 1 +
> drivers/gpio/sx150x.c | 645 ++++++++++++++++++++++++++++++++++++++++++++
> include/linux/i2c/sx150x.h | 78 ++++++
> 4 files changed, 735 insertions(+), 0 deletions(-)
> create mode 100644 drivers/gpio/sx150x.c
> create mode 100644 include/linux/i2c/sx150x.h
>
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index 7face91..f623953 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -195,6 +195,17 @@ config GPIO_PCF857X
> This driver provides an in-kernel interface to those GPIOs using
> platform-neutral GPIO calls.
>
> +config GPIO_SX150X
> + bool "Semtech SX150x I2C GPIO expander"
> + depends on I2C=y
> + default n
> + help
> + Say yes here to provide support for Semtech SX150-series I2C
> + GPIO expanders. Compatible models include:
Just curious, not complaining, but why does this driver (and some others)
need to be built-in instead of having the option of being built as a
loadable module?
> + 8 bits: sx1508q
> + 16 bits: sx1509q
> +
> config GPIO_TC35892
> bool "TC35892 GPIOs"
> depends on MFD_TC35892
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
WARNING: multiple messages have this Message-ID (diff)
From: randy.dunlap@oracle.com (Randy Dunlap)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] gpio: sx150x: Add Semtech I2C sx150x gpio expander driver.
Date: Thu, 22 Jul 2010 10:17:53 -0700 [thread overview]
Message-ID: <20100722101753.c73604eb.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1279818771-9428-1-git-send-email-gbean@codeaurora.org>
On Thu, 22 Jul 2010 10:12:51 -0700 Gregory Bean wrote:
> drivers/gpio/Kconfig | 11 +
> drivers/gpio/Makefile | 1 +
> drivers/gpio/sx150x.c | 645 ++++++++++++++++++++++++++++++++++++++++++++
> include/linux/i2c/sx150x.h | 78 ++++++
> 4 files changed, 735 insertions(+), 0 deletions(-)
> create mode 100644 drivers/gpio/sx150x.c
> create mode 100644 include/linux/i2c/sx150x.h
>
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index 7face91..f623953 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -195,6 +195,17 @@ config GPIO_PCF857X
> This driver provides an in-kernel interface to those GPIOs using
> platform-neutral GPIO calls.
>
> +config GPIO_SX150X
> + bool "Semtech SX150x I2C GPIO expander"
> + depends on I2C=y
> + default n
> + help
> + Say yes here to provide support for Semtech SX150-series I2C
> + GPIO expanders. Compatible models include:
Just curious, not complaining, but why does this driver (and some others)
need to be built-in instead of having the option of being built as a
loadable module?
> + 8 bits: sx1508q
> + 16 bits: sx1509q
> +
> config GPIO_TC35892
> bool "TC35892 GPIOs"
> depends on MFD_TC35892
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-07-22 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 17:12 [PATCH v4] gpio: sx150x: Add Semtech I2C sx150x gpio expander driver Gregory Bean
2010-07-22 17:12 ` Gregory Bean
2010-07-22 17:17 ` Randy Dunlap [this message]
2010-07-22 17:17 ` Randy Dunlap
2010-07-22 17:22 ` Greg Bean
2010-07-22 17:22 ` Greg Bean
2010-07-22 17:22 ` Greg Bean
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=20100722101753.c73604eb.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=gbean@codeaurora.org \
--cc=khali@linux-fr.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.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.