All of lore.kernel.org
 help / color / mirror / Atom feed
From: H Hartley Sweeten <hartleys@visionengravers.com>
To: Jamie Iles <jamie@jamieiles.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	Shawn Guo <shawn.guo@freescale.com>,
	Linus Walleij <linus.walleij@stericsson.com>,
	Jonas Aaberg <jonas.aberg@stericsson.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	Lee Jones <lee.jones@linaro.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio
Date: Fri, 20 May 2011 17:07:12 -0500	[thread overview]
Message-ID: <0D753D10438DA54287A00B027084269764D30C10DC@AUSP01VMBX24.collaborationhost.net> (raw)
In-Reply-To: <20110520015022.GA3095@pulham.picochip.com>

On Thursday, May 19, 2011 6:50 PM, Jamie Iles wrote:
>> Jamie Iles (cc'ed) posted some patches that extended the basic_mmio_gpio
>> driver so that it could be used as a library by other gpio drivers.
>> 
>> Jamie, could you re-post that series to the linux-arm-kernel list for
>> review?
>
> Grant has applied these patches but I've put them in a public branch if 
> that's OK rather than reposting:
>
>	git://github.com/jamieiles/linux-2.6-ji.git gpio

Thanks for the link.

I just noticed something in commit fdcd80cb991dac7a70433be1e336726415762b6a
"basic_mmio_gpio: split into a gpio library and platform device".

> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index d3b2953..2186d22 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -70,8 +70,14 @@ config GPIO_MAX730X
>  
>  comment "Memory mapped GPIO expanders:"
>  
> +config GPIO_BASIC_MMIO_CORE
> +       tristate
> +       help
> +         Provides core functionality for basic memory-mapped GPIO controllers.
> +
>  config GPIO_BASIC_MMIO
>         tristate "Basic memory-mapped GPIO controllers support"
> +       select GPIO_BASIC_MMIO_CORE
>         help
>           Say yes here to support basic memory-mapped GPIO controllers.
>  
> diff --git a/drivers/gpio/Makefile b/drivers/gpio/Makefile
> index becef59..aa9e97f 100644
> --- a/drivers/gpio/Makefile
> +++ b/drivers/gpio/Makefile
> @@ -10,6 +10,7 @@ obj-$(CONFIG_GPIOLIB)         += gpiolib.o
>  
>  obj-$(CONFIG_GPIO_ADP5520)     += adp5520-gpio.o
>  obj-$(CONFIG_GPIO_ADP5588)     += adp5588-gpio.o
> +obj-$(CONFIG_GPIO_BASIC_MMIO_CORE)     += basic_mmio_gpio.o
>  obj-$(CONFIG_GPIO_BASIC_MMIO)  += basic_mmio_gpio.o

I think the line above should be removed.  GPIO_BASIC_MMIO selects
GPIO_BASIC_MMIO_CORE so the line you added previous to it will cause
basic_mmio_gpio to be compiled.

GPIO_BASIC_MMIO is really just used in the driver to enable the code
at the end which creates the generic gbpio_driver.

>  obj-$(CONFIG_GPIO_LANGWELL)    += langwell_gpio.o
>  obj-$(CONFIG_GPIO_MAX730X)     += max730x.o

Regards,
Hartley

WARNING: multiple messages have this Message-ID (diff)
From: hartleys@visionengravers.com (H Hartley Sweeten)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio
Date: Fri, 20 May 2011 17:07:12 -0500	[thread overview]
Message-ID: <0D753D10438DA54287A00B027084269764D30C10DC@AUSP01VMBX24.collaborationhost.net> (raw)
In-Reply-To: <20110520015022.GA3095@pulham.picochip.com>

On Thursday, May 19, 2011 6:50 PM, Jamie Iles wrote:
>> Jamie Iles (cc'ed) posted some patches that extended the basic_mmio_gpio
>> driver so that it could be used as a library by other gpio drivers.
>> 
>> Jamie, could you re-post that series to the linux-arm-kernel list for
>> review?
>
> Grant has applied these patches but I've put them in a public branch if 
> that's OK rather than reposting:
>
>	git://github.com/jamieiles/linux-2.6-ji.git gpio

Thanks for the link.

I just noticed something in commit fdcd80cb991dac7a70433be1e336726415762b6a
"basic_mmio_gpio: split into a gpio library and platform device".

> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index d3b2953..2186d22 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -70,8 +70,14 @@ config GPIO_MAX730X
>  
>  comment "Memory mapped GPIO expanders:"
>  
> +config GPIO_BASIC_MMIO_CORE
> +       tristate
> +       help
> +         Provides core functionality for basic memory-mapped GPIO controllers.
> +
>  config GPIO_BASIC_MMIO
>         tristate "Basic memory-mapped GPIO controllers support"
> +       select GPIO_BASIC_MMIO_CORE
>         help
>           Say yes here to support basic memory-mapped GPIO controllers.
>  
> diff --git a/drivers/gpio/Makefile b/drivers/gpio/Makefile
> index becef59..aa9e97f 100644
> --- a/drivers/gpio/Makefile
> +++ b/drivers/gpio/Makefile
> @@ -10,6 +10,7 @@ obj-$(CONFIG_GPIOLIB)         += gpiolib.o
>  
>  obj-$(CONFIG_GPIO_ADP5520)     += adp5520-gpio.o
>  obj-$(CONFIG_GPIO_ADP5588)     += adp5588-gpio.o
> +obj-$(CONFIG_GPIO_BASIC_MMIO_CORE)     += basic_mmio_gpio.o
>  obj-$(CONFIG_GPIO_BASIC_MMIO)  += basic_mmio_gpio.o

I think the line above should be removed.  GPIO_BASIC_MMIO selects
GPIO_BASIC_MMIO_CORE so the line you added previous to it will cause
basic_mmio_gpio to be compiled.

GPIO_BASIC_MMIO is really just used in the driver to enable the code
at the end which creates the generic gbpio_driver.

>  obj-$(CONFIG_GPIO_LANGWELL)    += langwell_gpio.o
>  obj-$(CONFIG_GPIO_MAX730X)     += max730x.o

Regards,
Hartley

  reply	other threads:[~2011-05-20 22:07 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 13:13 [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio Linus Walleij
2011-04-27 13:13 ` Linus Walleij
2011-04-27 18:23 ` H Hartley Sweeten
2011-04-27 18:23   ` H Hartley Sweeten
2011-04-28  7:07   ` Linus Walleij
2011-04-28  7:07     ` Linus Walleij
2011-04-28  7:10     ` Linus Walleij
2011-04-28  7:10       ` Linus Walleij
2011-04-28 17:41     ` H Hartley Sweeten
2011-04-28 17:41       ` H Hartley Sweeten
2011-05-13 14:51       ` Linus Walleij
2011-05-13 14:51         ` Linus Walleij
2011-05-19  8:56 ` Shawn Guo
2011-05-19  8:56   ` Shawn Guo
2011-05-19 12:21   ` Linus Walleij
2011-05-19 12:21     ` Linus Walleij
2011-05-19 13:56     ` Shawn Guo
2011-05-19 13:56       ` Shawn Guo
2011-05-19 19:11       ` Sascha Hauer
2011-05-19 19:11         ` Sascha Hauer
2011-05-19 19:30         ` Nicolas Pitre
2011-05-19 19:30           ` Nicolas Pitre
2011-05-20  3:18           ` Shawn Guo
2011-05-20  3:18             ` Shawn Guo
2011-05-20  3:43             ` Kyungmin Park
2011-05-20  3:43               ` Kyungmin Park
2011-05-20  3:54               ` Nicolas Pitre
2011-05-20  3:54                 ` Nicolas Pitre
2011-05-19 21:18         ` H Hartley Sweeten
2011-05-19 21:18           ` H Hartley Sweeten
2011-05-20  1:50           ` Jamie Iles
2011-05-20  1:50             ` Jamie Iles
2011-05-20 22:07             ` H Hartley Sweeten [this message]
2011-05-20 22:07               ` H Hartley Sweeten
2011-05-21 13:03               ` Jamie Iles
2011-05-21 13:03                 ` Jamie Iles
2011-05-20  7:01         ` Grant Likely
2011-05-20  7:01           ` Grant Likely
2011-05-20  7:47           ` Linus Walleij
2011-05-20  7:47             ` Linus Walleij
2011-05-19 11:11 ` Barry Song
2011-05-19 11:38   ` Barry Song
2011-05-19 11:38     ` Barry Song
2011-05-19 12:25     ` Linus Walleij
2011-05-19 12:25       ` Linus Walleij
2011-05-19 12:35       ` Barry Song
2011-05-19 12:35         ` Barry Song
2011-05-19 13:17         ` Linus Walleij
2011-05-19 13:17           ` Linus Walleij
2011-05-19 14:05           ` Barry Song
2011-05-19 14:05             ` Barry Song
2011-05-20  6:58             ` Grant Likely
2011-05-20  6:58               ` Grant Likely
2011-05-20  6:52       ` Grant Likely
2011-05-20  6:52         ` Grant Likely
2011-05-20  7:46         ` Linus Walleij
2011-05-20  7:46           ` Linus Walleij

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=0D753D10438DA54287A00B027084269764D30C10DC@AUSP01VMBX24.collaborationhost.net \
    --to=hartleys@visionengravers.com \
    --cc=grant.likely@secretlab.ca \
    --cc=jamie@jamieiles.com \
    --cc=jonas.aberg@stericsson.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawn.guo@freescale.com \
    /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.