[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <153978998995.5275.238389804579286767@swboyd.mtv.corp.google.com>
Date: Wed, 17 Oct 2018 08:26:29 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: "kernel@...gutronix.de" <kernel@...gutronix.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mturquette@...libre.com" <mturquette@...libre.com>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
Anson Huang <anson.huang@....com>,
Fabio Estevam <fabio.estevam@....com>
Cc: dl-linux-imx <linux-imx@....com>
Subject: Re: [PATCH 1/2] clk: imx: cpu clock should be always critical
Quoting Anson Huang (2018-10-16 23:11:59)
> Add CLK_IS_CRITICAL flag for cpu clock type to
> make cpu clock use count correct, as cpu clock
> should be always critical.
>
> Signed-off-by: Anson Huang <Anson.Huang@....com>
> ---
Applied to clk-next
Powered by blists - more mailing lists