From: Chris Ball <cjb@laptop.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Shawn Guo <shawn.guo@linaro.org>,
Zhangfei Gao <zhangfei.gao@marvell.com>,
Kevin Liu <kliu5@marvell.com>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci-pltfm: Add a common clk API based implementation of get_timeout_clock
Date: Mon, 11 Feb 2013 11:26:03 -0500 [thread overview]
Message-ID: <87obfqstpg.fsf@octavius.laptop.org> (raw)
In-Reply-To: <1359397632-31646-1-git-send-email-lars@metafoo.de> (Lars-Peter Clausen's message of "Mon, 28 Jan 2013 19:27:12 +0100")
Hi Lars-Peter,
On Mon, Jan 28 2013, Lars-Peter Clausen wrote:
> Quite a few drivers have a implementation of the get_timeout_clock callback
> which simply returns the result of clk_get_rate on devices clock. This patch
> adds a common implementation of this to the sdhci-pltfm module and replaces all
> custom implementations with the common one.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
> I've only runtime tested this patch on a platform which is not yet upstream. For
> the drivers which are modified in this patch I've only done compile time
> testing. But I think all changes, but maybe the bcm2835 one, are straight
> forward.
Looks like this has good testing coverage now; pushed to mmc-next for
3.9, thanks.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2013-02-11 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 18:27 [PATCH] mmc: sdhci-pltfm: Add a common clk API based implementation of get_timeout_clock Lars-Peter Clausen
2013-01-29 5:45 ` Stephen Warren
2013-01-29 9:22 ` Lars-Peter Clausen
2013-01-30 4:22 ` Stephen Warren
2013-01-29 5:51 ` Shawn Guo
2013-02-11 16:26 ` Chris Ball [this message]
[not found] <25B60CDC2F704E4E9D88FFD52780CB4C08B059D3F2@SC-VEXCH1.marvell.com>
2013-01-29 9:06 ` Kevin Liu
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=87obfqstpg.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=kliu5@marvell.com \
--cc=lars@metafoo.de \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.org \
--cc=zhangfei.gao@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.