Re: [UPDATED v2][PATCH 0/6] regulator: voltage and current regulator framework

[David Brownell]

> > For those PMIC that covers additional features, like
> >   - usb vbus detection (or pull-up/pull-down)
> >   - audio codec
> >   - touch screen
> >   - battery monitor/ fuel gauge
> >   - battery charger
> >   - possible many others

Certainly many others ... like MMC transceivers, high speed USB
transceivers, RTCs, and lots of other analog and "high voltage"
(more than 1.8V, say) circuits that should be offloaded from 
SOCs for systems built with 90nm (and smaller) processes.


> > How do you plan to handle them?
>
> The WM8350 and MC13783 are both multi feature PMIC's like above. We
> handle WM8350 PMIC access via a bus manager.

I think most such PMIC cases are best modeled as multi-function
devices, plugging into numerous different frameworks.  That may
be implied by "bus manager".

There are already at least two PMIC drivers in drivers/i2c/chips
in the mainstream kernel (tps65010.c and menelaus.c) and I'd think
one factor to review of this framework is whether those chips
could reasonbly be used in this framework.

So for example the tps65010 presumes that fuel gauging is done
by a separate chip (presumptively using HDQ/1-Wire), and in fact
that may be part of a battery pack.  And the DAC functions, like
touchscreens and (input) codecs, use other dedicated chips.  As
time goes by, those PMIC chips integrate lots more functionality..

- Dave


>	This controls IO access to
> the WM8350 so that client driver (including the regulator driver) IO
> does not collide. We also cache non volatile PMIC registers to speed up
> access. Please have a look at drivers/regulator/wm8350/wm8350-bus.c in
> the imx31 branch for details.
>
> Liam
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/