| 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
| ||
|
Message-ID: <AANLkTim28RmH28LGgp6bEJ7XbyL4oO_5_C0phLL86roY@mail.gmail.com> Date: Tue, 28 Sep 2010 12:39:17 +0300 From: Grazvydas Ignotas <notasas@...il.com> To: balbi@...com Cc: Anton Vorontsov <cbouatmailru@...il.com>, "linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Chikkature Rajashekar, Madhusudhan" <madhu.cr@...com> Subject: Re: [PATCH v4] power_supply: Add driver for TWL4030/TPS65950 BCI charger On Tue, Sep 28, 2010 at 12:06 PM, Felipe Balbi <balbi@...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. -- 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/
Powered by blists - more mailing lists