From: Stephen Boyd <sboyd@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>,
abel.vesa@linaro.org, abelvesa@kernel.org, festevam@gmail.com,
kernel@pengutronix.de, krzysztof.kozlowski+dt@linaro.org,
mturquette@baylibre.com, robh+dt@kernel.org,
s.hauer@pengutronix.de, shawnguo@kernel.org
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,
Marek Vasut <marex@denx.de>
Subject: Re: [RFC PATCH 0/2] Propose critical clocks
Date: Wed, 05 Oct 2022 16:06:07 -0700 [thread overview]
Message-ID: <20221005230609.5BA04C433D6@smtp.kernel.org> (raw)
In-Reply-To: <20221005082348.v43xbjrhbdlbaohv@pengutronix.de>
Quoting Marco Felsch (2022-10-05 01:23:48)
> Hi Stephen, Michael,
>
> I know it is a busy time right now, but maybe you have a few minutes for
> this RFC. I know it is incomplete, but the interessting part is there
> and it would fix a real issue we encountered on the imx8mm-evk's.
>
There's another approach by Marek[1]. Can you work together on a
solution? I think we should step away from trying to make the critical
flag work during clk registration, and turn on the clk during provider
registration instead. That hopefully makes it simpler. We can keep the
clk flag of course, so that the clk can't be turned off, but otherwise
we shouldn't need to make registration path check for the property.
[1] https://lore.kernel.org/all/20220924174517.458657-1-marex@denx.de/
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-10-05 23:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 10:21 [RFC PATCH 0/2] Propose critical clocks 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
2022-09-14 8:13 ` Marco Felsch
2022-10-05 8:23 ` Marco Felsch
2022-10-05 23:06 ` Stephen Boyd [this message]
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=20221005230609.5BA04C433D6@smtp.kernel.org \
--to=sboyd@kernel.org \
--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=marex@denx.de \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).