From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jaehoon Chung <jh80.chung@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Kevin Hilman <khilman@baylibre.com>
Cc: Carlo Caione <carlo@caione.org>, linux-mmc@vger.kernel.org
Subject: Re: [PATCH 1/9] mmc: meson-gx: fix setting f_min
Date: Wed, 1 Feb 2017 21:14:00 +0100 [thread overview]
Message-ID: <6085c3ea-0a85-458d-bf15-8dcdd2d83186@gmail.com> (raw)
In-Reply-To: <1e55512d-1dc3-bd57-82e1-888553ab3a9e@samsung.com>
Am 01.02.2017 um 12:49 schrieb Jaehoon Chung:
> On 02/01/2017 05:57 AM, Heiner Kallweit wrote:
>> Currently f_min is set to 4 MHz whilst the comment states 400 MHz.
>> I think the itention is to set f_min to 400 kHz.
>> Change value and comment accordingly.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>> drivers/mmc/host/meson-gx-mmc.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/mmc/host/meson-gx-mmc.c b/drivers/mmc/host/meson-gx-mmc.c
>> index 5eca88bc..da3cce31 100644
>> --- a/drivers/mmc/host/meson-gx-mmc.c
>> +++ b/drivers/mmc/host/meson-gx-mmc.c
>> @@ -268,7 +268,7 @@ static int meson_mmc_clk_init(struct meson_host *host)
>> if (f_min != UINT_MAX)
>> f_min = DIV_ROUND_UP(CLK_SRC_XTAL_RATE, CLK_DIV_MAX);
>> else
>> - f_min = 4000000; /* default min: 400 MHz */
>> + f_min = 400000; /* default min: 400 kHz */
>
> I'm not sure but f_min can be 100KHz by default, not 400KHz.
> Because mmc-core should be try to find frequency from 400KHz to "f_min" value.
>
Actually I wonder how we can ever reach this part of the if clause.
If at least one parent clock is defined and we can get its clock rate
then f_min != UINT_MAX.
Can we think of a case where no parent clock is defined?
And would it make sense at all to proceed in this case?
> Best Regards,
> Jaehoon Chung
>
>> host->mmc->f_min = f_min;
>>
>> /* create the mux */
>>
>
>
next prev parent reply other threads:[~2017-02-01 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170131210651epcas5p37ca57e71ecbab37efe9b0227e4449d30@epcas5p3.samsung.com>
2017-01-31 20:57 ` [PATCH 1/9] mmc: meson-gx: fix setting f_min Heiner Kallweit
2017-02-01 11:49 ` Jaehoon Chung
2017-02-01 20:14 ` Heiner Kallweit [this message]
2017-02-03 13:58 ` Kevin Hilman
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=6085c3ea-0a85-458d-bf15-8dcdd2d83186@gmail.com \
--to=hkallweit1@gmail.com \
--cc=carlo@caione.org \
--cc=jh80.chung@samsung.com \
--cc=khilman@baylibre.com \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@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