From: Chris Ball <cjb@laptop.org>
To: Daniel Mack <zonque@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org,
linux-omap@vger.kernel.org, "Cousson, Benoit" <b-cousson@ti.com>
Subject: Re: [PATCH] ARM: OMAP: hsmmc: add max_freq field
Date: Sun, 19 Feb 2012 11:16:02 -0500 [thread overview]
Message-ID: <m2zkce6bp9.fsf@bob.laptop.org> (raw)
In-Reply-To: <1329654033-19584-1-git-send-email-zonque@gmail.com> (Daniel Mack's message of "Sun, 19 Feb 2012 13:20:33 +0100")
Hi,
On Sun, Feb 19 2012, Daniel Mack wrote:
> External circuitry like level shifters may limit the maximum operation
> speed of the hsmmc controller. Add a field to struct omap2_hsmmc_info
> so boards can adjust the setting on demand.
>
> Signed-off-by: Daniel Mack <zonque@gmail.com>
> Acked-by: Tony Lindgren <tony@atomide.com>
> Cc: Chris Ball <cjb@laptop.org>
> Cc: Cousson, Benoit <b-cousson@ti.com>
> ---
>
> This trivial patch is in my queue for some time already, and Tony acked
> on it awhile back. I was told to take Chris Ball in the loop as there
> is currently no OMAP MMC maintainer.
>
> This still applies cleanly to 3.3-rc4. Chris, can you queue this?
Thanks, queued in mmc-next now. (The arch/arm/mach-omap2/hsmmc.c
change did not apply cleanly, though; I fixed that.)
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-02-19 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 12:20 [PATCH] ARM: OMAP: hsmmc: add max_freq field Daniel Mack
2012-02-19 16:16 ` Chris Ball [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-14 13:22 Daniel Mack
2011-12-22 18:51 ` Tony Lindgren
2011-12-22 19:37 ` Kishore Kadiyala
2011-12-22 23:02 ` Daniel Mack
2011-12-23 15:40 ` T Krishnamoorthy, Balaji
2011-12-29 13:22 ` Daniel Mack
2012-02-17 13:44 ` Daniel Mack
2012-02-17 17:09 ` Cousson, Benoit
2012-03-02 0:11 ` Tony Lindgren
2012-03-02 7:11 ` S, Venkatraman
2012-03-02 9:14 ` S, Venkatraman
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=m2zkce6bp9.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=zonque@gmail.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).