Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 29 11月, 2012 2 次提交
  3. 01 8月, 2012 1 次提交
  5. 16 7月, 2012 2 次提交
  7. 04 1月, 2012 1 次提交
  9. 25 11月, 2011 2 次提交
    • A
      olpc_battery: Remove unneeded 'olpc_battery_trigger_uevent' · 7ab2f020
      由 Anton Vorontsov 提交于 
      It is no longer used, so we can safely remove it.
Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
      7ab2f020
    • A
      olpc_battery: Fix section mismatch noise · 5519d00e
      由 Anton Vorontsov 提交于 
      This patch fixes the following noise (by renaming _drv to _driver):

WARNING: drivers/power/olpc_battery.o(.data+0x100): Section mismatch in reference from the variable olpc_battery_drv to the function .devinit.text:olpc_battery_probe()
The variable olpc_battery_drv references
the function __devinit olpc_battery_probe()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*driver, *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console

WARNING: drivers/power/olpc_battery.o(.data+0x104): Section mismatch in reference from the variable olpc_battery_drv to the function .devexit.text:olpc_battery_remove()
The variable olpc_battery_drv references
the function __devexit olpc_battery_remove()
If the reference is valid then annotate the
variable with __exit* (see linux/init.h) or name the variable:
*driver, *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console

WARNING: drivers/power/olpc_battery.o(.data+0x128): Section mismatch in reference from the variable olpc_battery_drv to the variable .devinit.rodata:olpc_battery_ids
The variable olpc_battery_drv references
the variable __devinitconst olpc_battery_ids
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*driver, *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
      5519d00e
  11. 20 8月, 2011 2 次提交
  13. 13 1月, 2011 5 次提交
  15. 28 9月, 2010 1 次提交
  17. 11 8月, 2010 1 次提交
  19. 10 8月, 2010 1 次提交
  21. 22 5月, 2010 1 次提交
  23. 02 7月, 2009 1 次提交
  25. 01 7月, 2009 4 次提交
  27. 17 10月, 2008 1 次提交
  29. 19 5月, 2008 1 次提交
  31. 13 5月, 2008 1 次提交
  33. 04 5月, 2008 4 次提交
  35. 29 4月, 2008 1 次提交
  37. 02 2月, 2008 1 次提交
    • A
      power: remove POWER_SUPPLY_PROP_CAPACITY_LEVEL · 8efe4440
      由 Andres Salomon 提交于 
      The CAPACITY_LEVEL stuff defines various levels of charge; however, what
is the difference between them?  What differentiates between HIGH and NORMAL,
LOW and CRITICAL, etc?

As it appears that these are fairly arbitrary, we end up making such policy
decisions in the kernel (or in hardware).  This is the sort of decision that
should be made in userspace, not in the kernel.

If the hardware does not support _CAPACITY and it cannot be easily calculated,
then perhaps the driver should register a custom CAPACITY_LEVEL attribute;
however, userspace should not become accustomed to looking for such a thing,
and we should certainly not encourage drivers to provide CAPACITY_LEVEL
stubs.

The following removes support for POWER_SUPPLY_PROP_CAPACITY_LEVEL.  The
OLPC battery driver is the only driver making use of this, so it's
removed from there as well.
Signed-off-by: NAndres Salomon <dilinger@debian.org>
Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      8efe4440
  39. 16 7月, 2007 1 次提交
  41. 10 7月, 2007 1 次提交