linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grazvydas Ignotas <notasas@gmail.com>
To: Arun Murthy <arunrmurthy.83@gmail.com>
Cc: Anton Vorontsov <cbouatmailru@gmail.com>,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
	Felipe Balbi <balbi@ti.com>, Madhusudhan <madhu.cr@ti.com>
Subject: Re: [PATCH v3] power_supply: Add driver for TWL4030/TPS65950 BCI charger
Date: Mon, 27 Sep 2010 16:08:41 +0300	[thread overview]
Message-ID: <AANLkTi=xS_=QytU0Yrh5EEiiL6GyekcO+DezjT-Zpj-7@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik0LOQN8kOPjv_VohhO5To6pZDS=M0mw=q0whPp@mail.gmail.com>

On Mon, Sep 27, 2010 at 3:35 PM, Arun Murthy <arunrmurthy.83@gmail.com> wrote:
> On Mon, Sep 27, 2010 at 4:24 PM, Grazvydas Ignotas <notasas@gmail.com> wrote:
>> On Mon, Sep 27, 2010 at 10:21 AM, Arun Murthy <arunrmurthy.83@gmail.com> wrote:
>> The problem is that BCI is only active while charging, when it is not
>> charging most (all?) monitoring registers freeze and no monitoring
>> happens (BCI registers read frozen values from last charge). So I
>> don't register battery as it has no useful data to report. I heard it
>> is possible to use MADC to perform monitoring while not charging, so
>> battery can be added when MADC driver is merged and corresponding code
>> is written for this driver.
>>
> How do I check the battery voltage?
> I need to check the battery voltage/current/temp and, if I am not
> wrong these are obtained from MADC.
> MADC driver has to be added first and then the battery.
> With being able to read the basic parameter battery voltage, this
> driver becomes incomplete.

Incomplete driver is better than no driver, don't you think? There are
some boards like pandora or oswald that have additional battery
monitoring chips (as twl monitoring is pretty crude anyway), those
boards would have fully functional charging now. Currently mainline
kernel is not very useful with them simply because the battery runs
flat.

> How do I get notified if battery voltage is low and needs charging
> from user space?

Either additional monitoring chip notifies you (if you are lucky and
have one), or wait for update of this driver :) There are efforts to
merge MADC driver [1], but it may take some time.

[1] http://marc.info/?t=128461535700002&r=1&w=2

  reply	other threads:[~2010-09-27 13:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-26 19:35 [PATCH v3] power_supply: Add driver for TWL4030/TPS65950 BCI charger Grazvydas Ignotas
2010-09-27  6:18 ` Felipe Balbi
2010-09-27  9:57   ` Grazvydas Ignotas
     [not found] ` <AANLkTinkxokX9BGtxysYOr19xbZR4S8oPRYUAyneutzc@mail.gmail.com>
2010-09-27  8:16   ` Felipe Balbi
2010-09-27 10:54   ` Grazvydas Ignotas
2010-09-27 12:35     ` Arun Murthy
2010-09-27 13:08       ` Grazvydas Ignotas [this message]
2010-09-27 16:13         ` Arun Murthy
2010-09-27 19:42           ` Grazvydas Ignotas
2010-09-27 10:30 ` Arun Murthy

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='AANLkTi=xS_=QytU0Yrh5EEiiL6GyekcO+DezjT-Zpj-7@mail.gmail.com' \
    --to=notasas@gmail.com \
    --cc=arunrmurthy.83@gmail.com \
    --cc=balbi@ti.com \
    --cc=cbouatmailru@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.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;
as well as URLs for NNTP newsgroup(s).