From: Huacai Chen <chenhuacai@kernel.org>
To: Yao Zi <ziyao@disroot.org>
Cc: Yinbo Zhu <zhuyinbo@loongson.cn>,
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>,
WANG Xuerui <kernel@xen0n.name>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
Mingcong Bai <jeffbai@aosc.io>,
Kexy Biscuit <kexybiscuit@aosc.io>
Subject: Re: [PATCH v2 0/8] Add clock support for Loongson 2K0300 SoC
Date: Thu, 19 Jun 2025 23:23:02 +0800 [thread overview]
Message-ID: <CAAhV-H6EDEf3U6w5KY3R3HCAdAbqDefqpE3ktCQeQtFbDK2Ypg@mail.gmail.com> (raw)
In-Reply-To: <aFQN2TSjT1IOvOt3@pie.lan>
On Thu, Jun 19, 2025 at 9:17 PM Yao Zi <ziyao@disroot.org> wrote:
>
> On Thu, Jun 19, 2025 at 05:02:48PM +0800, Huacai Chen wrote:
> > Hi, Yao,
> >
> > I suggest dropping the last two patches temporarily, because:
> > 1, the last two should be merged via another tree.
> > 2, the last two depend on another series which hasn't been merged now,
> > and can be squashed to that series.
>
> These are fair points, but I think including corresponding devicetree
> changes along with the binding patch helps review and proves the binding
> makes sense. it should be okay to merge only parts of a series, so I
> guess keeping the patches doesn't hurt, does it?
Yes, keeping them is just OK.
>
> By the way, do you prefer to wait until all fundamental drivers (clock,
> pinctrl, and reset) ready and merged, then merge the devicetree with all
> the three devices added? Or is it just fine to go part by part, with
> incremental changes to the devicetree?
Yes, I prefer to wait until fundamental drivers are merged.
Huacai
>
> Best regards,
> Yao Zi
>
> > Huacai
> >
> > On Wed, Jun 18, 2025 at 12:25 AM Yao Zi <ziyao@disroot.org> wrote:
> > >
> > > This series adds support for Loongson 2K0300's clock controller.
> > > Loongson 2 clock driver is prepared to support more clock variants and
> > > its flexibility is improved. All clock hardwares except the output one
> > > for GMAC module are then defined.
> > >
> > > A clock tree dump could be obtained here[1]. This series depends on v3
> > > of series "Initial support for CTCISZ Forever Pi"[2] to apply.
> > >
> > > [1]: https://gist.github.com/ziyao233/160bb4693e7758b2a2a996d4510b7247
> > > [2]: https://lore.kernel.org/all/20250523095408.25919-1-ziyao@disroot.org/
> > >
> > > Changed from v1:
> > > - Fold loongson,ls2k0300-clk.yaml into loongson,ls2k-clk.yaml
> > > - Include the new binding header in MAINTAINERS
> > > - Link to v1: https://lore.kernel.org/all/20250523104552.32742-1-ziyao@disroot.org/
> > >
> > > Yao Zi (8):
> > > dt-bindings: clock: loongson2: Add Loongson 2K0300 compatible
> > > clk: loongson2: Allow specifying clock flags for gate clock
> > > clk: loongson2: Support scale clocks with an alternative mode
> > > clk: loongson2: Allow zero divisors for dividers
> > > clk: loongson2: Avoid hardcoding firmware name of the reference clock
> > > clk: loongson2: Add clock definitions for Loongson 2K0300 SoC
> > > LoongArch: dts: Add clock tree for Loongson 2K0300
> > > LoongArch: dts: Remove clock-frquency from UART0 of CTCISZ Forever Pi
> > >
> > > .../bindings/clock/loongson,ls2k-clk.yaml | 26 +++-
> > > MAINTAINERS | 1 +
> > > .../dts/loongson-2k0300-ctcisz-forever-pi.dts | 1 -
> > > arch/loongarch/boot/dts/loongson-2k0300.dtsi | 17 ++-
> > > drivers/clk/clk-loongson2.c | 124 +++++++++++++++---
> > > .../dt-bindings/clock/loongson,ls2k0300-clk.h | 54 ++++++++
> > > 6 files changed, 193 insertions(+), 30 deletions(-)
> > > create mode 100644 include/dt-bindings/clock/loongson,ls2k0300-clk.h
> > >
> > > --
> > > 2.49.0
> > >
> > >
>
prev parent reply other threads:[~2025-06-19 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 16:24 [PATCH v2 0/8] Add clock support for Loongson 2K0300 SoC Yao Zi
2025-06-17 16:24 ` [PATCH v2 1/8] dt-bindings: clock: loongson2: Add Loongson 2K0300 compatible Yao Zi
2025-06-27 8:03 ` Krzysztof Kozlowski
2025-06-27 11:52 ` Yao Zi
2025-07-11 2:31 ` Yao Zi
2025-06-17 16:24 ` [PATCH v2 2/8] clk: loongson2: Allow specifying clock flags for gate clock Yao Zi
2025-06-17 16:24 ` [PATCH v2 3/8] clk: loongson2: Support scale clocks with an alternative mode Yao Zi
2025-06-17 16:24 ` [PATCH v2 4/8] clk: loongson2: Allow zero divisors for dividers Yao Zi
2025-06-17 16:24 ` [PATCH v2 5/8] clk: loongson2: Avoid hardcoding firmware name of the reference clock Yao Zi
2025-06-17 16:24 ` [PATCH v2 6/8] clk: loongson2: Add clock definitions for Loongson 2K0300 SoC Yao Zi
2025-06-17 16:24 ` [PATCH v2 7/8] LoongArch: dts: Add clock tree for Loongson 2K0300 Yao Zi
2025-06-17 16:24 ` [PATCH v2 8/8] LoongArch: dts: Remove clock-frquency from UART0 of CTCISZ Forever Pi Yao Zi
2025-06-19 9:02 ` [PATCH v2 0/8] Add clock support for Loongson 2K0300 SoC Huacai Chen
2025-06-19 13:17 ` Yao Zi
2025-06-19 15:23 ` Huacai Chen [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=CAAhV-H6EDEf3U6w5KY3R3HCAdAbqDefqpE3ktCQeQtFbDK2Ypg@mail.gmail.com \
--to=chenhuacai@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jeffbai@aosc.io \
--cc=kernel@xen0n.name \
--cc=kexybiscuit@aosc.io \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=zhuyinbo@loongson.cn \
--cc=ziyao@disroot.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).