From: "Moffett, Kyle D" <Kyle.D.Moffett@boeing.com>
To: Rob Herring <robherring2@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>, Liam Girdwood <lrg@ti.com>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [REPOST RFC PATCH 0/3] New "gpio-poweroff" driver to turn off platform devices with GPIOs
Date: Tue, 13 Dec 2011 14:44:48 -0600 [thread overview]
Message-ID: <895CF182-4BF7-4DF5-A467-944EC008DBC3@boeing.com> (raw)
In-Reply-To: <4EE7A31E.7080301@gmail.com>
On Dec 13, 2011, at 14:10, Rob Herring wrote:
> On 12/13/2011 12:23 PM, Kyle Moffett wrote:
>>
>> I posted this patch series a few weeks ago and saw no responses, so I
>> tweaked the CC list and am reposting it again for review.
>>
>> I'm working on support for some custom hardware of ours, and part of
>> the support code is the ability for the software to shutdown the power
>> supply using GPIOs (via an I2C GPIO controller).
>>
>> I previously had this in my platform code, but it seemed generically
>> useful, so I split it out into a separate module for others to use.
>>
>> The first two patches are generic of_gpio enhancements, providing some
>> new library functions for requesting lots of GPIOs at once.
>>
>> The third patch is the actual driver itself. The driver can be used to
>> instantiate a platform device as a whole-machine-poweroff device as we
>> use it on our hardware. Alternatively it can instantiate multiple
>> platform devs at specific locations on the device tree which trigger
>> from the platform_driver->shutdown() callback.
>>
>> For architectures which are still stuck in the dark ages, this driver
>> also supports being instantiated via legacy platform_data.
>
> Leave them there... :)
Mostly this was out of convenience and imitating the other OF platform
drivers. I wrote it and ended up with a struct full of probe data being
passed between functions, so I just called it "platform_data" :-D.
>> The OpenFirmware binding documentation is added in the third patch.
>> Since this is my first cut, it's a little rough, so please be gentle.
>>
>> I'm interested to know what you all think.
>
> Does the regulator framework gpio-regulator not work for this?
Well, when I initially wrote this code, the regulator framework didn't
exist :-D.
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.
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.
I will admit that there's probably some value in having a more generic
GPIO-power-control (instead of just poweroff), but I don't have the
target use-case to be able to design for it.
> The DT gpio patches look useful on their own.
Yeah, it seemed like a fairly generic extension of the existing API.
Thanks for the comments!
Cheers,
Kyle Moffett
--
Curious about my work on the Debian powerpcspe port?
I'm keeping a blog here: http://pureperl.blogspot.com/
next prev parent reply other threads:[~2011-12-13 20:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 18:23 Kyle Moffett
2011-12-13 18:23 ` [REPOST RFC PATCH 1/3] of_gpio: Extend of_gpio_count() to support other property names Kyle Moffett
2011-12-13 18:23 ` [REPOST RFC PATCH 2/3] of_gpio: Add new helpers for easily requesting lots of GPIOs Kyle Moffett
2012-01-04 18:49 ` Grant Likely
2011-12-13 18:23 ` [REPOST RFC PATCH 3/3] New "gpio-poweroff" driver to turn off platform devices with GPIOs Kyle Moffett
2011-12-13 19:10 ` [REPOST RFC PATCH 0/3] " Rob Herring
2011-12-13 20:44 ` Moffett, Kyle D [this message]
2011-12-14 12:02 ` Mark Brown
2011-12-14 20:34 ` Moffett, Kyle D
2011-12-17 9:20 ` Mark Brown
2011-12-19 16:56 ` Moffett, Kyle D
2011-12-20 1:38 ` Mark Brown
2011-12-20 1:53 ` Moffett, Kyle D
2011-12-20 14:38 ` Mark Brown
2011-12-14 11:59 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=895CF182-4BF7-4DF5-A467-944EC008DBC3@boeing.com \
--to=kyle.d.moffett@boeing.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=robherring2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®