From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/2] mfd: arizona: Defer patch initialistation until after first device boot
Date: Mon, 3 Dec 2012 00:41:13 +0100 [thread overview]
Message-ID: <20121202234113.GX3176@sortiz-mobl> (raw)
In-Reply-To: <1354416107-17481-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Hi Mark,
On Sun, Dec 02, 2012 at 11:41:46AM +0900, Mark Brown wrote:
> Make sure that we don't race with the initial device boot by only doing
> the initialisation after we've waited for the boot to complete.
>
> The runtime PM code already waits for the boot to complete before it
> syncs the register patches so in most systems if a race does occur we will
> power down very soon afterwards and recover anyway.
>
> Reported-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> drivers/mfd/arizona-core.c | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
Applied, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-12-02 23:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 2:41 [PATCH 1/2] mfd: arizona: Defer patch initialistation until after first device boot Mark Brown
2012-12-02 2:41 ` [PATCH 2/2] mfd: wm5102: Add tuning for revision B Mark Brown
2012-12-02 23:42 ` Samuel Ortiz
2012-12-02 23:41 ` Samuel Ortiz [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-01 17:11 [PATCH 1/2] mfd: arizona: Defer patch initialistation until after first device boot Mark Brown
2012-12-02 2:34 ` 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=20121202234113.GX3176@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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