From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Abhilash Kesavan <kesavan.abhilash@gmail.com>
Cc: devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, grant.likely@secretlab.ca,
lrg@ti.com, Doug Anderson <dianders@chromium.org>,
Olof Johansson <olofj@google.com>,
Thomas Abraham <thomas.abraham@linaro.org>
Subject: Re: Regulator suspend state dt question
Date: Thu, 6 Dec 2012 15:28:38 +0900 [thread overview]
Message-ID: <20121206062836.GH10867@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAM4voa=X_rBkSXRHd=oEOnXhgyfSAeD8LmYnsTeQtd-SYKWwPg@mail.gmail.com>
On Thu, Dec 06, 2012 at 11:55:11AM +0530, Abhilash Kesavan wrote:
> As of now there is no support in the regulator core to specify the suspend state
> (mode, enabled/disabled) using dt. I can add new properties specifying
> the intial_state,
> mode, enable/disable but I am not too sure if it is appropriate to add
> such bindings to
> the device tree as they are not actually describing the hardware.
Well, it does depend on the hardware a bit - some hardware is hard wired
to only have one possible suspend state due to power up requirements.
But for a lot of hardware it's flexible...
> Is calling regulator_suspend_prepare from a machine specific file an option ?
This is not really relevant, it's an orthogonal thing about when we
trigger the state transition in the regulator.
It's not clear what a good solution is here, sorry.
next prev parent reply other threads:[~2012-12-06 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 6:25 Regulator suspend state dt question Abhilash Kesavan
2012-12-06 6:28 ` Mark Brown [this message]
2012-12-06 7:02 ` Abhilash Kesavan
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=20121206062836.GH10867@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dianders@chromium.org \
--cc=grant.likely@secretlab.ca \
--cc=kesavan.abhilash@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=olofj@google.com \
--cc=thomas.abraham@linaro.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.