stable-tracking not charging?

[Sean McNeil]

Andy Green wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Somebody in the thread at some point said:
> | Andy Green wrote:
> |> -----BEGIN PGP SIGNED MESSAGE-----
> |> Hash: SHA1
> |>
> |> Somebody in the thread at some point said:
> |> | When plugged into USB with kernel 2.6.26 I get battery charge 
> with no
> |> | problem. With stable-tracking, there is no charge indication and the
> |> | battery is definitely getting drained. I'm going to start 
> investigating
> |> | this right now.
> |>
> |> First please try andy-tracking instead, this has all of Balaji's 
> changes
> |> to regulator API and some bug fixes around this.  For GTA02 anyway
> |> otherwise than patches to adapt to Balaji's stuff andy-tracking is
> |> stable-tracking.
> |
> | OK, but aren't we going to make stable-tracking the new stable kernel?
>
> No confusingly enough it's andy-tracking that will branch for the new
> stable.
>
> I will write up a big boring email detailing about this later (again
> actually since I lost the original version when this laptop locked up)
> and various other git related things.
>
> | Should I look at the differences around this and make sure the ones 
> that
> | fix charging get into stable-tracking?
>
> It's fine if you just find that andy-tracking works, I will explain the
> logic in the BBE (Big Boring Email).  If it doesn't work then, oh well,
> we need to try to figure out what's busted.

Odd, but I can't compile andy-tracking. I see several duplicates from

drivers/i2c/chips/pcf50633.c and
drivers/mfd/pcf50633-gpio.c

there doesn't seem to be a way to deselect it in mfd with xconfig.

I end up getting

drivers/i2c/built-in.o: In function `pcf50633_reg_clear_bits':
pcf50633.c:(.text+0x7378): multiple definition of `pcf50633_reg_clear_bits'
drivers/mfd/built-in.o:pcf50633-gpio.c:(.text+0x3a20): first defined here
drivers/i2c/built-in.o: In function `pcf50633_adc_async_read':
pcf50633.c:(.text+0x7808): multiple definition of `pcf50633_adc_async_read'
drivers/mfd/built-in.o:pcf50633-gpio.c:(.text+0x46e4): first defined here
drivers/i2c/built-in.o: In function `pcf50633_adc_sync_read':
pcf50633.c:(.text+0x793c): multiple definition of `pcf50633_adc_sync_read'
drivers/mfd/built-in.o:pcf50633-gpio.c:(.text+0x4744): first defined here
drivers/i2c/built-in.o: In function `pcf50633_reg_read':
pcf50633.c:(.text+0x7488): multiple definition of `pcf50633_reg_read'
drivers/mfd/built-in.o:pcf50633-gpio.c:(.text+0x3b28): first defined here
drivers/i2c/built-in.o: In function `pcf50633_reg_set_bit_mask':
pcf50633.c:(.text+0x73d0): multiple definition of 
`pcf50633_reg_set_bit_mask'
drivers/mfd/built-in.o:pcf50633-gpio.c:(.text+0x3a78): first defined here
drivers/i2c/built-in.o: In function `pcf50633_reg_write':
pcf50633.c:(.text+0x72d8): multiple definition of `pcf50633_reg_write'
drivers/mfd/built-in.o:pcf50633-gpio.c:(.text+0x3ae0): first defined here
drivers/i2c/built-in.o: In function `pcf50633_gpio_get':
pcf50633.c:(.text+0x7714): multiple definition of `pcf50633_gpio_get'
drivers/mfd/built-in.o:pcf50633-gpio.c:(.text+0x4890): first defined here
drivers/i2c/built-in.o: In function `pcf50633_gpio_set':
pcf50633.c:(.text+0x7438): multiple definition of `pcf50633_gpio_set'
drivers/mfd/built-in.o:pcf50633-gpio.c:(.text+0x484c): first defined here