mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Anton Vorontsov <cbouatmailru@gmail.com>
Cc: "Balbi, Felipe" <balbi@ti.com>,
	Grazvydas Ignotas <notasas@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>,
	Arun Murthy <arunrmurthy.83@gmail.com>
Subject: Re: [PATCH v4] power_supply: Add driver for TWL4030/TPS65950 BCI charger
Date: Tue, 28 Sep 2010 16:33:45 +0300	[thread overview]
Message-ID: <20100928133345.GA8575@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <20100928112643.GC22734@oksana.dev.rtsoft.ru>

On Tue, Sep 28, 2010 at 06:26:43AM -0500, Anton Vorontsov wrote:
>On Tue, Sep 28, 2010 at 12:41:22PM +0300, Felipe Balbi wrote:
>> On Tue, Sep 28, 2010 at 04:39:17AM -0500, Grazvydas Ignotas wrote:
>> >On Tue, Sep 28, 2010 at 12:06 PM, Felipe Balbi <balbi@ti.com> wrote:
>> >>On Tue, Sep 28, 2010 at 04:02:48AM -0500, Grazvydas Ignotas wrote:
>> >>>>
>> >>>>Charger event is SENT by charger driver when it verifies it's attached
>> >>>>to a wall charger.
>> >>>
>> >>>Isn't that a job for musb/gadget? Detecting D+/D- being shorted by
>> >>>charger or something like that? I don't think BCI is able to detect
>> >>>charger.
>> >>
>> >>it's part of the charger detection right ? and according to trm, it's on
>> >>the BCI (actually BCC) role to take care of that :-)
>> >
>> >Hm you are probably talking about TWL5031, which has redesigned
>> >charger block that is named BCC. TWL4030 charger is different, called
>> >BCI and requires software charger detection from what I see in it's
>> >TRM.
>>
>> ok, might be that I got confused. Then it's ok the way it is. So we need
>> other means to detect the charger :-p
>
>May we consider this as a minor issue that can be improved later?

Sure, it's fine.

>If so, I would like to apply it, but I'll wait a day or two for
>Reviewed-by or Acked-by tags to give the proper credits.

Here you go.

Acked-by: Felipe Balbi <balbi@ti.com>

-- 
balbi

  reply	other threads:[~2010-09-28 13:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 20:18 Grazvydas Ignotas
2010-09-28  6:05 ` Felipe Balbi
2010-09-28  8:37   ` Grazvydas Ignotas
2010-09-28  8:42     ` Felipe Balbi
2010-09-28  9:02       ` Grazvydas Ignotas
2010-09-28  9:06         ` Felipe Balbi
2010-09-28  9:39           ` Grazvydas Ignotas
2010-09-28  9:41             ` Felipe Balbi
2010-09-28 11:26               ` Anton Vorontsov
2010-09-28 13:33                 ` Felipe Balbi [this message]
2010-09-30 15:33                   ` Anton Vorontsov

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=20100928133345.GA8575@legolas.emea.dhcp.ti.com \
    --to=balbi@ti.com \
    --cc=arunrmurthy.83@gmail.com \
    --cc=cbouatmailru@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.com \
    --cc=notasas@gmail.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

Powered by JetHome