Linux clock framework development
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Jacky Bai <ping.bai@nxp.com>,
	abel.vesa@nxp.com, mturquette@baylibre.com, shawnguo@kernel.org
Cc: festevam@gmail.com, linux-imx@nxp.com, linux-clk@vger.kernel.org
Subject: Re: [PATCH] clk: imx: Mark the snvs clock as critical by default
Date: Wed, 09 Mar 2022 10:46:35 -0800	[thread overview]
Message-ID: <20220309184637.31E2CC340F4@smtp.kernel.org> (raw)
In-Reply-To: <20220308101714.164163-1-ping.bai@nxp.com>

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.

  reply	other threads:[~2022-03-09 18:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 10:17 [PATCH] clk: imx: Mark the snvs clock as critical by default Jacky Bai
2022-03-09 18:46 ` Stephen Boyd [this message]
2022-03-10  0:54   ` Jacky Bai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220309184637.31E2CC340F4@smtp.kernel.org \
    --to=sboyd@kernel.org \
    --cc=abel.vesa@nxp.com \
    --cc=festevam@gmail.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=mturquette@baylibre.com \
    --cc=ping.bai@nxp.com \
    --cc=shawnguo@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox