From: Conor Dooley <conor@kernel.org>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: Nuno Sa <nuno.sa@analog.com>,
linux-clk@vger.kernel.org, devicetree@vger.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>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 1/2] dt-bindings: clock: axi-clkgen: include AXI clk
Date: Thu, 31 Oct 2024 13:02:04 +0000 [thread overview]
Message-ID: <20241031-saga-earache-2179dc30adaa@spud> (raw)
In-Reply-To: <113e98edbff4501556e35698431080364e134233.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]
On Mon, Oct 28, 2024 at 03:01:44PM +0100, Nuno Sá wrote:
> > > The assumption is that the axi clock is the last one in the phandle array. But
> > > your
> > > comment made me think a bit more about this and I do see a possible problem if we
> > > run
> > > old DTs against a kernel with this patch. We have two possibilities:
> > >
> > > 1) DT only with one parent clock;
> > > 2) DT with two parent clocks;
> > >
> > > 1) is "fine" as it would now fail to probe. 2) is more problematic as we would
> > > assume
> > > the second parent to be the axi_bus clock so effectively not fixing anything and
> > > silently probing with a broken setup.
> > >
> > > So yeah, I think I overthinked the backward compatibility thing. I mean, in
> > > theory,
> > > all old DTs are not correct and should be fixed by including the axi_clk. And if
> > > we
> > > now enforce clock-names we at least get probe errors right away making it clear
> > > (which is far better from silently breaking after probe).
> > >
> > > Given the above, it should be fine to just enforce clock-names now, right?
> >
> > I think you need to enforce clock-names in the binding and take
> > !clock-names and 2 clocks to mean that the second one is a clkin. I
> > think that's a better solution than failing to probe for all extant
> > devicestrees.
>
> Ok, so IIUC, you mean leaving old DTs as of today and relying on someone else to
> enable the axi clock (if it was not enabled they would have noticed by now).
Yea. Obviously any old dts within reach (so those in-tree) should be
updated to have the missing third clock, but as we can't be sure we have
changed all users, so the driver must retain its current functionality
with the old devicetrees.
> And only
> take care of the bus clock when clock-names is provided?
Yup.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-10-31 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 14:56 [PATCH 0/2] clk: clk-axi-clkgen: make sure to enable the AXI bus clock Nuno Sa
2024-10-23 14:56 ` [PATCH 1/2] dt-bindings: clock: axi-clkgen: include AXI clk Nuno Sa
2024-10-23 16:30 ` Conor Dooley
2024-10-24 12:35 ` Nuno Sá
2024-10-24 16:13 ` Conor Dooley
2024-10-25 6:56 ` Nuno Sá
2024-10-25 16:47 ` Conor Dooley
2024-10-28 14:01 ` Nuno Sá
2024-10-31 13:02 ` Conor Dooley [this message]
2024-10-23 14:56 ` [PATCH 2/2] clk: clk-axi-clkgen: make sure to enable the AXI bus clock Nuno Sa
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=20241031-saga-earache-2179dc30adaa@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=noname.nuno@gmail.com \
--cc=nuno.sa@analog.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