All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yao Zi <me@ziyao.cc>
To: wjjsn <wjjsn@qq.com>,
	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
Subject: Re: [PATCH v2 1/2] dt-bindings: clock: loongson,ls2k: add ls2k1000 compatible
Date: Sun, 22 Mar 2026 12:54:05 +0000	[thread overview]
Message-ID: <ab_mbVVQ9Nf7pTRt@pie> (raw)
In-Reply-To: <tencent_1EA9B7D351AF8169F880BAAA49B37E178A08@qq.com>

On Sun, Mar 22, 2026 at 04:19:14PM +0800, wjjsn wrote:
> Add a SoC-specific "loongson,ls2k1000-clk" compatible.
> Retain the existing "loongson,ls2k-clk" as a deprecated fallback
> for backward compatibility.
> 
> Signed-off-by: wjjsn <wjjsn@qq.com>
> ---
>  .../devicetree/bindings/clock/loongson,ls2k-clk.yaml        | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/clock/loongson,ls2k-clk.yaml b/Documentation/devicetree/bindings/clock/loongson,ls2k-clk.yaml
> index c07ad1f85857..4d70bc4e7a13 100644
> --- a/Documentation/devicetree/bindings/clock/loongson,ls2k-clk.yaml
> +++ b/Documentation/devicetree/bindings/clock/loongson,ls2k-clk.yaml
> @@ -13,12 +13,16 @@ description: |
>    Loongson-2 SoC clock control module is an integrated clock controller, which
>    generates and supplies to all modules.
>  
> +  The "loongson,ls2k1000-clk" string should be used for Loongson-2K1000.
> +  The "loongson,ls2k-clk" string is kept as a fallback for backward compatibility for Loongson-2K1000.
> +
>  properties:
>    compatible:
>      enum:
>        - loongson,ls2k0300-clk
>        - loongson,ls2k0500-clk
> -      - loongson,ls2k-clk  # This is for Loongson-2K1000
> +      - loongson,ls2k-clk
> +      - loongson,ls2k1000-clk

If you want to deprecate loongson,ls2k-clk, you should probably mark
it as "deprecated: true", instead of describing such situation in human
language.

I don't have a strong opinion on the change, but I don't think it
improves the situation much. We still need to document the historical
compatible in bindings and support it in driver, the only thing gets
improved is a slightly more clear compatible name in devicetree.

However, even if someone is confused by the current compatible, they
could have a look in the binding and get an explanation quickly.

Regards,
Yao Zi

>        - loongson,ls2k2000-clk
>  
>    reg:
> -- 
> 2.43.0
> 
> 

  reply	other threads:[~2026-03-22 12:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260322081915.1626723-1-wjjsn@qq.com>
2026-03-22  8:19 ` [PATCH v2 1/2] dt-bindings: clock: loongson,ls2k: add ls2k1000 compatible wjjsn
2026-03-22 12:54   ` Yao Zi [this message]
2026-03-22  8:19 ` [PATCH v2 2/2] clk: loongson2: add support for " wjjsn

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=ab_mbVVQ9Nf7pTRt@pie \
    --to=me@ziyao.cc \
    --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=wjjsn@qq.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.