From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3] mmc: omap_hsmmc: Enable HSPE bit for high speed cards
Date: Wed, 31 Oct 2012 22:16:26 +0200 [thread overview]
Message-ID: <20121031201626.GA28784@arwen.pp.htv.fi> (raw)
In-Reply-To: <CAOyx1LrKBE+xzSRN4F=+e1DuMJL+5SAv-YkJWJdDw8p=kDojmw@mail.gmail.com>
Hi,
On Thu, Nov 01, 2012 at 01:21:36AM +0530, Venkatraman S wrote:
> On Wed, Oct 31, 2012 at 5:56 PM, Felipe Balbi <balbi@ti.com> wrote:
> > Hi,
> >
> > On Wed, Oct 31, 2012 at 05:27:36PM +0530, Hebbar, Gururaja wrote:
> >> HSMMC IP on AM33xx need a special setting to handle High-speed cards.
> >> Other platforms like TI81xx, OMAP4 may need this as-well. This depends
> >> on the HSMMC IP timing closure done for the high speed cards.
> >>
> >> From AM335x TRM (SPRUH73F - 18.3.12 Output Signals Generation)
> >>
> >> The MMC/SD/SDIO output signals can be driven on either falling edge or
> >> rising edge depending on the SD_HCTL[2] HSPE bit. This feature allows
> >> to reach better timing performance, and thus to increase data transfer
> >> frequency.
> >>
> >> There are few pre-requisites for enabling the HSPE bit
> >> - Controller should support High-Speed-Enable Bit and
> >> - Controller should not be using DDR Mode and
> >> - Controller should advertise that it supports High Speed in
> >> capabilities register and
> >> - MMC/SD clock coming out of controller > 25MHz
> >>
> >> Note:
> >> The implementation reuses the output of calc_divisor() so as to reduce
> >> code addition.
> >>
> >> Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
> >
> > this looks good to my eyes, hopefully I haven't missed anything:
> >
> > Reviewed-by: Felipe Balbi <balbi@ti.com>
> >
>
> Except for the excessively verbose comments which are just duplicating the code,
> <Quote>
> >> + * Enable High-Speed Support
> >> + * Pre-Requisites
> >> + * - Controller should support High-Speed-Enable Bit
> >> + * - Controller should not be using DDR Mode
> >> + * - Controller should advertise that it supports High Speed
> >> + * in capabilities register
> >> + * - MMC/SD clock coming out of controller > 25MHz
> >> + */
> </Quote>
>
> I'm ok with this patch as well. I'm putting a few patches under test
> including this one,
> and will send it to Chris as part of that series.
> I'll strip out the above mentioned comments, unless there are any
> objections.
please don't. Detailing the pre-requisites for getting HSP mode working
isn't bad at all. Should someone decide to change the behavior and ends
up breaking it, the comment will help putting things back together.
my 2 cents, you've got the final decision though.
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121031/341e1607/attachment-0001.sig>
next prev parent reply other threads:[~2012-10-31 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 11:57 [PATCH V3] mmc: omap_hsmmc: Enable HSPE bit for high speed cards Hebbar, Gururaja
2012-10-31 12:26 ` Felipe Balbi
2012-10-31 19:51 ` Venkatraman S
2012-10-31 20:16 ` Felipe Balbi [this message]
2012-11-02 5:32 ` Hebbar, Gururaja
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=20121031201626.GA28784@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).