Re: [uClinux-dev] [RFC/PATCH] m68knommu: refactor Coldfire GPIO not to require GPIOLIB, eliminate mcf_gpio_chips.

2012-06-19 Thread Mark Brown
On Thu, Jun 07, 2012 at 12:01:20PM +1000, Greg Ungerer wrote: > On 07/06/12 00:20, Steven King wrote: > >>Ok, done. I had a merge conflict on Kconfig.cpu, but I thinked I > >>fixed it up right. > >Yeah, I ran into that conflict too when I rebased my trees; curious, I > >looked > >at the log and

Re: [uClinux-dev] [RFC/PATCH] m68knommu: refactor Coldfire GPIO not to require GPIOLIB, eliminate mcf_gpio_chips.

2012-06-06 Thread Greg Ungerer
On 07/06/12 00:20, Steven King wrote: On Wednesday 06 June 2012 12:07:33 am Greg Ungerer wrote: Hi Steven, On 06/06/12 00:23, Steven King wrote: On Monday 04 June 2012 11:27:04 pm Greg Ungerer wrote: On 22/05/12 06:10, Steven King wrote: If we're not connecting external GPIO extenders via i2

Re: [uClinux-dev] [RFC/PATCH] m68knommu: refactor Coldfire GPIO not to require GPIOLIB, eliminate mcf_gpio_chips.

2012-06-06 Thread Steven King
On Wednesday 06 June 2012 12:07:33 am Greg Ungerer wrote: > Hi Steven, > > On 06/06/12 00:23, Steven King wrote: > > On Monday 04 June 2012 11:27:04 pm Greg Ungerer wrote: > >> On 22/05/12 06:10, Steven King wrote: > >>> If we're not connecting external GPIO extenders via i2c or spi or > >>> whatev

Re: [uClinux-dev] [RFC/PATCH] m68knommu: refactor Coldfire GPIO not to require GPIOLIB, eliminate mcf_gpio_chips.

2012-06-06 Thread Greg Ungerer
Hi Steven, On 06/06/12 00:23, Steven King wrote: On Monday 04 June 2012 11:27:04 pm Greg Ungerer wrote: On 22/05/12 06:10, Steven King wrote: If we're not connecting external GPIO extenders via i2c or spi or whatever, we probably don't need GPIOLIB. If we provide an alternate implementation o

Re: [uClinux-dev] [RFC/PATCH] m68knommu: refactor Coldfire GPIO not to require GPIOLIB, eliminate mcf_gpio_chips.

2012-06-05 Thread Steven King
On Monday 04 June 2012 11:27:04 pm Greg Ungerer wrote: > Hi Steven, > > On 22/05/12 06:10, Steven King wrote: > > If we're not connecting external GPIO extenders via i2c or spi or > > whatever, we probably don't need GPIOLIB. If we provide an alternate > > implementation of the GPIOLIB functions t

Re: [uClinux-dev] [RFC/PATCH] m68knommu: refactor Coldfire GPIO not to require GPIOLIB, eliminate mcf_gpio_chips.

2012-06-04 Thread Greg Ungerer
Hi Steven, On 22/05/12 06:10, Steven King wrote: If we're not connecting external GPIO extenders via i2c or spi or whatever, we probably don't need GPIOLIB. If we provide an alternate implementation of the GPIOLIB functions to use when only on-chip GPIO is needed, we can change ARCH_REQUIRE_GPI

[uClinux-dev] [RFC/PATCH] m68knommu: refactor Coldfire GPIO not to require GPIOLIB, eliminate mcf_gpio_chips.

2012-05-21 Thread Steven King
If we're not connecting external GPIO extenders via i2c or spi or whatever, we probably don't need GPIOLIB. If we provide an alternate implementation of the GPIOLIB functions to use when only on-chip GPIO is needed, we can change ARCH_REQUIRE_GPIOLIB to ARCH_WANTS_OPTIONAL_GPIOLIB so that GPIOL