mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: David Rees <drees76@gmail.com>
Cc: Mohamed Ikbel Boulabiar <boulabiar@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Low-Level and Long-Term Battery Control
Date: Fri, 16 Apr 2010 06:15:09 +0200	[thread overview]
Message-ID: <20100416041509.GB1552@elf.ucw.cz> (raw)
In-Reply-To: <q2p72dbd3151004151642p9c0b8a14yc9de251b134aec08@mail.gmail.com>

On Thu 2010-04-15 16:42:56, David Rees wrote:
> On Thu, Apr 15, 2010 at 11:02 AM, Pavel Machek <pavel@ucw.cz> wrote:
> >> For Laptops, it is better to extract the battery from the Laptop when
> >> the computer will be on power for a long period.
> >> I ask if the kernel can do such control without the user intention and
> >> in an automatic way.
> >>
> >> Some BIOS provide to the user to select whether to block the battery
> >> charging to 50% to make it stand for more time.
> >
> > Where have you seen that?
> 
> I do recall that some older ThinkPads had a utility that would let you
> determine what "empty" and "full" was by setting artificial limits.
> It's well known that by keeping batteries from being fully
> charged/discharged can significantly extend it's useful life although
> you will suffer from shorter run-times.  How sensitive a battery is to
> this depends on it's exact chemistry, but all are affected by this to
> some degree.
> 
> For example, by keeping your battery from charging above 85% and below
> 15% can increase the number of charge/discharge cycles a large
> amount

>From charging below 15%?

> often on the order of 5-10 times more charge/discharge cycles - much
> more than the 30% reduction in total capacity.  Limiting to 25-75%
> will help even more.

I believe I've seen "don't charge above 85%", but "don't charge above
50%" is quite excessive...

Anyway, this is done by smartbattery, not by OS.
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2010-04-16  4:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 13:28 Mohamed Ikbel Boulabiar
2010-04-15 18:02 ` Pavel Machek
2010-04-15 23:42   ` David Rees
2010-04-16  4:15     ` Pavel Machek [this message]
2010-04-22  9:25       ` Mohamed Ikbel Boulabiar
2010-04-13 12:35 Mohamed Ikbel Boulabiar
2010-04-13 13:24 ` Tony Vroon
2010-04-19  4:31 ` Andy Lutomirski
2010-04-20 13:37   ` Pavel Machek

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=20100416041509.GB1552@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=boulabiar@gmail.com \
    --cc=drees76@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®