From: Linus Walleij <linus.walleij@linaro.org>
To: "Dong, Chuanxiao" <chuanxiao.dong@intel.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Chris Ball <cjb@laptop.org>, David Strobach <lalochcz@gmail.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Greg KH <greg@kroah.com>,
"horms@verge.net.au" <horms@verge.net.au>,
"damm@opensource.se" <damm@opensource.se>,
Andrei Warkentin <andreiw@motorola.com>
Subject: Re: kernel 2.6.38.6 MMC controller problem (fwd)
Date: Wed, 18 May 2011 07:29:53 +0200 [thread overview]
Message-ID: <BANLkTi=M+8nBZGzUOvEa67nb2LuTbQwx=Q@mail.gmail.com> (raw)
In-Reply-To: <5D8008F58939784290FAB48F54975198419F754247@shsmsx502.ccr.corp.intel.com>
2011/5/17 Dong, Chuanxiao <chuanxiao.dong@intel.com>:
> mmc clock gating thread may be delayed for a long time in some scenarios.
> Since mmc_claim_host will be also used by other thread. I think this will
> possibly happen.
That shouldn't matter? host->lock will make sure the requests are
serialized will it not?
Linus Walleij
next prev parent reply other threads:[~2011-05-18 5:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 7:06 kernel 2.6.38.6 MMC controller problem (fwd) Guennadi Liakhovetski
[not found] ` <BANLkTinbJfDLp5nfkq-VTYLJvihT1thXvA@mail.gmail.com>
2011-05-16 8:42 ` David Strobach
2011-05-16 8:45 ` Guennadi Liakhovetski
2011-05-16 10:26 ` Jaehoon Chung
2011-05-16 10:39 ` Guennadi Liakhovetski
2011-05-16 10:48 ` Jaehoon Chung
2011-05-16 14:52 ` Chris Ball
2011-05-16 15:15 ` David Strobach
2011-05-16 15:56 ` Chris Ball
2011-05-16 16:07 ` Guennadi Liakhovetski
2011-05-16 16:37 ` Chris Ball
2011-05-16 16:42 ` Guennadi Liakhovetski
2011-05-16 17:56 ` Linus Walleij
2011-05-17 9:20 ` Dong, Chuanxiao
2011-05-18 5:29 ` Linus Walleij [this message]
2011-05-18 6:01 ` Dong, Chuanxiao
2011-05-16 16:07 ` David Strobach
2011-05-16 16:29 ` David Strobach
2011-05-18 13:29 ` David Strobach
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='BANLkTi=M+8nBZGzUOvEa67nb2LuTbQwx=Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andreiw@motorola.com \
--cc=chuanxiao.dong@intel.com \
--cc=cjb@laptop.org \
--cc=damm@opensource.se \
--cc=g.liakhovetski@gmx.de \
--cc=greg@kroah.com \
--cc=horms@verge.net.au \
--cc=lalochcz@gmail.com \
--cc=linux-mmc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).