mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Marco Felsch <m.felsch@pengutronix.de>,
	krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
	abelvesa@kernel.org, abel.vesa@linaro.org,
	mturquette@baylibre.com, sboyd@kernel.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, kernel@pengutronix.de,
	festevam@gmail.com
Cc: linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
	linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org,
	linux-clk@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] Propose critical clocks
Date: Tue, 13 Sep 2022 20:24:47 +0800	[thread overview]
Message-ID: <30a8c599-583a-3eea-c7bf-04062c43b736@oss.nxp.com> (raw)
In-Reply-To: <20220913102141.971148-1-m.felsch@pengutronix.de>



On 9/13/2022 6:21 PM, Marco Felsch wrote:
> Hi,
> 
> this proposal is to mark clocks as critical. It is somehow inspired by
> the regulator-always-on property. Since sometimes we can end in circular
> dependcies if we wanna solve the dependcies for a specific clock
> provider.
> 
> The property is generic so it can be used by every hw clock provider. So
> it can be seen as generic implementation to [1].

Thanks for working on a generic solution, I think your proposal could 
also help [1] and try to resolve same issue as [2].


[1] 
https://lore.kernel.org/all/CAJ+vNU1Za2CPGVX3q4HKufsxbL5zRrk1B5CWFpKritetrTs4dA@mail.gmail.com/
[2] 
https://lore.kernel.org/all/20220517235919.200375-1-marex@denx.de/T/#m52d6d0831bf43d5f293e35cb27f3021f278d0564

Thanks,
Peng.


> 
> [1] https://lore.kernel.org/linux-clk/20220913092136.1706263-1-peng.fan@oss.nxp.com/
> 
> Marco Felsch (2):
>    clk: add support for critical always-on clocks
>    arm64: dts: imx8mm-evk: mark 32k pmic clock as always-on
> 
>   arch/arm64/boot/dts/freescale/imx8mm-evk.dtsi |  1 +
>   drivers/clk/clk.c                             | 18 ++++++++++++++++++
>   2 files changed, 19 insertions(+)
> 

  parent reply	other threads:[~2022-09-13 12:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 10:21 Marco Felsch
2022-09-13 10:21 ` [RFC PATCH 1/2] clk: add support for critical always-on clocks Marco Felsch
2022-09-13 10:21 ` [RFC PATCH 2/2] arm64: dts: imx8mm-evk: mark 32k pmic clock as always-on Marco Felsch
2022-09-13 10:33 ` [RFC PATCH 0/2] Propose critical clocks Marco Felsch
2022-09-13 10:48 ` Krzysztof Kozlowski
2022-09-13 11:51   ` Marco Felsch
2022-09-13 12:24 ` Peng Fan [this message]
2022-09-14  8:13   ` Marco Felsch
2022-10-05  8:23 ` Marco Felsch
2022-10-05 23:06   ` Stephen Boyd
2022-10-06 11:05     ` Marek Vasut
2023-01-17 16:45       ` Marco Felsch
2023-01-17 17:55     ` Marco Felsch
2023-03-29 19:40       ` Stephen Boyd

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=30a8c599-583a-3eea-c7bf-04062c43b736@oss.nxp.com \
    --to=peng.fan@oss.nxp.com \
    --cc=abel.vesa@linaro.org \
    --cc=abelvesa@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=mturquette@baylibre.com \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sboyd@kernel.org \
    --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
all inboxes | Powered by JetHome®