linux-kernel - Re: [PATCH 0/3] clk: keystone: some minor fixes

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <8a594a9d-8e10-6e01-908c-8e59da1d7fbe@oracle.com>
Date:   Tue, 8 Sep 2020 10:19:32 -0700
From:   santosh.shilimkar@...cle.com
To:     Tero Kristo <t-kristo@...com>, linux-clk@...r.kernel.org,
        ssantosh@...nel.org, linux-kernel@...r.kernel.org,
        sboyd@...nel.org, mturquette@...libre.com
Subject: Re: [PATCH 0/3] clk: keystone: some minor fixes



On 9/7/20 1:57 AM, Tero Kristo wrote:
> Hi Santosh,
> 
> This series contains a few fixes for the TI SCI clock driver.
> - Patch #1 is a clear bug fix, where we missed to parse assigned-clock
>    data properly to detect which clocks are in use on the SoC.
> - Patch #2 is a performance improvement patch which avoids some
>    unnecessary round trips to firmware side while setting clock
>    frequency.
> - Patch #3 fixes some issues with set_rate passed to firmware, where the
>    parameters are too strict; namely, firmware fails to handle some cases
>    properly if min,tgt,max values for a clock rate are exactly the same
>    value. Yeah, the firmware is quite weird here but nothing much else we
>    can do from kernel side other than this....
> 
Looks fine to me Tero.

Acked-by: Santosh Shilimkar <ssantosh@...nel.org>


Hi Stephen, Mike,
Can you please pick these fixes via clk tree ?