From: Simon Horman <horms@verge.net.au>
To: "Brandt, Chris" <Chris.Brandt@renesas.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
Chris Ball <cjb@laptop.org>, Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH] mmc: sh_mmcif: mmc->f_max heuristic
Date: Fri, 22 Jun 2012 08:30:10 +0900 [thread overview]
Message-ID: <20120621233009.GD7034@verge.net.au> (raw)
In-Reply-To: <A389CA2909F7E548A28A6A30A9446C0903651FAF81@REAMBX.NA.RTA>
On Thu, Jun 21, 2012 at 07:11:42AM -0700, Brandt, Chris wrote:
> > At least for the sh7757 and sh7372.
> Also for the sh7724 (ie, only the sh7757 can run at full bus speed by setting CLKDIV=0xF which no other part can....yet)
Thanks.
> But, with this new patch applied:
>
> > if (!ret) {
> > host->clk = clk_get_rate(host->hclk);
> > - host->mmc->f_max = host->clk / 2;
> > + host->mmc->f_max = p->sup_pclk ? host->clk : host->clk / 2;
> > host->mmc->f_min = host->clk / 512;
> > }
>
> Then there's no need to check for p->sup_pclk in sh_mmcif_clock_control() because if (clk == host->clk) then p->sup_pclk can be assumed to be set.
>
> - if (p->sup_pclk && clk == host->clk)
> + if (clk == host->clk)
> sh_mmcif_bitset(host, MMCIF_CE_CLK_CTRL, CLK_SUP_PCLK);
> else
> sh_mmcif_bitset(host, MMCIF_CE_CLK_CTRL, CLK_CLEAR &
> ((fls(DIV_ROUND_UP(host->clk,
> clk) - 1) - 1) << 16));
>
>
> But, that's probably more along the lines of driver cleanup I guess.
Thanks, I'll add that.
next prev parent reply other threads:[~2012-06-21 23:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 5:58 [PATCH] mmc: sh_mmcif: mmc->f_max heuristic Simon Horman
2012-06-20 6:49 ` Guennadi Liakhovetski
2012-06-20 7:02 ` Simon Horman
2012-06-20 14:56 ` Brandt, Chris
2012-06-21 0:47 ` Simon Horman
2012-06-21 14:11 ` Brandt, Chris
2012-06-21 23:30 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-21 23:49 Simon Horman
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=20120621233009.GD7034@verge.net.au \
--to=horms@verge.net.au \
--cc=Chris.Brandt@renesas.com \
--cc=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@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