From: Marco Felsch <m.felsch@pengutronix.de>
To: 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: Peng Fan <peng.fan@nxp.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
peng.fan@oss.nxp.com
Subject: Re: [RFC PATCH 0/2] Propose critical clocks
Date: Tue, 13 Sep 2022 12:33:30 +0200 [thread overview]
Message-ID: <20220913103330.owcemoinelvo5s45@pengutronix.de> (raw)
In-Reply-To: <20220913102141.971148-1-m.felsch@pengutronix.de>
+Cc Peng (OSS)
On 22-09-13, 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].
>
> [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(+)
>
> --
> 2.30.2
>
>
>
next prev parent reply other threads:[~2022-09-13 10:33 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 ` Marco Felsch [this message]
2022-09-13 10:48 ` [RFC PATCH 0/2] Propose critical clocks Krzysztof Kozlowski
2022-09-13 11:51 ` Marco Felsch
2022-09-13 12:24 ` Peng Fan
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=20220913103330.owcemoinelvo5s45@pengutronix.de \
--to=m.felsch@pengutronix.de \
--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=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.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®