[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190123220545.GD179701@dtor-ws>
Date: Wed, 23 Jan 2019 14:05:45 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Lubomir Rintel <lkundrak@...sk>
Cc: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
linux-input@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org
Subject: Re: [PATCH 1/3] Revert "Input: olpc_apsp - enable the SP clock"
On Mon, Jan 21, 2019 at 07:22:54AM +0100, Lubomir Rintel wrote:
> Turns out this is not such a great idea. Once the SP clock is disabled,
> it's not sufficient to just enable in order to bring the SP core back up.
>
> It seems that the kernel has no business managing this clock. Just let
> the firmware keep it enabled.
>
> This reverts commit ed22cee91a88c47e564478b012fdbcb079653499.
>
> Link: https://lore.kernel.org/lkml/154783267051.169631.3197836544646625747@swboyd.mtv.corp.google.com/
> Signed-off-by: Lubomir Rintel <lkundrak@...sk>
OK, as clock folks say it is a bad idea it must be so. Merge though clk
tree?
Acked-by: Dmitry Torokhov <dmitry.torokhov@...il.com>
Thanks.
--
Dmitry
Powered by blists - more mailing lists