linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tgih.jun@samsung.com (Seungwon Jeon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] mmc: dw_mmc: add dw_mmc-k3 for k3 platform
Date: Mon, 13 Jan 2014 11:09:24 +0900	[thread overview]
Message-ID: <001501cf1004$7b1f34b0$715d9e10$%jun@samsung.com> (raw)
In-Reply-To: <52CFFFDA.8050108@linaro.org>

On Fri, January 10, 2014, Zhangfei Gao wrote:
> On 01/10/2014 09:39 PM, Seungwon Jeon wrote:
> >> +static void dw_mci_k3_set_ios(struct dw_mci *host, struct mmc_ios *ios)
> >> +{
> >> +	struct dw_mci_k3_priv_data *priv = host->priv;
> >> +	u32 rate = priv->clk_table[ios->timing];
> >
> > First, sorry for quick review even though your effort.
> > But I still worry about this change.
> > Currently k3 host's clock table depends on value number of SD/MMC mode value.
> > It seems close to identifier for eachg mode. I think it's not good way to use as table's index.
> > Can you modify to mmc_clk_determine_rate() in your another patch-set?
> > I guess required actual target rate could be determined depending on ios->clock.
> >
> 
> No, it can not get input clock source rate simply from ios->clock, also
> requied info like which controller, which mode etc.
> Here is setting clock source rate, not the working clock rate.
> 
> For example, emmc init clock source rate is 13M, while sd init clock
> source is 25M, it can not simply get such info from ios->clock.
> And for HS200, emmc may have to set clock source rate to 104M since the
> controller limitation and can not work stable as 208M.

Yes, clock table is source clock rate, not actual working clock rate.
I was not saying that 'ios->clock' would be used for source clock directly.
I meant that you can adjust the source clock rate depending on 'ios->clock'.
You've already done with clock table similarly in mmc_clk_determine_rate().

For example, in case of HS200, 'ios->clock' will be passed with 200MHz.
And then, mmc_clk_determine_rate() can set the 'rate & best' to 100000000 and 720000000 respectively.
Also, 'ios->clock' with 400KHz or less may be passed for init clock.
If clock id is HI3620_SD_CIUCLK, 'rate & best' can be selected with 13000000 and 26000000.
If not and it's case of MMC,  'rate & best' can be selected with 25000000 and 180000000.
If it should be considered with other conditions, please let me know.

Thanks,
Seungwon Jeon

  reply	other threads:[~2014-01-13  2:09 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 14:35 [PATCH v7 0/3] mmc: dw_mmc: add dw_mmc-k3 Zhangfei Gao
2014-01-09 14:35 ` [PATCH 1/3] mmc: dw_mmc: use slot-gpio to handle cd pin Zhangfei Gao
2014-01-09 14:38   ` Arnd Bergmann
2014-01-14 15:58   ` Kevin Hilman
2014-01-14 17:23     ` Olof Johansson
2014-01-15  1:09       ` zhangfei
2014-01-15  5:16         ` zhangfei
2014-01-15  7:15     ` [PATCH] mmc: dw_mmc: fix dw_mci_get_cd Zhangfei Gao
2014-01-15  7:31       ` zhangfei
2014-01-15 10:07       ` Zhangfei Gao
2014-01-15 11:58         ` Seungwon Jeon
2014-01-15 12:10           ` zhangfei
2014-01-15 12:26             ` Seungwon Jeon
2014-01-15 13:56               ` zhangfei
2014-01-15 13:59                 ` Arnd Bergmann
2014-01-15 14:20                   ` Arnd Bergmann
2014-01-15 15:36                     ` zhangfei
2014-01-15 16:01                   ` Russell King - ARM Linux
2014-01-15 16:07                     ` Arnd Bergmann
2014-01-15 16:22                       ` Russell King - ARM Linux
2014-01-16  2:10                         ` zhangfei
2014-01-16 11:12                         ` Arnd Bergmann
2014-01-16 11:25                           ` Russell King - ARM Linux
2014-01-15 14:38                 ` Seungwon Jeon
2014-01-15 15:32                   ` zhangfei
2014-01-15 15:51                     ` Zhangfei Gao
2014-01-15 15:59                       ` Russell King - ARM Linux
2014-01-15 15:54                     ` Arnd Bergmann
2014-01-09 14:35 ` [PATCH 2/3] mmc: dw_mmc: add dw_mmc-k3 for k3 platform Zhangfei Gao
2014-01-09 14:45   ` Arnd Bergmann
2014-01-10 13:39   ` Seungwon Jeon
2014-01-10 14:12     ` zhangfei
2014-01-13  2:09       ` Seungwon Jeon [this message]
2014-01-13  2:37         ` zhangfei
2014-01-13  5:32           ` Seungwon Jeon
2014-01-13  8:30             ` zhangfei
2014-01-14  9:38               ` Seungwon Jeon
2014-01-14  9:47                 ` zhangfei
2014-01-09 14:35 ` [PATCH 3/3] clk: hisilicon: add hi3620_mmc_clks Zhangfei Gao
2014-01-09 14:38   ` Arnd Bergmann
2014-01-10  3:41 ` [PATCH v7 0/3] mmc: dw_mmc: add dw_mmc-k3 Jaehoon Chung
2014-01-12 16:35 ` Chris Ball
2014-01-13  1:00   ` Zhangfei Gao
  -- strict thread matches above, loose matches on Subject: below --
2013-12-28 14:34 [PATCH v6 " Zhangfei Gao
2013-12-28 14:34 ` [PATCH 2/3] mmc: dw_mmc: add dw_mmc-k3 for k3 platform Zhangfei Gao
2013-12-29 21:05   ` Arnd Bergmann
2013-12-29 23:55     ` Jaehoon Chung
2013-12-30  2:32       ` Zhangfei Gao
2013-12-30 17:19         ` zhangfei
2013-12-30 20:27           ` Arnd Bergmann
2013-12-31  4:43             ` zhangfei
2013-12-31 13:20     ` Gerhard Sittig
2014-01-02  2:19       ` zhangfei
2014-01-02  3:07   ` Zhangfei Gao
2013-12-14  2:12 [PATCH v5 0/3] mmc: dw_mmc: add dw_mmc-k3 Zhangfei Gao
2013-12-14  2:12 ` [PATCH 2/3] mmc: dw_mmc: add dw_mmc-k3 for k3 platform Zhangfei Gao
2013-12-16  3:50   ` Seungwon Jeon
2013-12-16  5:05     ` zhangfei
2013-12-16  7:29       ` Seungwon Jeon
2013-12-16  8:08         ` zhangfei
2013-12-16  9:18           ` Seungwon Jeon
2013-12-16 11:07             ` zhangfei
2013-12-16 13:12   ` Zhangfei Gao
2013-12-20  2:31     ` zhangfei
2013-12-26  4:33     ` Jaehoon Chung
2013-12-27  6:13       ` zhangfei
2013-12-11 14:02 [PATCH v4 0/3] mmc: dw_mmc: add dw_mmc-k3 Zhangfei Gao
2013-12-11 14:02 ` [PATCH 2/3] mmc: dw_mmc: add dw_mmc-k3 for k3 platform Zhangfei Gao
2013-12-11 14:49   ` Arnd Bergmann
2013-12-11 15:36     ` zhangfei
2013-12-11 15:53       ` zhangfei
2013-12-11 20:12       ` Arnd Bergmann
2013-12-12 13:27         ` zhangfei
2013-12-12 14:13           ` Zhangfei Gao
2013-12-12 20:40           ` Arnd Bergmann
2013-12-13  2:57             ` zhangfei

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='001501cf1004$7b1f34b0$715d9e10$%jun@samsung.com' \
    --to=tgih.jun@samsung.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).