From: Sujit Reddy Thumma <sthumma@codeaurora.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Per Forlin <per.friden@stericsson.com>,
linux-mmc@vger.kernel.org, cjb@laptop.org
Subject: Re: [PATCH] mmc: core: Ensure clocks are always enabled before host interaction
Date: Tue, 24 Jan 2012 09:14:51 +0530 [thread overview]
Message-ID: <4F1E2933.8030708@codeaurora.org> (raw)
In-Reply-To: <CACRpkdbZS7TxKSpKR0DV4TC4dOzO_q83U1bd0HonKC2GBDBOgA@mail.gmail.com>
Hi Linus Walleij,
On 12/30/2011 7:44 AM, Linus Walleij wrote:
> On Mon, Dec 12, 2011 at 9:21 AM, Sujit Reddy Thumma
> <sthumma@codeaurora.org> wrote:
>
>> Ensure clocks are always enabled before any interaction with the
>> host controller driver. This makes sure that there is no race
>> between host execution and the core layer turning off clocks
>> in different context with clock gating framework.
>>
>> Signed-off-by: Sujit Reddy Thumma<sthumma@codeaurora.org>
>
> I guess Per Förlin may not be available, but would have preferred to
> have his view on this as well, since he knows the semantics of
> pre/post-req.
I have checked the implementation for pre-req and post-req in mmc host
drivers. There is no interaction to the controller or card registers in
these functions, but in future if drivers appeal to configure their
controller in these functions then we must have clocks enabled.
Per, if you are available can you comment on this?
>
> However from my PoV it looks nice and clean, and you surely have
> done some serious testing on things like SDIO so:
> Acked-by: Linus Walleij<linus.walleij@linaro.org>
Thanks. Tested with SD3.0, eMMC4.4 and SDIO2.0 cards.
Thanks,
Sujit
next prev parent reply other threads:[~2012-01-24 3:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 8:21 [PATCH] mmc: core: Ensure clocks are always enabled before host interaction Sujit Reddy Thumma
2011-12-12 9:12 ` Subhash Jadavani
2011-12-27 4:53 ` Sujit Reddy Thumma
2011-12-30 2:14 ` Linus Walleij
2012-01-24 3:44 ` Sujit Reddy Thumma [this message]
2012-01-30 12:48 ` Per Forlin
2012-01-30 19:33 ` Linus Walleij
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=4F1E2933.8030708@codeaurora.org \
--to=sthumma@codeaurora.org \
--cc=cjb@laptop.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=per.friden@stericsson.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;
as well as URLs for NNTP newsgroup(s).