From: Arnd Bergmann <arnd@arndb.de>
To: zhangfei <zhangfei.gao@linaro.org>
Cc: Chris Ball <cjb@laptop.org>,
Mike Turquette <mturquette@linaro.org>,
Rob Herring <robherring2@gmail.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Seungwon Jeon <tgih.jun@samsung.com>,
Kumar Gala <galak@codeaurora.org>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
patches@linaro.org, devicetree@vger.kernel.org,
Heiko Stuebner <heiko@sntech.de>,
Dinh Nguyen <dinguyen@altera.com>
Subject: Re: [PATCH 2/3] mmc: dw_mmc: add dw_mmc-k3 for k3 platform
Date: Thu, 12 Dec 2013 21:40:08 +0100 [thread overview]
Message-ID: <201312122140.08566.arnd@arndb.de> (raw)
In-Reply-To: <52A9B9B4.3080105@linaro.org>
On Thursday 12 December 2013, zhangfei wrote:
> On 12/12/2013 04:12 AM, Arnd Bergmann wrote:
> > On Wednesday 11 December 2013, zhangfei wrote:
> >
> > But aren't the times fixed for each mode? Why do you need to specify them in
> > the DT? I would expect that the clock rates for each mode are set in the
> > MMC and SD specifications. When you call clk_set_rate(), it should normally
> > be enough to ask for the clock you actually want and let the clk subsystem
> > figure out how to set up the parents and multipliers on the way.
>
> Yes. that's will be perfect.
>
> However, currently this ip still has no such capability.
> Input rate for init are diferent for different controller, not the
> init 400K, some are 13M, others are 25M, since different clock source.
> This can be easily solved by clock-freq-init = <25000000>
> 2. There is maxmum limit, also can be easily solved by define CLK_MAX.
> 3. However some mode can not use the max speed from ios->clock
> for example UHS_SDR104_MAX_DTR 208000000 can not be used, only half may
> be reached, at least currently.
I don't fully understand the explanation, but if some of the other
people with interest in dw-mmc (I've added some more to Cc now) think
this makes sense, I'm fine with it too.
> How about this desc
>
> * clock-freq-table: should be the frequency (in Hz) array of the ciu
> clock
> in each supported timing.
>
> 1. CIU clock rate in HZ for MMC_TIMING_LEGACY mode
>
> 2. CIU clock rate in HZ for MMC_TIMING_MMC_HS mode
> 3. CIU clock rate in HZ for MMC_TIMING_SD_HS mode
> 4. CIU clock rate in HZ for MMC_TIMING_UHS_SDR12 mode
>
> 5. CIU clock rate in HZ for MMC_TIMING_UHS_SDR25 mode
>
> 6. CIU clock rate in HZ for MMC_TIMING_UHS_SDR50 mode
>
> 7. CIU clock rate in HZ for MMC_TIMING_UHS_SDR104 mode
>
> 8. CIU clock rate in HZ for MMC_TIMING_SD_HS mode
>
> 9. CIU clock rate in HZ for MMC_TIMING_MMC_HS200 mode
>
Yes, that is much better. but please avoid using Linux internal
identifiers (e.g. MMC_TIMING_LEGACY) and instead use the terminology from
the MMC and SD specs. Also 'Hz' is the official symbol for Hertz, not 'HZ'.
Arnd
next prev parent reply other threads:[~2013-12-12 20:40 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 14:02 [PATCH v4 0/3] mmc: dw_mmc: add dw_mmc-k3 Zhangfei Gao
2013-12-11 14:02 ` [PATCH 1/3] mmc: dw_mmc: use slot-gpio to handle cd pin 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
[not found] ` <201312112112.52746.arnd-r2nGTMty4D4@public.gmane.org>
2013-12-12 13:27 ` zhangfei
2013-12-12 14:13 ` Zhangfei Gao
2013-12-12 20:40 ` Arnd Bergmann [this message]
2013-12-13 2:57 ` zhangfei
2013-12-11 14:02 ` [PATCH 3/3] clk: hisilicon: add hi3620_mmc_clks Zhangfei Gao
2013-12-11 14:44 ` Arnd Bergmann
2013-12-11 15:40 ` zhangfei
-- strict thread matches above, loose matches on Subject: below --
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-28 14:34 [PATCH v6 0/3] mmc: dw_mmc: add dw_mmc-k3 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
2014-01-09 14:35 [PATCH v7 0/3] mmc: dw_mmc: add dw_mmc-k3 Zhangfei Gao
[not found] ` <1389278112-7099-1-git-send-email-zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
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
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
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=201312122140.08566.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@altera.com \
--cc=galak@codeaurora.org \
--cc=haojian.zhuang@linaro.org \
--cc=heiko@sntech.de \
--cc=jh80.chung@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=patches@linaro.org \
--cc=robherring2@gmail.com \
--cc=tgih.jun@samsung.com \
--cc=zhangfei.gao@linaro.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).