From: Brian Masney <bmasney@redhat.com>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Junhui Liu <junhui.liu@pigmoral.tech>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Conor Dooley <conor@kernel.org>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Yixun Lan <dlan@kernel.org>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH 2/2] riscv: dts: anlogic: drop unused DR1V90 external clocks
Date: Fri, 2 Oct 2026 11:23:35 -0400 [thread overview]
Message-ID: <ar_MdxhafYCvqci_@redhat.com> (raw)
In-Reply-To: <20261002-manpower-croon-26d578f57143@wendy>
Hi Conor,
On Fri, Oct 02, 2026 at 08:09:08AM +0100, Conor Dooley wrote:
> On Fri, Oct 02, 2026 at 02:07:01PM +0800, Junhui Liu wrote:
> > The external CAN and watchdog clock inputs are not routed on the MLKPAI
> > FS01, the only board currently supported. Drop the two fixed-clock
> > placeholders from the common dtsi, as fixed clocks require a valid
> > clock-frequency property.
> >
> > Both clock muxes select their internal parent clocks after reset, so
> > the CRU operates correctly without the external inputs. Keep only the
> > required oscillator input to the CRU.
> >
> > A board using these external clocks should define them in its own
> > board-level dts and override the clocks and clock-names properties of
> > the CRU node.
> >
> > Reported-by: Yixun Lan <dlan@kernel.org>
> > Fixes: 7849521aaac2 ("riscv: dts: anlogic: add clocks and CRU for DR1V90")
>
> Uh, why is this in linux next?
>
> Brian, please don't apply dts patches to the clock (or any other) driver
> tree in the future.
OK, sorry. I just checked clk-next and this is the only dts that I
applied. I'll rebase clk-next and drop this so that the tree only
contains the drivers.
Brian
>
> Patch itself makes total sense,
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> and because it's easier
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> > Signed-off-by: Junhui Liu <junhui.liu@pigmoral.tech>
> > ---
> > arch/riscv/boot/dts/anlogic/dr1v90.dtsi | 16 ++--------------
> > 1 file changed, 2 insertions(+), 14 deletions(-)
> >
> > diff --git a/arch/riscv/boot/dts/anlogic/dr1v90.dtsi b/arch/riscv/boot/dts/anlogic/dr1v90.dtsi
> > index 574c6608aef0..fe85d01563ad 100644
> > --- a/arch/riscv/boot/dts/anlogic/dr1v90.dtsi
> > +++ b/arch/riscv/boot/dts/anlogic/dr1v90.dtsi
> > @@ -44,23 +44,11 @@ cpu0_intc: interrupt-controller {
> > };
> >
> > clocks {
> > - can_ext: clock-ext-can {
> > - compatible = "fixed-clock";
> > - clock-output-names = "can_ext";
> > - #clock-cells = <0>;
> > - };
> > -
> > osc: clock-osc {
> > compatible = "fixed-clock";
> > clock-output-names = "osc";
> > #clock-cells = <0>;
> > };
> > -
> > - wdt_ext: clock-ext-wdt {
> > - compatible = "fixed-clock";
> > - clock-output-names = "wdt_ext";
> > - #clock-cells = <0>;
> > - };
> > };
> >
> > soc {
> > @@ -128,8 +116,8 @@ uart1: serial@f8401000 {
> > cru: clock-controller@f8801000 {
> > compatible = "anlogic,dr1v90-cru";
> > reg = <0x0 0xf8801000 0 0x400>;
> > - clocks = <&osc>, <&can_ext>, <&wdt_ext>;
> > - clock-names = "osc", "can_ext", "wdt_ext";
> > + clocks = <&osc>;
> > + clock-names = "osc";
> > #clock-cells = <1>;
> > #reset-cells = <1>;
> > };
> >
> > --
> > 2.55.0
> >
prev parent reply other threads:[~2026-10-02 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 6:06 [PATCH 0/2] riscv: dts: anlogic: dr1v90: fix clock dtbs_check errors Junhui Liu
2026-10-02 6:07 ` [PATCH 1/2] dt-bindings: clock: anlogic,dr1v90-cru: make external clocks optional Junhui Liu
2026-10-02 7:17 ` Conor Dooley
2026-10-02 15:55 ` Junhui Liu
2026-10-02 6:07 ` [PATCH 2/2] riscv: dts: anlogic: drop unused DR1V90 external clocks Junhui Liu
2026-10-02 7:09 ` Conor Dooley
2026-10-02 15:23 ` Brian Masney [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=ar_MdxhafYCvqci_@redhat.com \
--to=bmasney@redhat.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=junhui.liu@pigmoral.tech \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--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®