[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a017be90-4538-ecbd-64dd-a988ec8f80ce@oracle.com>
Date: Thu, 10 Sep 2020 15:41:08 -0700
From: santosh.shilimkar@...cle.com
To: Stephen Boyd <sboyd@...nel.org>, Tero Kristo <t-kristo@...com>,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
mturquette@...libre.com, ssantosh@...nel.org
Subject: Re: [PATCH 0/3] clk: keystone: some minor fixes
On 9/10/20 2:29 PM, Stephen Boyd wrote:
> Quoting santosh.shilimkar@...cle.com (2020-09-08 10:19:32)
>>
>>
>> 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 ?
>
> Sure. I assume this is -next material and not critical fixes.
>
Yep.
Powered by blists - more mailing lists