lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 8 Jan 2021 13:21:00 -0800
From:   Doug Anderson <>
To:     Ulf Hansson <>,
        Adrian Hunter <>
Cc:     Taniya Das <>,
        Veerabhadrarao Badiganti <>,
        Stephen Boyd <>,
        Bjorn Andersson <>,
        Andy Gross <>,
        linux-arm-msm <>,
        LKML <>,
        Linux MMC List <>
Subject: Re: [PATCH v5 1/2] mmc: sdhci-msm: Warn about overclocking SD/MMC


On Mon, Dec 14, 2020 at 9:23 AM Douglas Anderson <> wrote:
> As talked about in commit 5e4b7e82d497 ("clk: qcom: gcc-sdm845: Use
> floor ops for sdcc clks"), most clocks handled by the Qualcomm clock
> drivers are rounded _up_ by default instead of down.  We should make
> sure SD/MMC clocks are always rounded down in the clock drivers.
> Let's add a warning in the Qualcomm SDHCI driver to help catch the
> problem.
> This would have saved a bunch of time [1].
> NOTE: this doesn't actually fix any problems, it just makes it obvious
> to devs that there is a problem and that should be an indication to
> fix the clock driver.
> [1]
> Suggested-by: Stephen Boyd <>
> Signed-off-by: Douglas Anderson <>
> Reviewed-by: Stephen Boyd <>
> Reviewed-by: Bjorn Andersson <>
> ---
> (no changes since v4)
> Changes in v4:
> - Emphasize in the commit message that this itself doesn't fix anything.
> Changes in v3:
> - Proper printf format code.
> Changes in v2:
> - Store rate in unsigned long, not unsigned int.
> - Reuse the clk_get_rate() in the later print.
>  drivers/mmc/host/sdhci-msm.c | 15 +++++++++++++--
>  1 file changed, 13 insertions(+), 2 deletions(-)

Is there anything you need me to do for this patch and the next one?
They are both reviewed / Acked and hopefully have sat around long
enough that folks who took a long holiday break had a chance to shout
if they were going to, so I think they could land.  ;-)  Please yell
if there's something you need me to do, or feel free to tell me to sit
quietly and be patient.



Powered by blists - more mailing lists