Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <8a594a9d-8e10-6e01-908c-8e59da1d7fbe@oracle.com>
References: <20200907085740.1083-1-t-kristo@ti.com> <8a594a9d-8e10-6e01-908c-8e59da1d7fbe@oracle.com>
Subject: Re: [PATCH 0/3] clk: keystone: some minor fixes
From:   Stephen Boyd <sboyd@kernel.org>
To:     Tero Kristo <t-kristo@ti.com>, linux-clk@vger.kernel.org,
        linux-kernel@vger.kernel.org, mturquette@baylibre.com,
        santosh.shilimkar@oracle.com, ssantosh@kernel.org
Date:   Thu, 10 Sep 2020 14:29:13 -0700
Message-ID: <159977335346.2295844.11165311759086345858@swboyd.mtv.corp.google.com>
User-Agent: alot/0.9.1
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Quoting santosh.shilimkar@oracle.com (2020-09-08 10:19:32)
>=20
>=20
> On 9/7/20 1:57 AM, Tero Kristo wrote:
> > Hi Santosh,
> >=20
> > 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 cas=
es
> >    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....
> >=20
> Looks fine to me Tero.
>=20
> Acked-by: Santosh Shilimkar <ssantosh@kernel.org>
>=20
>=20
> Hi Stephen, Mike,
> Can you please pick these fixes via clk tree ?

Sure. I assume this is -next material and not critical fixes.