[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1203683790.4071.262.camel@localhost.localdomain>
Date: Fri, 22 Feb 2008 12:36:30 +0000
From: Liam Girdwood <lg@...nsource.wolfsonmicro.com>
To: eric miao <eric.y.miao@...il.com>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.arm.linux.org.uk>
Subject: Re: [UPDATED v2][PATCH 0/6] regulator: voltage and current
regulator framework
On Fri, 2008-02-22 at 11:22 +0800, eric miao wrote:
>
> I have a rough peek into the git tree on opensource.wolfsonmicro.com,
> find another PMIC framework, and here instead is a regulator framework,
> looks like a simplified or dedicated one. What is their relationship?
>
This is probably the old version you came across. It was tightly coupled
to a particular PMIC and SoC CPU and not portable. The new version that
I posted is portable and not tied to a particular PMIC or CPU
architecture. The new version is hosted in the audioplus git repository
(imx31 branch).
> 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
>
> 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. 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@...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