All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yao Zi <ziyao@disroot.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Yinbo Zhu <zhuyinbo@loongson.cn>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	WANG Xuerui <kernel@xen0n.name>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	linux-gpio@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>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: gpio: loongson: Document GPIO controller of 2K0300 SoC
Date: Thu, 4 Sep 2025 01:40:56 +0000	[thread overview]
Message-ID: <aLjuKPIhTcdAQ7Z1@pie> (raw)
In-Reply-To: <aLW0rgvKno3zpXDi@pie>

Hi Huacai,

On Mon, Sep 01, 2025 at 02:58:54PM +0000, Yao Zi wrote:
> On Mon, Sep 01, 2025 at 10:22:04PM +0800, Huacai Chen wrote:
> > Hi, Yao,
> > 
> > On Mon, Sep 1, 2025 at 9:38 PM Yao Zi <ziyao@disroot.org> wrote:
> > >
> > > Loongson 2K0300 ships a GPIO controller whose input/output control logic
> > > is similar to previous generation of SoCs. Additionally, it acts as an
> > > interrupt-controller supporting both level and edge interrupts and has a
> > > distinct reset signal.
> > >
> > > Describe its compatible in devicetree. We enlarge the maximum value of
> > > ngpios to 128, since the controller technically supports at most 128
> > > pins, although only 106 are routed out of the package. Properties for
> > > interrupt-controllers and resets are introduced and limited as 2K0300
> > > only.
> > Replace the full name with "Loongson-2K0300" and short name with
> > "LS2K0300", others look good to me.
> > Reviewed-by: Huacai Chen <chenhuacai@loongson.cn>
> 
> I don't understand what is improved with this. For the fullname, I don't
> see any difference between "Loongson 2K0300" and "Loongson-2K0300". And
> for the short one, omitting the "LS" prefix doesn't introduce any
> ambiguity, either.
> 
> I did a quick search through git log, and found many commits for Loongson
> 2K SoCs do include a hyphen for the fullname and "LS" prefix for
> abbreviation in messages, while some merge commits don't do so.
> 
> Even the official production page for Loongson 2K0300 refers to it
> without a hyphen[1]. Thus I cannot find out of the point of rewording...
> 
> > Loongson 2K0300 is a multi-function SoC build upon the LA264 processor
> > core, ...
> 
> I'll appreciate and adapt it if you could explain why the change is
> necessary. Thanks for your patience.

Though I still don't understand purpose of the change, I've sent v3[2]
with naming style adjusted and all comments you left in PATCH 2
resolved. Thanks for your review.

> Best regards,
> Yao Zi
> 
> [1]: https://loongson.cn/EN/product/show?id=35

Regards,
Yao Zi

[2]: https://lore.kernel.org/linux-gpio/20250904013438.2405-1-ziyao@disroot.org/

  reply	other threads:[~2025-09-04  1:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 13:38 [PATCH v2 0/3] Support GPIO controller of Loongson 2K0300 SoC Yao Zi
2025-09-01 13:38 ` [PATCH v2 1/3] dt-bindings: gpio: loongson: Document GPIO controller of " Yao Zi
2025-09-01 14:22   ` Huacai Chen
2025-09-01 14:58     ` Yao Zi
2025-09-04  1:40       ` Yao Zi [this message]
2025-09-01 13:38 ` [PATCH v2 2/3] gpio: loongson-64bit: Add support for Loongson " Yao Zi
2025-09-01 14:24   ` Huacai Chen
2025-09-01 13:38 ` [PATCH v2 3/3] LoongArch: dts: Add GPIO controller for Loongson 2K0300 Yao Zi

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=aLjuKPIhTcdAQ7Z1@pie \
    --to=ziyao@disroot.org \
    --cc=brgl@bgdev.pl \
    --cc=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=krzysztof.kozlowski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@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 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.