From: santosh.shilimkar@oracle.com
To: Tero Kristo <t-kristo@ti.com>,
linux-clk@vger.kernel.org, ssantosh@kernel.org,
linux-kernel@vger.kernel.org, sboyd@kernel.org,
mturquette@baylibre.com
Subject: Re: [PATCH 0/3] clk: keystone: some minor fixes
Date: Tue, 8 Sep 2020 10:19:32 -0700 [thread overview]
Message-ID: <8a594a9d-8e10-6e01-908c-8e59da1d7fbe@oracle.com> (raw)
In-Reply-To: <20200907085740.1083-1-t-kristo@ti.com>
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 ?
next prev parent reply other threads:[~2020-09-08 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 8:57 [PATCH 0/3] clk: keystone: some minor fixes 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 ` santosh.shilimkar [this message]
2020-09-10 21:29 ` [PATCH 0/3] clk: keystone: some minor fixes Stephen Boyd
2020-09-10 22:41 ` santosh.shilimkar
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=8a594a9d-8e10-6e01-908c-8e59da1d7fbe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.