From: Conor Dooley <conor@kernel.org>
To: Yinbo Zhu <zhuyinbo@loongson.cn>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Jianmin Lv <lvjianmin@loongson.cn>,
wanghongliang@loongson.cn, loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH v4 1/2] gpio: dt-bindings: add more loongson gpio chip support
Date: Wed, 23 Aug 2023 16:08:28 +0100 [thread overview]
Message-ID: <20230823-certainty-grimace-a8365c0cfb02@spud> (raw)
In-Reply-To: <20230823033427.23072-2-zhuyinbo@loongson.cn>
[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]
On Wed, Aug 23, 2023 at 11:34:26AM +0800, Yinbo Zhu wrote:
> This patch was to add loongson 2k0500, 2k2000 and 3a5000 gpio chip
> dt-bindings support in yaml file.
>
> Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn>
> ---
> .../bindings/gpio/loongson,ls-gpio.yaml | 23 +++++++++++++++----
> 1 file changed, 19 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/gpio/loongson,ls-gpio.yaml b/Documentation/devicetree/bindings/gpio/loongson,ls-gpio.yaml
> index fb86e8ce6349..97472f1529a0 100644
> --- a/Documentation/devicetree/bindings/gpio/loongson,ls-gpio.yaml
> +++ b/Documentation/devicetree/bindings/gpio/loongson,ls-gpio.yaml
> @@ -11,9 +11,24 @@ maintainers:
>
> properties:
> compatible:
> - enum:
> - - loongson,ls2k-gpio
> - - loongson,ls7a-gpio
> + oneOf:
> + - enum:
> + - loongson,ls2k-gpio
> + - loongson,ls2k0500-gpio0
> + - loongson,ls2k0500-gpio1
> + - loongson,ls2k2000-gpio0
> + - loongson,ls2k2000-gpio1
> + - loongson,ls2k2000-gpio2
> + - loongson,ls3a5000-gpio
> + - loongson,ls7a-gpio
> + - items:
> + - enum:
> + - loongson,ls2k1000-gpio
> + - const: loongson,ls2k-gpio
> + - items:
> + - enum:
> + - loongson,ls7a1000-gpio
> + - const: loongson,ls7a-gpio
Are there going to be more controllers that are compatible with
"ls7a-gpio"? If not, you can simplify both of these to have 2 const:
entries, like:
- items:
- const: loongson,ls2k1000-gpio
- const: loongson,ls2k-gpio
- items:
- const: loongson,ls7a1000-gpio
- const: loongson,ls7a-gpio
Either way,
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Thanks for sticking at this one :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-23 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 3:34 [PATCH v4 0/2] gpio: loongson: add more gpio chip support Yinbo Zhu
2023-08-23 3:34 ` [PATCH v4 1/2] gpio: dt-bindings: add more loongson " Yinbo Zhu
2023-08-23 12:17 ` Linus Walleij
2023-08-23 15:08 ` Conor Dooley [this message]
2023-08-29 12:12 ` Yinbo Zhu
2023-08-23 3:34 ` [PATCH v4 2/2] gpio: loongson: add more " Yinbo Zhu
2023-08-23 12:29 ` Linus Walleij
2023-08-29 11:27 ` Yinbo Zhu
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=20230823-certainty-grimace-a8365c0cfb02@spud \
--to=conor@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=lvjianmin@loongson.cn \
--cc=robh+dt@kernel.org \
--cc=wanghongliang@loongson.cn \
--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 NNTP newsgroup(s).