From: Matt Fleming <matt@console-pimps.org>
To: David Vrabel <david.vrabel@csr.com>
Cc: zhangfei gao <zhangfei.gao@gmail.com>,
linux-mmc@vger.kernel.org,
Anton Vorontsov <cbouatmailru@gmail.com>,
Ben Dooks <ben-linux@fluff.org>,
Wolfram Sang <w.sang@pengutronix.de>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Eric Miao <eric.y.miao@gmail.com>
Subject: Re: [patch v2 1/1]sdhci support 10 bit divided clock Mode for spec 3.0
Date: Mon, 16 Aug 2010 20:27:48 +0100 [thread overview]
Message-ID: <20100816192748.GC6263@console-pimps.org> (raw)
In-Reply-To: <4C698956.101@csr.com>
On Mon, Aug 16, 2010 at 07:54:14PM +0100, David Vrabel wrote:
> Matt Fleming wrote:
> >
> > Sorry, I did mean to reply to this sooner but I've been travelling. Yeah
> > David, you're right. Zhangfei, have you confused the Programmable Clock
> > Mode in the 3.00 spec here with 10-bit Divided Clock Mode?
> >
> > Both 8-bit Divided Clock Mode and 10-bit Divided Clock Mode require the
> > divisor to be a power of two.
>
> The power-of-two requirement only applies to 2.00 controller. From
> section 2.2.14 of the spec.
>
> "(2) 10-bit Divided Clock Mode
> Host Controller Version 3.00 supports this mandatory mode instead of
> the 8-bit Divided Clock Mode. The length of divider is extended to
> 10bits and all divider values shall be supported."
>
> 3.00 dividers can be any multiple of two.
Yep, you're right. I misread the spec. My bad.
next prev parent reply other threads:[~2010-08-16 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 13:41 [patch v2 1/1]sdhci support 10 bit divided clock Mode for spec 3.0 zhangfei gao
2010-08-16 13:48 ` zhangfei gao
2010-08-16 16:07 ` David Vrabel
2010-08-16 18:27 ` Matt Fleming
2010-08-16 18:54 ` David Vrabel
2010-08-16 19:27 ` Matt Fleming [this message]
2010-08-17 11:08 ` zhangfei gao
2010-08-17 11:32 ` David Vrabel
2010-08-17 11:42 ` Matt Fleming
2010-09-14 13:12 ` 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=20100816192748.GC6263@console-pimps.org \
--to=matt@console-pimps.org \
--cc=ben-linux@fluff.org \
--cc=cbouatmailru@gmail.com \
--cc=david.vrabel@csr.com \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=w.sang@pengutronix.de \
--cc=zhangfei.gao@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 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.