RE: [PATCH] clk: imx: Mark the snvs clock as critical by default

From: Jacky Bai <ping.bai@nxp.com>
To: Stephen Boyd <sboyd@kernel.org>, Abel Vesa <abel.vesa@nxp.com>,
	"mturquette@baylibre.com" <mturquette@baylibre.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>
Cc: "festevam@gmail.com" <festevam@gmail.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Subject: RE: [PATCH] clk: imx: Mark the snvs clock as critical by default
Date: Thu, 10 Mar 2022 00:54:29 +0000	[thread overview]
Message-ID: <DB9PR04MB8412630A41E49E66EB5FFB04870B9@DB9PR04MB8412.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20220309184637.31E2CC340F4@smtp.kernel.org>

> Subject: Re: [PATCH] clk: imx: Mark the snvs clock as critical by default
> 
> Quoting Jacky Bai (2022-03-08 02:17:14)
> > The SNVS moudule is not used only by the linux, it may also used by
> > other SW component is secure world. No sense to gate it by linux, so
> > mark it as critical clock.
> 
> Does it make sense to even populate it in the kernel then? Presumably nobody is
> going to use it.

For such clocks, IMO, no sense to populate it in linux kernel. but it is already added there, and
referenced in dts file, so I just mark it CRITICAL to minimize the code changes. ^_^

BR
Jacky Bai