From: Mark Brown <broonie@kernel.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Mike Turquette <mturquette@linaro.org>,
Ming Lei <tom.leiming@gmail.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Saravana Kannan <skannan@codeaurora.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Liam Girdwood <lrg@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] driver core: Add API to wait for deferred probe to complete during init
Date: Fri, 10 May 2013 10:30:07 +0100 [thread overview]
Message-ID: <20130510093007.GL3200@sirena.org.uk> (raw)
In-Reply-To: <CACxGe6sO7kEZgg6km4bzP1cq+2MqGb=D4cZbuWELoz+yhaO6KQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
On Thu, May 09, 2013 at 05:39:03PM +0100, Grant Likely wrote:
> +1. You can /minimize/ up-down cycles with the kind of optimization
> that is being attempted here, but the driver still *must* deal with
> bringing resources back up if they get requested "later than you would
> otherwise like".
Now that I think about it we should probably have a debug option like
the shared IRQ testing one which does actually disable all resources as
soon as the kernel gains control of them in order to help with test
coverage for this.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-10 9:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 5:18 [PATCH 0/3] Fix disable of unused clk/regulator with deferred probe Saravana Kannan
2013-05-09 5:18 ` [PATCH 1/3] driver core: Add API to wait for deferred probe to complete during init Saravana Kannan
2013-05-09 10:07 ` Ming Lei
2013-05-09 11:50 ` Grant Likely
2013-05-09 13:50 ` Mark Brown
2013-05-09 14:14 ` Russell King - ARM Linux
2013-05-09 14:37 ` Mark Brown
2013-05-09 15:07 ` Russell King - ARM Linux
2013-05-09 15:43 ` Mark Brown
2013-05-09 18:39 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-09 16:39 ` Grant Likely
2013-05-10 9:30 ` Mark Brown [this message]
2013-05-09 16:52 ` Saravana Kannan
2013-05-09 18:09 ` Grant Likely
2013-05-09 18:12 ` Saravana Kannan
2013-05-09 14:32 ` Ming Lei
2013-05-09 5:18 ` [PATCH 2/3] clk: Disable unused clocks after deferred probing is done Saravana Kannan
2013-05-09 5:18 ` [PATCH 3/3] regulator: core: Disable unused regulators " Saravana Kannan
2013-05-09 18:35 ` [PATCH v2 1/2] clk: Disable unused clocks " Saravana Kannan
2013-05-10 6:45 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-10 23:03 ` Saravana Kannan
2013-05-22 10:35 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-16 4:34 ` Saravana Kannan
2013-05-16 12:55 ` Ulf Hansson
2013-05-16 19:23 ` Saravana Kannan
2013-05-29 7:51 ` Mike Turquette
2013-05-30 1:46 ` Saravana Kannan
2013-05-09 18:35 ` [PATCH 2/2] regulator: core: Disable unused regulators " Saravana Kannan
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=20130510093007.GL3200@sirena.org.uk \
--to=broonie@kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lrg@ti.com \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.org \
--cc=skannan@codeaurora.org \
--cc=tom.leiming@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