From: wjjsn <wjjsn@qq.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
chenhuacai@kernel.org, zhuyinbo@loongson.cn,
mturquette@baylibre.com, sboyd@kernel.org
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
loongarch@lists.linux.dev, kernel@xen0n.name,
devicetree@vger.kernel.org, wjjsn <wjjsn@qq.com>
Subject: [PATCH v3 0/2] loongson2 clk: introduce ls2k1000 specific compatible
Date: Sun, 22 Mar 2026 23:20:28 +0800 [thread overview]
Message-ID: <tencent_42EBBFB2A4110192AADECFAA5D48A7F64D0A@qq.com> (raw)
Changes in v3:
- Use 'deprecated: true' property for the old compatible string
instead of just describing it in human language, as suggested
by Yao Zi.
- In the example, the 'loongson,ls2k-clk'
has been changed to 'loongson,ls2k1000-clk'
- The order in loongson2_clk_match_table has been adjusted
Changes in v2:
- Consistently use wjjsn <wjjsn@qq.com> for
both Author and Signed-off-by fields.
The "loongson,ls2k-clk" compatible is currently used for the
Loongson-2K1000 clock controller, despite being generic.
This series introduces a SoC-specific compatible
"loongson,ls2k1000-clk" to make the binding more precise and
consistent with other Loongson-2 variants.
The existing "loongson,ls2k-clk" is retained as a deprecated
fallback for backward compatibility.
Patch 1 updates the devicetree binding documentation.
Patch 2 adds driver support and updates the DTS.
Regards,
wjjsn
wjjsn (2):
dt-bindings: clock: loongson,ls2k: Add ls2k1000 compatible and
deprecate legacy
clk: loongson2: Add ls2k1000 compatible
.../bindings/clock/loongson,ls2k-clk.yaml | 15 +++++++++------
arch/loongarch/boot/dts/loongson-2k1000.dtsi | 2 +-
drivers/clk/clk-loongson2.c | 3 ++-
3 files changed, 12 insertions(+), 8 deletions(-)
--
2.43.0
reply other threads:[~2026-03-22 15:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tencent_42EBBFB2A4110192AADECFAA5D48A7F64D0A@qq.com \
--to=wjjsn@qq.com \
--cc=chenhuacai@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@xen0n.name \
--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 \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).