From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-mmc@vger.kernel.org
Cc: cjb@laptop.org, linus.walleij@linaro.org,
linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH v2 0/3] mmc: fixes for aggressive clock gating framework
Date: Thu, 18 Aug 2011 15:23:46 +0300 [thread overview]
Message-ID: <cover.1313664897.git.mika.westerberg@linux.intel.com> (raw)
Hi,
This is an updated series which should fix few races seen when aggressive
clock gating is active. The first patch actually just renames the gating
functions to make their use-cases a bit more clear.
Second and third patches fix the races itself.
Previous version of the series can be seen here
http://article.gmane.org/gmane.linux.kernel.mmc/9611
Changes to previous version:
* rename clock gating functions
* use mmc_host_clk_hold() and mmc_host_clk_release() to protect the
ios updates
* use non-reentrant workqueue instead of the default
Please review, thanks.
Mika Westerberg (3):
mmc: rename mmc_host_clk_{ungate|gate} to mmc_host_clk_{hold|release}
mmc: prevent aggressive clock gating to race with ios updates
mmc: use non-reentrant workqueue for clock gating
drivers/mmc/core/core.c | 35 +++++++++++++++++++++++++++++++----
drivers/mmc/core/host.c | 12 ++++++------
drivers/mmc/core/host.h | 8 ++++----
3 files changed, 41 insertions(+), 14 deletions(-)
--
1.7.5.4
next reply other threads:[~2011-08-18 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 12:23 Mika Westerberg [this message]
2011-08-18 12:23 ` [PATCH v2 1/3] mmc: rename mmc_host_clk_{ungate|gate} to mmc_host_clk_{hold|release} Mika Westerberg
2011-08-18 12:23 ` [PATCH v2 2/3] mmc: prevent aggressive clock gating to race with ios updates Mika Westerberg
2011-08-18 12:23 ` [PATCH v2 3/3] mmc: use non-reentrant workqueue for clock gating Mika Westerberg
2011-08-19 9:58 ` [PATCH v2 0/3] mmc: fixes for aggressive clock gating framework Linus Walleij
2011-08-19 17:13 ` Chris Ball
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=cover.1313664897.git.mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=cjb@laptop.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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