From: Simon Horman <horms@verge.net.au>
To: "Michał Mirosław" <mirqus@gmail.com>
Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
Yusuke Goda <yusuke.goda.sx@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Chris Ball <cjb@laptop.org>, Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH 3/3 v2] sh, mmc: Use defines when setting CE_CLK_CTRL
Date: Sun, 28 Nov 2010 06:17:36 +0900 [thread overview]
Message-ID: <20101127211736.GC2090@verge.net.au> (raw)
In-Reply-To: <AANLkTi=zKbNhVz=Bh7ytRezobsnxeWE49mJcAS=rJ4Oq@mail.gmail.com>
On Sat, Nov 27, 2010 at 12:54:41PM +0100, Michał Mirosław wrote:
> 2010/11/27 Simon Horman <horms@verge.net.au>:
> > The 16-19th bits of CE_CLK_CTRL set the
> > MMC clock frequency.
> >
> > Cc: Yusuke Goda <yusuke.goda.sx@renesas.com>
> > Cc: Magnus Damm <magnus.damm@gmail.com>
> > Signed-off-by: Simon Horman <horms@verge.net.au>
> > ---
> > include/linux/mmc/sh_mmcif.h | 17 +++++++++--------
> > 1 files changed, 9 insertions(+), 8 deletions(-)
> >
> > diff --git a/include/linux/mmc/sh_mmcif.h b/include/linux/mmc/sh_mmcif.h
> > index 519a2cd..44fc534 100644
> > --- a/include/linux/mmc/sh_mmcif.h
> > +++ b/include/linux/mmc/sh_mmcif.h
> > @@ -77,6 +77,9 @@ struct sh_mmcif_plat_data {
> > #define CLK_ENABLE (1 << 24) /* 1: output mmc clock */
> > #define CLK_CLEAR ((1 << 19) | (1 << 18) | (1 << 17) | (1 << 16))
> > #define CLK_SUP_PCLK ((1 << 19) | (1 << 18) | (1 << 17) | (1 << 16))
> > +#define CLKDIV_4 (1<<16) /* mmc clock frequency.
> > + * n: bus clock/(2^(n+1)) */
> > +#define CLKDIV_256 (7<<16) /* mmc clock frequency. (see above) */
> > #define SRSPTO_256 ((1 << 13) | (0 << 12)) /* resp timeout */
> > #define SRBSYTO_29 ((1 << 11) | (1 << 10) | \
> > (1 << 9) | (1 << 8)) /* resp busy timeout */
> [...]
>
> Maybe zero is a valid value here meaning CLKDIV = 2.
Hi Michał,
Yes, it is. I intended to provide defines only for values that are used.
But I can provide all the valid values (there are only 9) it that
makes thing clearer. Or perhaps change the comment to:
/* CLKDIV_n
* mmc clock frequency.
* n: bus clock/(2^(m+1))
* where 0 <= m <= 8 */
next prev parent reply other threads:[~2010-11-27 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 23:02 [PATCH 1/3] sh, mmc: Make mmcif_update_progress static inline Simon Horman
2010-11-26 23:02 ` [PATCH 2/3] mmc, sh: Correct value for reset Simon Horman
2010-11-26 23:02 ` [PATCH 3/3] sh, mmc: Use defines when setting CE_CLK_CTRL Simon Horman
2010-11-27 0:01 ` Simon Horman
2010-11-27 0:11 ` [PATCH 3/3 v2] " Simon Horman
2010-11-27 11:54 ` Michał Mirosław
2010-11-27 21:17 ` Simon Horman [this message]
2010-11-29 3:55 ` [PATCH 1/3] sh, mmc: Make mmcif_update_progress static inline Paul Mundt
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=20101127211736.GC2090@verge.net.au \
--to=horms@verge.net.au \
--cc=cjb@laptop.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lethal@linux-sh.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mirqus@gmail.com \
--cc=yusuke.goda.sx@renesas.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