public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Mark Brown <broonie@kernel.org>, Liam Girdwood <lgirdwood@gmail.com>
Subject: Implementing a gpio based regulator with status pins
Date: Fri, 22 May 2015 20:49:01 -0700	[thread overview]
Message-ID: <555FF8AD.5010502@roeck-us.net> (raw)

Hi all,

I have a system with a gpio based regulator which does not only have an
enable pin, but also a status pin to report the actual power status.
In some cases there may be a secondary status pin, making it possible
to report on/off/error.

Some twist of this is that power activation time is not exactly well
defined; activation can vary from board to board. I could of course
use the existing (fixed) timeout supported by the regulator core,
but it would be nice to be able to use an interrupt on the status
pin(s), possibly with a timeout, to achieve a dynamic activation
time.

The gpio pin(s) support interrupts, making it possible to report
status updates, which might be useful if the power source goes bad
or to support a dynamic power enable time.

As far as I can see, the existing gpio regulators don't implement
status pins.

What would be the best way to implement this ?

- Add status support to the 'fixed' regulator
- Add status support to gpio-regulator.c
- Add (gpio) status support to the regulator core
- Write a new regulator driver
- Something else

Thanks,
Guenter

             reply	other threads:[~2015-05-23  3:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-23  3:49 Guenter Roeck [this message]
2015-05-25 12:12 ` Implementing a gpio based regulator with status pins 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=555FF8AD.5010502@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox