Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 160
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 06 5月, 2012 1 次提交
  3. 05 5月, 2012 2 次提交
    • M
      smb347-charger: Convert to regmap API · 34298d40
      由 Mika Westerberg 提交于 
      The smb347-charger driver does a lot of read-modify-write to the device
registers. Instead of open-coding everything we can take advantage of
regmap API which provides nice functions to do this kind of things.

In addition there is no need for custom debugfs file for dumping
registers as this is already provided by the regmap API.
Signed-off-by: NMika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
      34298d40
    • A
      power_supply: Make the core a boolean instead of a tristate · 0d4ed4e2
      由 Anton Vorontsov 提交于 
      On Mon, Apr 02, 2012 at 01:53:23PM +1000, Benjamin Herrenschmidt wrote:
> > drivers/built-in.o: In function `.nouveau_pm_trigger':
> > (.text+0xa56e8): undefined reference to `.power_supply_is_system_supplied'
> >
> > nouveau probably needs to depends on CONFIG_POWER_SUPPLY to force a module
> > build with the latter is =m
>
> Ok, not that trivial...
>
> The problem is more like POWER_SUPPLY should be a bool, not a tristate.
>
> If you think about it: you don't want things like nouveau to depend on a
> random subsystem like that, people will never get it. In fact,
> POWER_SUPPLY provides empty inline stubs when not enabled, so that's
> really designed to not have depends...
>
> However that -cannot- work if POWER_SUPPLY is modular and the drivers
> who use it are not.
>
> The only fixes here that make sense I can think of
> that don't also involve Kconfig horrors are:
>
>  - Ugly: in power_supply.h, use the extern variant if
>
>       defined(CONFIG_POWER_SUPPLY) ||
>        (defined(CONFIG_POWER_SUPPLY_MODULE) && defined(MODULE))
>
> IE. use the stub if power supply is a module and what is being built is
> built-in. Of course that's not only ugly, it somewhat sucks from a user
> perspective as the subsystem now exists but can't be used by some
> drivers...
>
>  - Better: Just make the bloody thing a bool :-) The power supply
> framework itself is small enough, just make it a boolean option and
> avoid the problem entirely. The actual power supply sub drivers can
> remain modular of course.
Suggested-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
      0d4ed4e2
  5. 27 3月, 2012 3 次提交
  7. 09 3月, 2012 1 次提交
  9. 10 1月, 2012 1 次提交
    • A
      power_supply: Mark da9052 driver as broken · 6cfc2a23
      由 Anton Vorontsov 提交于 
      There are some problems with MFD part of this driver, so the
driver fails to build:

drivers/power/da9052-battery.c: In function 'da9052_bat_read_volt':
drivers/power/da9052-battery.c:293:2: error: implicit declaration of function 'da9052_adc_manual_read' [-Werror=implicit-function-declaration]
drivers/power/da9052-battery.c: In function 'da9052_bat_check_presence':
drivers/power/da9052-battery.c:306:2: error: implicit declaration of function 'da9052_adc_read_temp' [-Werror=implicit-function-declaration]
drivers/power/da9052-battery.c: In function 'da9052_determine_vc_tbl_index':
drivers/power/da9052-battery.c:348:1: warning: control reaches end of non-void function [-Wreturn-type]
cc1: some warnings being treated as errors

The fix for MFD part will probably go post -rc1 (or in the next merge
window), so let's disable the driver for now.
Reported-by: NStephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
      6cfc2a23
  11. 06 1月, 2012 2 次提交
  13. 04 1月, 2012 2 次提交
  15. 02 11月, 2011 1 次提交
  17. 08 7月, 2011 2 次提交
  19. 27 5月, 2011 1 次提交
  21. 22 4月, 2011 1 次提交
  23. 20 4月, 2011 1 次提交
  25. 22 2月, 2011 1 次提交
    • L
      bq27x00: Add bq27000 support · 7fb7ba58
      由 Lars-Peter Clausen 提交于 
      This patch adds support for the bq27000 battery to the bq27x00 driver.
The bq27000 is similar to the bq27200 except that it uses the HDQ bus
instead of I2C to communicate with the host system.

The driver is implemented as a platform driver. The driver expects to be
provided with a read callback function through its platform data. The read
function is assumed to do the lowlevel HDQ handling and read out the value
of a certain register.
Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
Tested-by: NGrazvydas Ignotas <notasas@gmail.com>
      7fb7ba58
  27. 14 1月, 2011 1 次提交
  29. 18 11月, 2010 1 次提交
  31. 29 10月, 2010 1 次提交
  33. 28 10月, 2010 1 次提交
    • A
      power_supply: Mark twl4030_charger as broken · 23886839
      由 Anton Vorontsov 提交于 
      The driver is not buildable without MFD changes. For now, let's
disable the driver as it breaks build for major platforms (i.e. x86).

  CC [M]  drivers/power/twl4030_charger.o
drivers/power/twl4030_charger.c: In function 'twl4030_clear_set_boot_bci':
drivers/power/twl4030_charger.c:105: error: 'TWL4030_PM_MASTER_BOOT_BCI' undeclared (first use in this function)
drivers/power/twl4030_charger.c:105: error: (Each undeclared identifier is reported only once
drivers/power/twl4030_charger.c:105: error: for each function it appears in.)
drivers/power/twl4030_charger.c: In function 'twl4030_bci_have_vbus':
drivers/power/twl4030_charger.c:137: error: 'TWL4030_PM_MASTER_STS_HW_CONDITIONS' undeclared (first use in this function)
drivers/power/twl4030_charger.c: In function 'twl4030_bci_probe':
drivers/power/twl4030_charger.c:477: warning: overflow in implicit constant conversion
drivers/power/twl4030_charger.c:485: warning: overflow in implicit constant conversion
make[2]: *** [drivers/power/twl4030_charger.o] Error 1

We can re-enable it if MFD tree will finally merge into 2.6.37.
Reported-by: NIngo Molnar <mingo@elte.hu>
Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
      23886839
  35. 30 9月, 2010 1 次提交
  37. 23 9月, 2010 1 次提交
  39. 06 9月, 2010 1 次提交
  41. 19 8月, 2010 1 次提交
  43. 05 8月, 2010 1 次提交
  45. 23 7月, 2010 1 次提交
  47. 18 6月, 2010 1 次提交
  49. 18 5月, 2010 1 次提交
  51. 27 4月, 2010 1 次提交
  53. 07 4月, 2010 1 次提交
  55. 08 3月, 2010 1 次提交
  57. 17 2月, 2010 1 次提交
  59. 28 11月, 2009 1 次提交
  61. 16 11月, 2009 1 次提交
  63. 05 9月, 2009 1 次提交
  65. 01 7月, 2009 1 次提交
  67. 09 6月, 2009 1 次提交