From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Jerome Brunet <jbrunet@baylibre.com>,
Vyacheslav Yurkov via B4 Relay
<devnull+V.Yurkov.EXT.bruker.com@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Brian Masney <bmasney@redhat.com>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Jyri Sarha <jsarha@ti.com>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org,
Vyacheslav Yurkov <V.Yurkov.EXT@bruker.com>
Subject: Re: [PATCH v5 2/2] clk: Add gpio-locked fixed clock driver
Date: Thu, 17 Sep 2026 19:05:50 +0200 [thread overview]
Message-ID: <39fdddbf-0fdb-40e7-9cd5-c8f857ee8b9d@gmail.com> (raw)
In-Reply-To: <1jtsnpcn8l.fsf@starbuckisacylon.baylibre.com>
On 16.09.2026 15:57, Jerome Brunet wrote:
>>>> +/* We can't enable the clock, but the Common Clock Framework calls only
>>>> + * enable() not is_enabled()
>>>> + */
>>>> +static int gpio_locked_clk_enable(struct clk_hw *hw)
>>>> +{
>>>> + return gpio_locked_clk_is_enabled(hw);
>>>> +}
>
> You need to explain your problem a bit more because this is not OK. Your
> clock should really just provide .is_enabled() AFAICT
When a peripheral driver uses devm_clk_get_enabled(), this is resolved
to clk_prepare() and clk_enable(). Neither of them check for
.is_enabled(). Is that a flaw in the CCF or expected behavior?
>>>> +
>>>> +/* We have to implement it, but we are not going to control
>>>> + * parent clock selection
>>>> + */
>>>> +static u8 gpio_locked_clk_get_parent(struct clk_hw *hw)
>>>> +{
>>>> + return 0;
>>>> +}
>
> Same, I dont get why you need that. Not needed if there a single parent
This is a remnant from v4, thanks for spotting it.
Slava
prev parent reply other threads:[~2026-09-17 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 9:27 [PATCH v5 0/2] A proposal to add a " Vyacheslav Yurkov via B4 Relay
2026-09-15 9:27 ` [PATCH v5 1/2] dt-bindings: clock: gpio-gate-clock: Add a new compatible string Vyacheslav Yurkov via B4 Relay
2026-09-15 16:35 ` Conor Dooley
2026-09-15 9:27 ` [PATCH v5 2/2] clk: Add gpio-locked fixed clock driver Vyacheslav Yurkov via B4 Relay
2026-09-15 10:09 ` Jerome Brunet
2026-09-15 13:58 ` Vyacheslav Yurkov
2026-09-16 13:57 ` Jerome Brunet
2026-09-17 17:05 ` Vyacheslav Yurkov [this message]
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=39fdddbf-0fdb-40e7-9cd5-c8f857ee8b9d@gmail.com \
--to=uvv.mail@gmail.com \
--cc=V.Yurkov.EXT@bruker.com \
--cc=bmasney+clk@redhat.com \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+V.Yurkov.EXT.bruker.com@kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=jbrunet@baylibre.com \
--cc=jsarha@ti.com \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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®