mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: santosh.shilimkar@oracle.com
To: Stephen Boyd <sboyd@kernel.org>, Tero Kristo <t-kristo@ti.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	mturquette@baylibre.com, ssantosh@kernel.org
Subject: Re: [PATCH 0/3] clk: keystone: some minor fixes
Date: Thu, 10 Sep 2020 15:41:08 -0700	[thread overview]
Message-ID: <a017be90-4538-ecbd-64dd-a988ec8f80ce@oracle.com> (raw)
In-Reply-To: <159977335346.2295844.11165311759086345858@swboyd.mtv.corp.google.com>



On 9/10/20 2:29 PM, Stephen Boyd wrote:
> Quoting santosh.shilimkar@oracle.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@kernel.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.

      reply	other threads:[~2020-09-10 22:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07  8:57 Tero Kristo
2020-09-07  8:57 ` [PATCH 1/3] clk: keystone: sci-clk: fix parsing assigned-clock data during probe Tero Kristo
2020-09-22 19:59   ` Stephen Boyd
2020-09-07  8:57 ` [PATCH 2/3] clk: keystone: sci-clk: cache results of last query rate operation Tero Kristo
2020-09-22 19:59   ` Stephen Boyd
2020-09-07  8:57 ` [PATCH 3/3] clk: keystone: sci-clk: add 10% slack to set_rate Tero Kristo
2020-09-22 19:59   ` Stephen Boyd
2020-09-08 17:19 ` [PATCH 0/3] clk: keystone: some minor fixes santosh.shilimkar
2020-09-10 21:29   ` Stephen Boyd
2020-09-10 22:41     ` santosh.shilimkar [this message]

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=a017be90-4538-ecbd-64dd-a988ec8f80ce@oracle.com \
    --to=santosh.shilimkar@oracle.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=t-kristo@ti.com \
    /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

all inboxes | Powered by JetHome®