From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Bibek Basu <bbasu@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pritesh Raithatha <praithatha@nvidia.com>
Subject: Re: [PATCH] pinctrl: tegra: add suspend-resume support
Date: Wed, 3 Apr 2013 16:09:09 +0200 [thread overview]
Message-ID: <CACRpkdYLSVkfAxVBMBnkyePujaoQQqB27UiG+-r2APkEDrfLrA@mail.gmail.com> (raw)
In-Reply-To: <5154827B.8010701@wwwdotorg.org>
On Thu, Mar 28, 2013 at 6:48 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
> Why can't we just use the device suspend/resume functions rather than
> global (syscore) suspend/resume functions? Presumably this is to ensure
> that all other drivers suspend first, then the pinctrl driver does, and
> the reverse for resume. Can't we rely on deferred probe to ensure that
> instead?
>
> To make that work, we might need every affected driver to define a dummy
> pinmux state in DT that references the pinctrl driver, to make sure they
> all get probed after the pinctrl driver.
Hm that reminds me of that policy change I suggested a while back to
do this instead of using hogs where possible.
It has the nice side-effect that when we inspect the debugfs info
all pins will be properly owned by respective consuming device.
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-04-03 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 17:11 Bibek Basu
2013-03-28 17:48 ` Stephen Warren
2013-04-01 4:34 ` Bibek Basu
2013-04-01 16:23 ` Stephen Warren
2013-04-03 14:09 ` Linus Walleij [this message]
2013-04-03 17:16 ` Stephen Warren
2013-04-03 20:28 ` Linus Walleij
2013-04-03 16:21 ` Linus Walleij
2013-04-23 17:52 ` Bibek Basu
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=CACRpkdYLSVkfAxVBMBnkyePujaoQQqB27UiG+-r2APkEDrfLrA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bbasu@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=praithatha@nvidia.com \
--cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®