- 01 8月, 2012 1 次提交
-
-
由 Andres Salomon 提交于
Switch over to using olpc-ec.h in multiple steps, so as not to break builds. This covers every driver that calls olpc_ec_cmd(). Signed-off-by: NAndres Salomon <dilinger@queued.net> Acked-by: NPaul Fox <pgf@laptop.org> Reviewed-by: NThomas Gleixner <tglx@linutronix.de>
-
- 19 7月, 2012 1 次提交
-
-
由 Theodore Ts'o 提交于
With the changes in the random tree, IRQF_SAMPLE_RANDOM is now a no-op; interrupt randomness is now collected unconditionally in a very low-overhead fashion; see commit 775f4b29. The IRQF_SAMPLE_RANDOM flag was scheduled to be removed in 2009 on the feature-removal-schedule, so this patch is preparation for the final removal of this flag. Signed-off-by: N"Theodore Ts'o" <tytso@mit.edu> Acked-by: NAnton Vorontsov <cbou@mail.ru> Cc: David Woodhouse <dwmw2@infradead.org>
-
- 16 7月, 2012 3 次提交
-
-
由 Richard A. Smith 提交于
Reduce the mAh value for the BYD LiFe battery from 3100mAh to 2800mAh to better reflect the average usable capacity as measured by olpc-pwr-log. Signed-off-by: NRichard A. Smith <richard@laptop.org> Signed-off-by: NDaniel Drake <dsd@laptop.org> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Richard A. Smith 提交于
upowerd wants to compute the energy in the battery by looking at this property. If it's not present then it falls back on using the reported voltage of the battery at time upowerd loads. That's close but also means that every time you boot you get a slightly different energy capacity. Adding the VOLTAGE_MAX_DESIGN property allows upowerd to compute the same energy every time. Signed-off-by: NRichard A. Smith <richard@laptop.org> Signed-off-by: NDaniel Drake <dsd@laptop.org> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Chanwoo Choi 提交于
This patch select CONFIG_EXTCON to resolve below build break of charger-manager because charger-manager use API of EXTCON subsystem. drivers/built-in.o: In function `charger_manager_probe': charger-manager.c:(.text+0x11d61a): undefined reference to `extcon_register_interest' charger-manager.c:(.text+0x11d7b6): undefined reference to `extcon_unregister_interest' drivers/built-in.o: In function `charger_manager_remove': charger-manager.c:(.devexit.text+0x8f3): undefined reference to `extcon_unregister_interest' Signed-off-by: NChanwoo Choi <cw00.choi@samsung.com> Signed-off-by: NMyungjoo Ham <myungjoo.ham@samsung.com> Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
- 14 7月, 2012 5 次提交
-
-
由 Kim, Milo 提交于
The lp8727 header can be used only in the platform side, so it can be moved to the platform_data directory. Signed-off-by: NMilo(Woogyom) Kim <milo.kim@ti.com> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Ramakrishna Pallala 提交于
Minimum and maximum alerts on power supply properties will help or allow the user space to "proactively" create policies like connect/disconnect charger or stop/start the user apps based on capacity or temperature parameters. These parameters can be used to avoid unnecessary polling from user space and even from kernel space if the underlying HW can support INT triggers (ex: max17042/47). This patch adds the following power supply alert type properties: CAPACITY_ALERT_MIN CAPACITY_ALERT_MAX TEMP_ALERT_MIN TEMP_ALERT_MAX TEMP_AMBIENT_ALERT_MIN TEMP_AMBIENT_ALERT_MAX Signed-off-by: NRamakrishna Pallala <ramakrishna.pallala@intel.com> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Saranya Gopal 提交于
This patch adds support for BQ27425 (TI) chip. This chip is same as BQ27500 with few registers removed and register address map changed. The data sheet for this chip is publicly available at http://www.ti.com/product/bq27425-g1Signed-off-by: NSaranya Gopal <saranya.gopal@intel.com> Reviewed-by: NLars-Peter Clausen <lars@metafoo.de> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Chanwoo Choi 提交于
This patch support the protection of host device from over current. The Charger-manager set proper current limit of charger(regulator) for charging according to type of charger cable when external connector is attached. Signed-off-by: NChanwoo Choi <cw00.choi@samsung.com> Signed-off-by: NMyungjoo Ham <myungjoo.ham@samsung.com> Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Chanwoo Choi 提交于
This patch support that charger-manager use EXTCON(External Connector) Subsystem to detect the state of charger cables for enabling or disabling charger(regulator) and select the charger cable for charging among a number of external cable according to policy of H/W board. Signed-off-by: NChanwoo Choi <cw00.choi@samsung.com> Signed-off-by: NMyungjoo Ham <myungjoo.ham@samsung.com> Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
- 02 7月, 2012 1 次提交
-
-
由 Kishon Vijay Abraham I 提交于
usb_get_phy will return -ENODEV if it's not able to find the phy. Hence fixed all the callers of usb_get_phy to check for this error condition instead of relying on a non-zero value as success condition. Signed-off-by: NKishon Vijay Abraham I <kishon@ti.com> Signed-off-by: NFelipe Balbi <balbi@ti.com>
-
- 29 6月, 2012 1 次提交
-
-
由 Jean Pihet 提交于
Disable the module option for POWER_AVS since this is currently not supported. This patch fixes these error in the case POWER_AVS is set to 'm': arch/arm/mach-omap2/built-in.o: In function `sr_class3_configure': arch/arm/mach-omap2/smartreflex-class3.c:43: undefined reference to `sr_configure_errgen' arch/arm/mach-omap2/built-in.o: In function `sr_class3_disable': arch/arm/mach-omap2/smartreflex-class3.c:33: undefined reference to `sr_disable_errgen' arch/arm/mach-omap2/smartreflex-class3.c:35: undefined reference to `sr_disable' arch/arm/mach-omap2/built-in.o: In function `sr_class3_enable': arch/arm/mach-omap2/smartreflex-class3.c:28: undefined reference to `sr_enable' arch/arm/mach-omap2/built-in.o: In function `sr_class3_init': arch/arm/mach-omap2/smartreflex-class3.c:59: undefined reference to `sr_register_class' Reported-by: NTony Lindgren <tony@atomide.com> Signed-off-by: NJean Pihet <j-pihet@ti.com> Signed-off-by: NKevin Hilman <khilman@ti.com> [tony@atomide.com: updated to use relative paths for the build error] Signed-off-by: NTony Lindgren <tony@atomide.com>
-
- 28 6月, 2012 1 次提交
-
-
由 Paul Bolle 提交于
Signed-off-by: NPaul Bolle <pebolle@tiscali.nl> Signed-off-by: NJiri Kosina <jkosina@suse.cz>
-
- 25 6月, 2012 2 次提交
-
-
由 Kishon Vijay Abraham I 提交于
Add a linked list for keeping multiple PHY instances with different types so that we can have separate USB2 and USB3 PHYs on one single board. _get_phy_ has been changed so that the controller gets the transceiver by type. _remove_phy_ has been added to let the phy be removed from the phy list. Signed-off-by: NKishon Vijay Abraham I <kishon@ti.com> Signed-off-by: NFelipe Balbi <balbi@ti.com>
-
由 Kishon Vijay Abraham I 提交于
_transceiver() in otg.c is replaced with _phy. usb_set_transceiver is replaced with usb_add_phy to make it similar to other usb standard function names like usb_add_hcd. Signed-off-by: NKishon Vijay Abraham I <kishon@ti.com> Signed-off-by: NFelipe Balbi <balbi@ti.com>
-
- 21 6月, 2012 2 次提交
-
-
由 Dmitry Eremin-Solenikov 提交于
Emulate battery temperature (fixed to 26) and battery voltage (variable) properties. Signed-off-by: NDmitry Eremin-Solenikov <dmitry_eremin@mentor.com> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
由 Dmitry Eremin-Solenikov 提交于
Usually a device has both AC plug and UDC plug usable for charging. Provide both AC sources. Signed-off-by: NDmitry Eremin-Solenikov <dmitry_eremin@mentor.com> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
- 20 6月, 2012 9 次提交
-
-
由 Pritesh Raithatha 提交于
Context of gpio_charger_get_property is sleepable so we should use gpio_set_value_cansleep instead of gpio_set_value. It will remove WARN_ON incase of using gpio from i2c-to-gpio expander like pca953x. Signed-off-by: NPritesh Raithatha <praithatha@nvidia.com> Acked-by: NLars-Peter Clausen <lars@metafoo.de> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
由 Syed Rafiuddin 提交于
Addition of power average and health properties. Signed-off-by: NSyed Rafiuddin <srafiuddin@nvidia.com> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
由 Nikolaus Voss 提交于
power_supply_changed() events are triggerd based on the return value of a get_property() call. However the property TECHNOLOGY is hard-coded to LION in this driver, thus always succeeds. So, with the battery removed, this triggers a false battery present uevent. This uevent triggers a new query via power_supply_uevent() which again starts to query all known properties and thus leads to an infinite loop of battery present/not-present uevents. This patch skips the battery presence detection for the hard-coded property TECHNOLOGY. Signed-off-by: NNikolaus Voss <n.voss@weinmann.de> Acked-by Rhyland Klein <rklein@nvidia.com> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
由 NeilBrown 提交于
The charger needs usb3v1 to be running, so add a new consumer to keep it running. This allows the charger to draw current even when the USB driver has powered down. Signed-off-by: NNeilBrown <neilb@suse.de> Acked-by: NTero Kristo <t-kristo@ti.com> Acked-by: NSamuel Ortiz <sameo@linux.intel.com> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
由 NeilBrown 提交于
This allows a voltage and current (bb_uvolts and bb_uamps) to be specified in the platform_data, and charging of the backup battery will be enabled with those specification. As it is not possible to monitor the backup battery at all there is no new device created to represent it. Signed-off-by: NNeilBrown <neilb@suse.de> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
由 NeilBrown 提交于
Signed-off-by: NNeilBrown <neilb@suse.de> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
由 Ramakrishna Pallala 提交于
This patch adds the support for CHARGE_COUNTER power supply attribute to max17042/47 driver. Note:QH(Charge Counter) register is not documented in max17042 the Spec. Signed-off-by: NRamakrishna Pallala <ramakrishna.pallala@intel.com> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
由 Ramakrishna Pallala 提交于
This patch makes use of the two new properties in smb347 charger driver. Signed-off-by: NRamakrishna Pallala <ramakrishna.pallala@intel.com> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
由 Ramakrishna Pallala 提交于
Constant Charge Current(CC) is charging parameter which limit the maximum current which can be pumped into the battery during charge cycle. Constant Charge Voltage(CV) is also charging parameter which limit the maximum voltage that battery can reach during charge cycle. It is very common practice that at low or high temperatures we do not charge the batteries upto it's fullest charge voltage to avoid battery and user safety issues. These sysfs properties will be useful for debug and to implement certain user space policies like "Charging limited due to OverTemp". Signed-off-by: NRamakrishna Pallala <ramakrishna.pallala@intel.com> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
- 18 6月, 2012 3 次提交
-
-
由 Jenny TC 提交于
Battery and charger contribute to Thermals in most of the embedded devices. So, it makes sense to identify them as Thermal zones in a particular platform. This patch registers a thermal zone if the power supply is reporting a temperature property. The thermal zone will be used by platform's thermal management solution. Signed-off-by: NJenny TC <jenny.tc@intel.com> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
由 Anton Vorontsov 提交于
This patch fixes the following sparse warning: CHECK drivers/power/ds2781_battery.c drivers/power/ds2781_battery.c:72:5: warning: symbol 'w1_ds2781_read' was not declared. Should it be static? Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
由 Mark Brown 提交于
Rather than silently ignoring errors from the regulator enable and disable add a WARN_ON() - it's probably pretty important if we're not getting power, though it should be vanishingly unlikely in production. Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by: NAnton Vorontsov <cbouatmailru@gmail.com>
-
- 14 6月, 2012 1 次提交
-
-
由 NeilBrown 提交于
The 'mutex' in struct w1_master is use for two very different purposes. Firstly it protects various data structures such as the list of all slaves. Secondly it protects the w1 buss against concurrent accesses. This can lead to deadlocks when the ->probe code called while adding a slave needs to talk on the bus, as is the case for power_supply devices. ds2780 and ds2781 drivers contain a work around to track which process hold the lock simply to avoid this deadlock. bq27000 doesn't have that work around and so deadlocks. There are other possible deadlocks involving sysfs. When removing a device the sysfs s_active lock is held, so the lock that protects the slave list must take precedence over s_active. However when access power_supply attributes via sysfs, the s_active lock must take precedence over the lock that protects accesses to the bus. So to avoid deadlocks between w1 slaves and sysfs, these must be two separate locks. Making them separate means that the work around in ds2780 and ds2781 can be removed. So this patch: - adds a new mutex: "bus_mutex" which serialises access to the bus. - takes in mutex in w1_search and ds1wm_search while they access the bus for searching. The mutex is dropped before calling the callback which adds the slave. - changes all slaves to use bus_mutex instead of mutex to protect access to the bus - removes w1_ds2790_io_nolock and w1_ds2781_io_nolock, and the related code from drivers/power/ds278[01]_battery.c which calls them. Signed-off-by: NNeilBrown <neilb@suse.de> Acked-by: NEvgeniy Polyakov <zbr@ioremap.net> Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
-
- 01 6月, 2012 1 次提交
-
-
由 Jean Pihet 提交于
After a clean-up of the interfaces the OMAP Smartreflex IP driver is now a generic driver. Move it to drivers/power/avs/. The build is controlled by the following Kconfig options: . CONFIG_POWER_AVS: general knob for Adaptive Voltage Scaling support, . CONFIG_POWER_AVS_OMAP: AVS(Adaptive Voltage Scaling) support on OMAP containing the version 1 or version 2 of the SmartReflex IP, . CONFIG_POWER_AVS_OMAP_CLASS3: Class 3 implementation of Smartreflex. Signed-off-by: NJean Pihet <j-pihet@ti.com> Signed-off-by: NJ Keerthy <j-keerthy@ti.com> Acked-by: NRafael J. Wysocki <rjw@sisk.pl> Reviewed-by: NKevin Hilman <khilman@ti.com> Signed-off-by: NKevin Hilman <khilman@ti.com>
-
- 20 5月, 2012 1 次提交
-
-
由 Mark Brown 提交于
The modern idiom is to use irq_domain to allocate interrupts. This is useful partly to allow further infrastructure to be based on the domains and partly because it makes it much easier to allocate virtual interrupts to devices as we don't need to allocate a contiguous range of interrupt numbers. Convert the wm831x driver over to this infrastructure, using a legacy IRQ mapping if an irq_base is specified in platform data and otherwise using a linear mapping, always registering the interrupts even if they won't ever be used. Only boards which need to use the GPIOs as interrupts should need to use an irq_base. This means that we can't use the MFD irq_base management since the unless we're using an explicit irq_base from platform data we can't rely on a linear mapping of interrupts. Instead we need to map things via the irq_domain - provide a conveniencem function wm831x_irq() to save a small amount of typing when doing so. Looking at this I couldn't clearly see anything the MFD core could do to make this nicer. Since we're not supporting device tree yet there's no meaningful advantage if we don't do this conversion in one, the fact that the interrupt resources are used for repeated IP blocks makes accessor functions for the irq_domain more trouble to do than they're worth. Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
-
- 19 5月, 2012 1 次提交
-
-
由 Mika Westerberg 提交于
Without the include we get build errors like: drivers/power/smb347-charger.c: In function 'smb347_probe': drivers/power/smb347-charger.c:1039:2: error: implicit declaration of function 'IS_ERR' [-Werror=implicit-function-declaration] drivers/power/smb347-charger.c:1040:3: error: implicit declaration of function 'PTR_ERR' [-Werror=implicit-function-declaration] Reported-by: NStephen Rothwell <sfr@canb.auug.org.au> Signed-off-by: NMika Westerberg <mika.westerberg@linux.intel.com> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
- 06 5月, 2012 7 次提交
-
-
由 Ramakrishna Pallala 提交于
CURRENT_NOW and VOLTAGE_NOW should be instantaneous readings from power supply(ex: battery). smb347 charger driver reports charge voltage for VOLTAGE_NOW and charge current for CURRENT_NOW attributes which are not instantaneous readings. This patch removes the battery VOLTAGE_NOW and CURRENT_NOW properties from the driver and also removes hw_to_current() which is not required anymore. Signed-off-by: NRamakrishna Pallala <ramakrishna.pallala@intel.com> Acked-by: NMika Westerberg <mika.westerberg@linux.intel.com> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Ramakrishna Pallala 提交于
max17047 is improved version of max17042 chip. It has few HW bug fixes with minor changes in register set. max17050 is same as max17047 chip except its silicon packging. So from driver's point of view there is no difference btw max1047 and max1050. This patch adds the support to dynamically detect the chip type and adds steps to initialize the max17047 chip. Signed-off-by: NRamakrishna Pallala <ramakrishna.pallala@intel.com> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Nikolaus Voss 提交于
Currently, the capacity exported by this driver refers to reg 0x0e, which is the absolute state of charge which according to SBS refers to the design capacity/ energy of the battery. It can be > 100 % and drops below 100 % for a fully charged battery with the battery aging. This is not what the user exspects of a remaining capacity indication between 0 and 100 % with 100 % referring to a fully charged battery. This is provided by SBS reg 0x0d, which is the relative state of charge referring to the full charge capacity. Signed-off-by: NNikolaus Voss <n.voss@weinmann.de> Acked-by: NRhyland Klein <rklein@nvidia.com> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Dan Carpenter 提交于
We can't use "isp" after freeing it. Signed-off-by: NDan Carpenter <dan.carpenter@oracle.com> Reviewed-by: NFelipe Contreras <felipe.contreras@gmail.com> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Axel Lin 提交于
Since we have defined DS2781_PARAM_EEPROM_SIZE and DS2781_USER_EEPROM_SIZE, use them to simplify the code. Signed-off-by: NAxel Lin <axel.lin@gmail.com> Acked-by: NEvgeniy Polyakov <zbr@ioremap.net> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Axel Lin 提交于
Signed-off-by: NAxel Lin <axel.lin@gmail.com> Acked-by: NEvgeniy Polyakov <zbr@ioremap.net> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-
由 Chanwoo Choi 提交于
By using cm_notify_event function, charger driver can report several charger events (e.g. battery full and external power in/out, etc) to Charger-Manager. Charger-Manager can properly and immediately control chargers by the reported event. Signed-off-by: NMyungJoo Ham <myungjoo.ham@samsung.com> Signed-off-by: NDonggeun Kim <dg77.kim@samsung.com> Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com> Signed-off-by: NAnton Vorontsov <anton.vorontsov@linaro.org>
-