[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <155562436407.15276.5265889537123283982@swboyd.mtv.corp.google.com>
Date: Thu, 18 Apr 2019 14:52:44 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Leo Yan <leo.yan@...aro.org>,
Michael Turquette <mturquette@...libre.com>,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: stable@...r.kernel.org, Zhong Kaihua <zhongkaihua@...wei.com>,
John Stultz <john.stultz@...aro.org>,
Zhangfei Gao <zhangfei.gao@...aro.org>
Subject: Re: [PATCH v2] clk: hi3660: Mark clk_gate_ufs_subsys as critical
Quoting Leo Yan (2019-04-17 22:33:39)
> Hi Michael, Stephen,
>
> On Wed, Mar 20, 2019 at 06:05:08PM +0800, Leo Yan wrote:
> > clk_gate_ufs_subsys is a system bus clock, turning off it will
> > introduce lockup issue during system suspend flow. Let's mark
> > clk_gate_ufs_subsys as critical clock, thus keeps it on during
> > system suspend and resume.
>
> Could you pick up this patch? Or should I resend it?
>
I can pick it up. Is it critical or can it wait for v5.2?
Powered by blists - more mailing lists