From: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] clk: rcar-h2: fix sd0/sd1 divisor table
Date: Thu, 06 Feb 2014 00:43:03 +0000 [thread overview]
Message-ID: <87txcdul4b.wl%kuninori.morimoto.gx@gmail.com> (raw)
In-Reply-To: <2298259.CqC51XrMZM@avalon>
Hi all
> > >>> The clk_div_table for cpg_sd01_div_table[] concurs with the manual
> > >>> but not with values found in the device itself (which are also the
> > >>> same as the ones in arch/arm/mach-shmobile/clock-r8a7790.c).
> > >>>
> > >>> Update the clk-rcar-gen2.c driver to have the same table as the one
> > >>> used by the mach-shmobile driver which work once further issues are
> > >>> fixed in the clk-rcar-gen2.c driver.
> > >>>
> > >>> Part of the fix for the following error where the driver reports the
> > >>>
> > >>> output as 1MHz but is really 97.5MHz:
> > >>> sh_mobile_sdhi ee100000.sd: mmc0 base at 0xee100000 clock rate 1
> > >>> MHz
> > >>>
> > >>> [ben.dooks@codethink.co.uk: updated patch description]
> > >>> Signed-off-by: William Towle <william.towle@codethink.co.uk>
> > >>> Reviewed-by: Ben Dooks <ben.dooks@codethink.co.uk>
(snip)
> > >>> static const struct clk_div_table cpg_sd01_div_table[] = {
> > >>> + { 0, 2 }, { 1, 3 }, { 2, 4 }, { 3, 6 },
> > >>> + { 4, 8 },
> > >>>
> > >>> { 5, 12 }, { 6, 16 }, { 7, 18 }, { 8, 24 },
> > >>> { 10, 36 }, { 11, 48 }, { 12, 10 }, { 0, 0 },
(snip)
> > > I would like feedback from Renesas on this issue if possible. I can
> > > have a quick try at setting the clock value to 10 in u-boot and scope
> > > it out and see what happens.
> > >
> > > Magnus or Morimoto-san, is there a chance this could be reviewed by
> > > someone in Renesas who has knowledge of the hardware block?
> > >
> > > [PS, added Kuninori Morimoto to this[
> >
> > I got William to do a quick test with the following u-boot command
> > mw.l 0xE6150074 0xCCC
> >
> > sdhi0 showed 156MHz output, and it seemed to work. So there is a
> > distinct possibility that the sdh clock also supports setting 12
> > for a /10
>
> Thank you for trying it out. I'd like feedback from Renesas as well, assuming
> we don't get a "don't do that or it will cause the universe to collapse -
> woops, too late" nack, let's respin this patch and merge the two tables
> instead.
I ask it to Renesas HW team.
Please wait
Best regards
---
Kuninori Morimoto
next prev parent reply other threads:[~2014-02-06 0:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 18:17 Clock divisor/parent settings changes William Towle
2014-02-04 18:17 ` [PATCH 1/3] clk: rcar-h2: fix sd0/sd1 divisor table William Towle
2014-02-05 10:56 ` Laurent Pinchart
2014-02-05 11:55 ` Ben Dooks
2014-02-05 12:41 ` Ben Dooks
2014-02-05 13:07 ` Laurent Pinchart
2014-02-06 0:43 ` Kuninori Morimoto [this message]
2014-02-07 6:43 ` Kuninori Morimoto
2014-02-07 9:55 ` Ben Dooks
2014-02-04 18:17 ` [PATCH 2/3] ARM: shmobile: r8a7790: specify multiple parents for cpg_clks William Towle
2014-02-05 9:15 ` [Linux-kernel] " Ben Dooks
2014-02-05 10:32 ` Laurent Pinchart
2014-02-05 10:36 ` Ben Dooks
2014-02-05 10:57 ` Laurent Pinchart
2014-02-04 18:17 ` [PATCH 3/3] clk: shmobile: handle multiple parent clocks for cpg clocks William Towle
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=87txcdul4b.wl%kuninori.morimoto.gx@gmail.com \
--to=kuninori.morimoto.gx@gmail.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).