linux-kernel - Re: [PATCH] power_supply: Add charge_current and charge

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 19 Jun 2012 16:54:48 -0700
From:	Anton Vorontsov <cbouatmailru@...il.com>
To:	Ramakrishna Pallala <ramakrishna.pallala@...el.com>
Cc:	linux-kernel@...r.kernel.org,
	Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: Re: [PATCH] power_supply: Add charge_current and charge_voltage
 properties and use it in smb347

On Sun, May 06, 2012 at 06:16:44PM +0530, Ramakrishna Pallala wrote:
> 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".
> 
> This patch also makes use of these two properties in smb347 charger driver.
> 
> Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@...el.com>
> ---

Applied, thank you. (FYI: I split the patch into two: power_supply
part and smb347 part.)

-- 
Anton Vorontsov
Email: cbouatmailru@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/