From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: "Moffett,
Kyle D" <Kyle.D.Moffett-X8CqP27nNzzQT0dZR+AlfA@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Liam Girdwood <lrg-l0cyMroinI0@public.gmane.org>
Subject: Re: [REPOST RFC PATCH 0/3] New "gpio-poweroff" driver to turn off platform devices with GPIOs
Date: Sat, 17 Dec 2011 09:20:44 +0000 [thread overview]
Message-ID: <20111217092044.GC2833@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <E30C4693-0D31-4A9A-9E9D-0FC03C5F6B8A-X8CqP27nNzzQT0dZR+AlfA@public.gmane.org>
On Wed, Dec 14, 2011 at 02:34:37PM -0600, Moffett, Kyle D wrote:
> On Dec 14, 2011, at 07:02, Mark Brown wrote:
> > The regulator API in -next has DT bindings.
> Based on the description of our hardware, is there a good way that I
> can wire up gpio-regulator driver to our hardware with just the device
> tree (and maybe one small board-specific function) to make it shut down
> each domain in sequence at poweroff time? Otherwise I will just go back
> to my custom board-specific function for GPIO-twiddling.
No, it's a very rare use case so there's nothing off the shelf. But it
should be straightfoward to write a device driver doing this.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Moffett, Kyle D" <Kyle.D.Moffett@boeing.com>
Cc: Rob Herring <robherring2@gmail.com>,
"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: Sat, 17 Dec 2011 09:20:44 +0000 [thread overview]
Message-ID: <20111217092044.GC2833@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <E30C4693-0D31-4A9A-9E9D-0FC03C5F6B8A@boeing.com>
On Wed, Dec 14, 2011 at 02:34:37PM -0600, Moffett, Kyle D wrote:
> On Dec 14, 2011, at 07:02, Mark Brown wrote:
> > The regulator API in -next has DT bindings.
> Based on the description of our hardware, is there a good way that I
> can wire up gpio-regulator driver to our hardware with just the device
> tree (and maybe one small board-specific function) to make it shut down
> each domain in sequence at poweroff time? Otherwise I will just go back
> to my custom board-specific function for GPIO-twiddling.
No, it's a very rare use case so there's nothing off the shelf. But it
should be straightfoward to write a device driver doing this.
next prev parent reply other threads:[~2011-12-17 9:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 18:23 [REPOST RFC PATCH 0/3] New "gpio-poweroff" driver to turn off platform devices with GPIOs Kyle Moffett
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
2011-12-14 12:02 ` Mark Brown
[not found] ` <20111214120240.GC25088-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2011-12-14 20:34 ` Moffett, Kyle D
2011-12-14 20:34 ` Moffett, Kyle D
[not found] ` <E30C4693-0D31-4A9A-9E9D-0FC03C5F6B8A-X8CqP27nNzzQT0dZR+AlfA@public.gmane.org>
2011-12-17 9:20 ` Mark Brown [this message]
2011-12-17 9:20 ` Mark Brown
2011-12-19 16:56 ` Moffett, Kyle D
[not found] ` <D482A908-020C-43E0-ADFC-33AE213D7257-X8CqP27nNzzQT0dZR+AlfA@public.gmane.org>
2011-12-20 1:38 ` Mark Brown
2011-12-20 1:38 ` Mark Brown
[not found] ` <20111220013819.GV2860-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2011-12-20 1:53 ` Moffett, Kyle D
2011-12-20 1:53 ` Moffett, Kyle D
[not found] ` <B187B965-8671-485E-9CAB-7CF3468D2ED6-X8CqP27nNzzQT0dZR+AlfA@public.gmane.org>
2011-12-20 14:38 ` Mark Brown
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=20111217092044.GC2833@opensource.wolfsonmicro.com \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=Kyle.D.Moffett-X8CqP27nNzzQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lrg-l0cyMroinI0@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.