On Monday 23 September 2013 22:47:15 Sebastian Reichel wrote: > On Mon, Sep 23, 2013 at 10:06:46PM +0200, Pali Rohár wrote: > > On Monday 23 September 2013 22:00:09 Sebastian Reichel wrote: > > > On Mon, Sep 23, 2013 at 09:16:18PM +0200, Pali Rohár wrote: > > > > It is not as simple as it looks. This is reason why I > > > > submited this patch long time after I submited bq2415x > > > > driver. > > > > > > > > Problem is that for rx51 is needed specific function > > > > which connect to two drivers (bq2415x and isp1704) plus > > > > it call specific rx51 board functions. > > > > > > > > Something which cannot be in DT (unless DT support C/ASM > > > > code). > > > > > > mh could isp1704 driver expose the data via the regulator > > > framework? > > > > No, isp1704 is power supply driver and export data via power > > supply (sysfs) interface. It is not regulator but charger > > driver. > > well it does not charge the battery directly, but just > provides a power line with 5 Volt and a specified amount of > current to the system, doesn't it? > No, isp1704 driver is doing fastcharger detection (and then export charger type via sysfs power supply) based on musb usb events. Real charging (enabling/disabling and setting properties) is done by bq24150a chip which has own power driver bq2415x_charger. As already wrote this is not simple and this is reason why I sent board data and functions only now... > From my POV this is a candiate for the regulator framework: > > https://www.kernel.org/doc/Documentation/power/regulator/overv > iew.txt > > -- Sebastian -- Pali Rohár pali.rohar@xxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part.
