linux-kernel - RE: N900 DT

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20ADAB092842284E95860F279283C5640AA999C5@BGSMSX104.gar.corp.intel.com>
Date:	Mon, 28 Oct 2013 03:01:35 +0000
From:	"Tc, Jenny" <jenny.tc@...el.com>
To:	Pali Rohár <pali.rohar@...il.com>,
	Sebastian Reichel <sre@...g0.de>
CC:	Anton Vorontsov <anton.vorontsov@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: N900 DT


> 
> On Saturday 26 October 2013 02:25:02 Sebastian Reichel wrote:
> > Hi Pali,
> >
> > On Fri, Oct 25, 2013 at 08:39:40PM +0200, Pali Rohár wrote:
> > > Now I found this patch and it looks like it will be in mainline
> > > kernel. And after that it could be simple to listen for needed
> > > events from isp driver in my bq driver (without touching isp).
> > >
> > > https://lkml.org/lkml/2013/7/25/204
> > >
> > > Can you look at isp1704 driver for DT support? I think that only one
> > > gpio needs to be passed to driver from board data.
> >
> > I had a quick overview over Jenny's patchset [0] (the patch you
> > referenced is part of a bigger patchset). I don't think the scenario
> > found in the Nokia N900 is covered by it, but probably now is the time
> > to change it :)
> >
> > So for everybody new to this thread:
> >
> > Multiple chips are involved in the charging of the Nokia N900
> > battery:
> >
> > bq27200:   This chip is used for reading battery status. AFAIK
> >            it's not directly involved in charging the battery.
> > bq24150a:  This chip takes care of actually charging the battery. It
> > has no clue about USB related stuff. The maximum
> > current it draws can be configured, though. isp1704:   USB
> > charger detector. This chip is used to detect how much current may be
> > used by the bq24150a chip. rx51-temp: Analog temperature sensor for
> > the battery, which is connected via an analog-digital-converter.
> >
> > The question is how to connected these driver with each other if
> > device tree is used to boot the system. Any suggestions?
> >
The patch http://thread.gmane.org/gmane.linux.kernel/1377608 is intended to cover similar
scenario. It connects different components involved in charging to monitor and control the
charging.  This keeps the charging logic outside the charger driver and the charger driver just
need to be a h/w abstraction layer. It doesn't take care of the device tree part. But as long as the
drivers are registered with power supply class,  the framework can take actions. Hope this helps.

> > [0] http://thread.gmane.org/gmane.linux.kernel/1377608
> >
> > -- Sebastian
> 
> What I need is receive property change event (from isp1704) in bq24150a. And with this
> patch https://lkml.org/lkml/2013/7/25/204
> bq24150a driver can receive them and use only these which comes from driver specified in
> DT (on n900 from isp1704).
>