From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RESEND PATCH v3 1/2] mmc: rockchip_sdhci: add clock init for mmc
Date: Thu, 29 Dec 2016 08:53:51 +0800 [thread overview]
Message-ID: <58645E9F.60300@rock-chips.com> (raw)
In-Reply-To: <50d2fa0b-ae37-c613-983e-6b8917bc4a8a@herbrechtsmeier.net>
Hi Stefan,
Thanks for your review comment.
On 12/29/2016 02:35 AM, Stefan Herbrechtsmeier wrote:
> Hi,
>
> Am 28.12.2016 um 12:01 schrieb Jaehoon Chung:
>> On 12/28/2016 12:32 PM, Kever Yang wrote:
>>> Init the clock rate to max-frequency from dts with clock driver api.
>>>
>>> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
>> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
> This is an incorrect use of the max-frequency property.
>
> The max-frequency value limit the output clock of the mmc interface
> and depends on the controller, circuit (level shifter), board and so
> on. It doesn't represents the clock frequency of the controller.
>
> The clock setup inside the clock framework should use the
> assigned-clock-rates property. The mmc driver should only enable the
> clock and pass the clock rate together with the max-frequency to the
> mmc framework.
I'm not good at mmc controller and driver framework, but seems that the
sdhci core treats the max-frequency as the clock input from clock
module, right?
What if the mmc controller max-frequency is not equal to the clock
module output which is possible? Does kernel deal with this, and how.
Thanks,
- Kever
>
> Regards,
> Stefan
>
>
>
>
next prev parent reply other threads:[~2016-12-29 0:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161228033846epcas5p301db09515cbe274b1c3244aa7e5af2de@epcas5p3.samsung.com>
2016-12-28 3:32 ` [U-Boot] [RESEND PATCH v3 1/2] mmc: rockchip_sdhci: add clock init for mmc Kever Yang
2016-12-28 3:32 ` [U-Boot] [RESEND PATCH v3 2/2] dts: arm64: rk3399: add max-frequency for sdhci Kever Yang
2016-12-28 11:01 ` Jaehoon Chung
2017-01-12 5:08 ` Simon Glass
2016-12-28 11:01 ` [U-Boot] [RESEND PATCH v3 1/2] mmc: rockchip_sdhci: add clock init for mmc Jaehoon Chung
2016-12-28 18:35 ` Stefan Herbrechtsmeier
2016-12-29 0:53 ` Kever Yang [this message]
2016-12-29 7:44 ` Jaehoon Chung
2016-12-29 15:41 ` Stefan Herbrechtsmeier
2016-12-30 0:13 ` Jaehoon Chung
2016-12-30 15:07 ` Stefan Herbrechtsmeier
2017-01-02 1:29 ` Jaehoon Chung
2017-01-02 16:59 ` Stefan Herbrechtsmeier
2017-01-12 5:08 ` Simon Glass
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=58645E9F.60300@rock-chips.com \
--to=kever.yang@rock-chips.com \
--cc=u-boot@lists.denx.de \
/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