[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111214120240.GC25088@sirena.org.uk>
Date: Wed, 14 Dec 2011 12:02:40 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: "Moffett, Kyle D" <Kyle.D.Moffett@...ing.com>
Cc: Rob Herring <robherring2@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>, Liam Girdwood <lrg@...com>,
Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [REPOST RFC PATCH 0/3] New "gpio-poweroff" driver to turn off
platform devices with GPIOs
On Tue, Dec 13, 2011 at 02:44:48PM -0600, Moffett, Kyle D wrote:
> I looked at it a bit when I was generalizing my code, but it seemed
> dramatically more complicated than I needed, and I couldn't see any
> reasonable way to hook it from the machine_poweroff() code.
Some ST platform had to do odd stuff with regulators to power off, it
made a platform device representing the odd poweroff code.
> There's also the fact that I was looking for a pure-device-tree type
> of driver and the regulator framework does not seem to support the
> standard OF-platform probe system.
The regulator API in -next has DT bindings.
--
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