public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Cc: linux-kernel@vger.kernel.org,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH] power_supply: Add charge_current and charge_voltage properties and use it in smb347
Date: Tue, 19 Jun 2012 16:54:48 -0700	[thread overview]
Message-ID: <20120619235445.GC12508@lizard> (raw)
In-Reply-To: <1336308404-25129-1-git-send-email-ramakrishna.pallala@intel.com>

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@intel.com>
> ---

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

-- 
Anton Vorontsov
Email: cbouatmailru@gmail.com

      parent reply	other threads:[~2012-06-19 23:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-06 12:46 [PATCH] power_supply: Add charge_current and charge_voltage properties and use it in smb347 Ramakrishna Pallala
2012-06-18  7:50 ` Pallala, Ramakrishna
2012-06-19 23:54 ` Anton Vorontsov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120619235445.GC12508@lizard \
    --to=cbouatmailru@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=ramakrishna.pallala@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox