Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Changhuang Liang <changhuang.liang@starfivetech.com>
Cc: Conor Dooley <conor@kernel.org>,
	Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Emil Renner Berthing <kernel@esmil.dk>,
	Paul Walmsley <pjw@kernel.org>, Albert Ou <aou@eecs.berkeley.edu>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Bartosz Golaszewski <brgl@kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	Lianfeng Ouyang <lianfeng.ouyang@starfivetech.com>
Subject: Re: [PATCH v2 04/22] dt-bindings: pinctrl: Add starfive,jhb100-sys0-pinctrl
Date: Fri, 15 May 2026 08:22:42 +0100	[thread overview]
Message-ID: <20260515-eligible-greasily-257029ab1720@wendy> (raw)
In-Reply-To: <ZQ4PR01MB1202BD7677ACAF6EE18D062AF2042@ZQ4PR01MB1202.CHNPR01.prod.partner.outlook.cn>

[-- Attachment #1: Type: text/plain, Size: 10474 bytes --]

On Fri, May 15, 2026 at 06:10:28AM +0000, Changhuang Liang wrote:
> Hi, Conor
> 
> Thanks for the review.
> 
> > On Thu, May 14, 2026 at 04:12:00AM -0700, Changhuang Liang wrote:
> > > Add pinctrl bindings for StarFive JHB100 SoC System-0(sys0) pinctrl
> > > controller.
> > >
> > > Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
> > > ---
> > >  .../pinctrl/starfive,jhb100-sys0-pinctrl.yaml | 175 ++++++++++++++++++
> > >  .../pinctrl/starfive,jhb100-pinctrl.h         |  17 ++
> > >  2 files changed, 192 insertions(+)
> > >  create mode 100644
> > > Documentation/devicetree/bindings/pinctrl/starfive,jhb100-sys0-pinctrl
> > > .yaml  create mode 100644
> > > include/dt-bindings/pinctrl/starfive,jhb100-pinctrl.h
> > >
> > > diff --git
> > > a/Documentation/devicetree/bindings/pinctrl/starfive,jhb100-sys0-pinct
> > > rl.yaml
> > > b/Documentation/devicetree/bindings/pinctrl/starfive,jhb100-sys0-pinct
> > > rl.yaml
> > > new file mode 100644
> > > index 000000000000..21d3693587fd
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/pinctrl/starfive,jhb100-sys0-p
> > > +++ inctrl.yaml
> > > @@ -0,0 +1,175 @@
> > > +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause %YAML 1.2
> > > +---
> > > +$id:
> > > +http://devicetree.org/schemas/pinctrl/starfive,jhb100-sys0-pinctrl.ya
> > > +ml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: StarFive JHB100 System-0 Pin Controller
> > > +
> > > +description: |
> > > +  Pinctrl bindings for JHB100 RISC-V SoC from StarFive Technology Ltd.
> > > +
> > > +  The JHB100 SoC has 13 pinctrl domains - sys0, sys0h, sys1, sys2,
> > > + per0, per1,  per2, per2pok, per3, adc0, adc1, emmc, and vga.
> > > +  This document provides an overview of the "sys0" pinctrl domain.
> > > +
> > > +  The "sys0" domain has a pin controller which provides
> > > +  - function selection for GPIO pads.
> > > +  - GPIO pad configuration.
> > > +  - GPIO interrupt handling.
> > > +
> > > +  In the SYS0 Pin Controller, there are 4 multi-function GPIO_PADs.
> > > + Each of  them can be multiplexed to different hardware blocks
> > > + through function  selection and each iopad has a maximum of up to 2
> > functions - 0 and 1.
> > > +  Function 0 is the default function which is generally the GPIO
> > > + function  (or occasionally, it can be a peripheral signal).
> > > +  Function 1 is the alternate function or peripheral signal that can
> > > + be  routed to the iopad. The function selection is carried out by
> > > + writing  the function number to the iopad function select register.
> > > +
> > > +  Each iopad is configurable with parameters such as input-enable,
> > > + internal  pull-up/pull-down bias, drive strength, schmitt trigger,
> > > + slew rate,  input  debounce nanoseconds, power source and drive type
> > (open-drain or push-pull).
> > > +
> > > +maintainers:
> > > +  - Alex Soo <yuklin.soo@starfivetech.com>
> > 
> > Why is Alex the maintainer when you are the sole author?
> > 
> > > +
> > > +properties:
> > > +  compatible:
> > > +    items:
> > > +      - const: starfive,jhb100-sys0-pinctrl
> > > +
> > > +  reg:
> > > +    maxItems: 1
> > > +
> > > +  clocks:
> > > +    maxItems: 1
> > > +
> > > +  resets:
> > > +    maxItems: 1
> > > +
> > > +  interrupts:
> > > +    maxItems: 1
> > > +
> > > +  interrupt-controller: true
> > > +
> > > +  '#interrupt-cells':
> > > +    const: 3
> > > +
> > > +  gpio-controller: true
> > > +
> > > +  '#gpio-cells':
> > > +    const: 3
> > > +
> > > +  gpio-ranges: true
> > > +
> > > +  gpio-line-names: true
> > > +
> > > +patternProperties:
> > > +  '-grp$':
> > > +    type: object
> > > +    additionalProperties: false
> > > +    patternProperties:
> > > +      '-pins$':
> > > +        type: object
> > > +        description: |
> > > +          A pinctrl node should contain at least one subnode
> > representing the
> > > +          pinctrl groups available in the domain. Each subnode will list
> > the
> > > +          pins it needs, and how they should be configured, with regard
> > to
> > > +          function selection, bias, input enable/disable, input schmitt
> > > +          trigger enable/disable, slew-rate, input debounce
> > nanoseconds,
> > > +          drive-open-drain, drive-push-pull, power-source and
> > drive-strength.
> > > +        allOf:
> > > +          - $ref: /schemas/pinctrl/pincfg-node.yaml
> > > +          - $ref: /schemas/pinctrl/pinmux-node.yaml
> > > +        unevaluatedProperties: false
> > 
> > I think this should be additionalProperties, since you're citing all the
> > properties you do support below.
> > 
> > > +
> > > +        properties:
> > > +          pins:
> > > +            description:
> > > +              The list of IOs that properties in the pincfg node apply to.
> > > +
> > > +          function:
> > > +            description:
> > > +              A string containing the name of the function to mux for
> > these
> > > +              pins.
> > > +            enum: [ auxpwrgood, gpio, hbled, pe2rst_out ]
> > > +
> > > +          bias-disable: true
> > > +
> > > +          bias-pull-down:
> > > +            type: boolean
> > > +
> > > +          bias-pull-up:
> > > +            oneOf:
> > > +              - type: boolean
> > > +              - enum: [ 600, 900, 1200, 2000 ]
> > > +                description: Pull up RSEL type resistance values (in
> > ohms)
> > > +            description:
> > > +              For normal pull up type there is no need to specify a
> > resistance
> > > +              value, hence this can be specified as a boolean property.
> > > +              For RSEL pull up type a resistance value (in ohms) can be
> > added.
> > > +
> > > +          drive-open-drain: true
> > > +
> > > +          drive-push-pull: true
> > > +
> > > +          drive-strength:
> > > +            enum: [ 2, 4, 8, 12 ]
> > > +
> > > +          drive-strength-microamp:
> > > +            enum: [ 2000, 4000, 8000, 12000 ]
> > > +
> > > +          input-debounce-nanoseconds:
> > > +            minimum: 0
> > > +            maximum: 4294967295
> > > +
> > > +          input-disable: true
> > > +
> > > +          input-enable: true
> > > +
> > > +          input-schmitt-enable: true
> > > +
> > > +          input-schmitt-disable: true
> > > +
> > > +          power-source:
> > > +             enum: [ 0, 1, 2 ]
> > > +
> > > +          slew-rate:
> > > +            enum: [ 0, 1 ]
> > > +            default: 0
> > > +            description: |
> > > +                0: slow (half frequency)
> > > +                1: fast
> > > +
> > > +required:
> > > +  - compatible
> > > +  - reg
> > > +  - resets
> > > +  - interrupts
> > > +  - interrupt-controller
> > > +  - '#interrupt-cells'
> > > +  - gpio-controller
> > > +  - '#gpio-cells'
> > > +  - gpio-ranges
> > > +
> > > +additionalProperties: false
> > > +
> > > +examples:
> > > +  - |
> > > +    soc {
> > > +        #address-cells = <2>;
> > > +        #size-cells = <2>;
> > > +
> > > +        pinctrl_sys0: pinctrl@13080000 {
> > > +            compatible = "starfive,jhb100-sys0-pinctrl";
> > > +            reg = <0x0 0x13080000 0x0 0x800>;
> > > +            resets = <&sys0crg 2>;
> > > +            interrupts = <56>;
> > > +            interrupt-controller;
> > > +            #interrupt-cells = <3>;
> > > +            gpio-controller;
> > > +            #gpio-cells = <3>;
> > > +            gpio-ranges = <&pinctrl_sys0 0 0 0 4>;
> > > +        };
> > > +    };
> > > diff --git a/include/dt-bindings/pinctrl/starfive,jhb100-pinctrl.h
> > > b/include/dt-bindings/pinctrl/starfive,jhb100-pinctrl.h
> > > new file mode 100644
> > > index 000000000000..6d8f5516a178
> > > --- /dev/null
> > > +++ b/include/dt-bindings/pinctrl/starfive,jhb100-pinctrl.h
> > > @@ -0,0 +1,17 @@
> > > +/* SPDX-License-Identifier: GPL-2.0 OR MIT */
> > > +/*
> > > + * Copyright (C) 2022 StarFive Technology Co., Ltd.
> > > + *
> > > + * Author: Changhuang Liang <changhuang.liang@starfivetech.com>
> > > + */
> > > +
> > > +#ifndef __DT_BINDINGS_PINCTRL_STARFIVE_JHB100_H__
> > > +#define __DT_BINDINGS_PINCTRL_STARFIVE_JHB100_H__
> > > +
> > > +/* sys0 pad numbers */
> > > +#define PADNUM_SYS0_GPIO_A0				0
> > > +#define PADNUM_SYS0_GPIO_A1				1
> > > +#define PADNUM_SYS0_GPIO_A2				2
> > > +#define PADNUM_SYS0_GPIO_A3				3
> > 
> > Does this provide any actual value? Across the whole series, most numbers
> > you put in this binding headers do not appear in any drivers at all. Seems like
> > these defines should appear in the dts directly?
> 
> However, the current series of drivers will use some of these definitions.
> 
> Copied from patch 12:
> +static const struct pinvref_desc pinvref_desc_sys2[] = {
> +	{
> +		.name = "gpiow0",
> +		.pin_grp = {
> +			PADNUM_SYS2_GPIO_A36,
> +			PADNUM_SYS2_GPIO_A37,
> +			PADNUM_SYS2_GPIO_A38,
> +			PADNUM_SYS2_GPIO_A39
> +		},
> +		.num_pins = 4,
> +		.range = BIT(JHB100_PINVREF_1_8V) | BIT(JHB100_PINVREF_3_3V)

Can you explain why you need something like this when you're using pins
and functions? These look a lot like your own home-rolled groups, that
exist just to set the range of permitted values for vref?

As far as I can tell, the only controller that supports something other
than 1.8v and 3.3v is "per2", so you should be able to apply the
restrictions here entirely in the dt-binding?

I notice you have
> > > +          power-source:
> > > +             enum: [ 0, 1, 2 ]
in all bindings, but no explanation of what the values are. That needs
to change, and you should not permit 1 in anything other than "per2",
since that appears to be the only user.

Also, you've not responded to my other comments, one of which was a
question. Why not?

Thanks,
Conor.

> +	},
> +	{
> +		.name = "gpiow-inner",
> +		.pin_grp = {
> +			PADNUM_SYS2_GPIO_A40,
> +			PADNUM_SYS2_GPIO_A41,
> +			PADNUM_SYS2_GPIO_A42,
> +			PADNUM_SYS2_GPIO_A43
> +		},
> +		.num_pins = 4,
> +		.range = BIT(JHB100_PINVREF_1_8V) | BIT(JHB100_PINVREF_3_3V)
> +	},
> +	{ NULL },
> +};
> 
> Therefore, I have uniformly created include/dt-bindings/pinctrl/starfive,jhb100-pinctrl.h
> 
> Best Regards,
> Changhuang
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-05-15  7:23 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 11:11 [PATCH v2 00/22] Add basic pinctrl drivers for JHB100 SoC Changhuang Liang
2026-05-14 11:11 ` [PATCH v2 01/22] dt-bindings: pincfg-node: Add property 'input-debounce-nanoseconds' Changhuang Liang
2026-05-14 18:35   ` Conor Dooley
2026-05-14 11:11 ` [PATCH v2 02/22] pinctrl: pinconf-generic: " Changhuang Liang
2026-05-14 11:11 ` [PATCH v2 03/22] pinctrl: pinctrl-generic: Make the "function" property optional Changhuang Liang
2026-05-14 18:46   ` Conor Dooley
2026-05-15  5:55     ` Changhuang Liang
2026-05-15  7:38       ` Conor Dooley
2026-05-15  8:23         ` Changhuang Liang
2026-05-15  9:47           ` Conor Dooley
2026-05-15 10:30             ` Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 04/22] dt-bindings: pinctrl: Add starfive,jhb100-sys0-pinctrl Changhuang Liang
2026-05-14 18:52   ` Conor Dooley
2026-05-15  6:10     ` Changhuang Liang
2026-05-15  7:22       ` Conor Dooley [this message]
2026-05-15  8:53         ` Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 05/22] pinctrl: starfive: Add StarFive JHB100 sys0 controller driver Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 06/22] dt-bindings: pinctrl: Add starfive,jhb100-sys0h-pinctrl Changhuang Liang
2026-05-14 13:17   ` Rob Herring (Arm)
2026-05-14 11:12 ` [PATCH v2 07/22] pinctrl: starfive: Add StarFive JHB100 sys0h controller driver Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 08/22] dt-bindings: pinctrl: Add starfive,jhb100-sys1-pinctrl Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 09/22] pinctrl: starfive: Add StarFive JHB100 sys1 controller driver Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 10/22] dt-bindings: pinctrl: Add starfive,jhb100-sys2-pinctrl Changhuang Liang
2026-05-14 13:17   ` Rob Herring (Arm)
2026-05-14 11:12 ` [PATCH v2 11/22] pinctrl: starfive: Add StarFive JHB100 sys2 controller driver Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 12/22] dt-bindings: pinctrl: Add starfive,jhb100-per0-pinctrl Changhuang Liang
2026-05-14 13:17   ` Rob Herring (Arm)
2026-05-14 11:12 ` [PATCH v2 13/22] pinctrl: starfive: Add StarFive JHB100 per0 controller driver Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 14/22] dt-bindings: pinctrl: Add starfive,jhb100-per1-pinctrl Changhuang Liang
2026-05-14 13:17   ` Rob Herring (Arm)
2026-05-14 11:12 ` [PATCH v2 15/22] pinctrl: starfive: Add StarFive JHB100 per1 controller driver Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 16/22] dt-bindings: pinctrl: Add starfive,jhb100-per2-pinctrl Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 17/22] pinctrl: starfive: Add StarFive JHB100 per2 controller driver Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 18/22] dt-bindings: pinctrl: Add starfive,jhb100-per2pok-pinctrl Changhuang Liang
2026-05-14 13:17   ` Rob Herring (Arm)
2026-05-14 11:12 ` [PATCH v2 19/22] pinctrl: starfive: Add StarFive JHB100 per2pok controller driver Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 20/22] dt-bindings: pinctrl: Add starfive,jhb100-per3-pinctrl Changhuang Liang
2026-05-14 13:17   ` Rob Herring (Arm)
2026-05-14 11:12 ` [PATCH v2 21/22] pinctrl: starfive: Add StarFive JHB100 per3 controller driver Changhuang Liang
2026-05-14 11:12 ` [PATCH v2 22/22] riscv: dts: starfive: jhb100: Add pinctrl nodes Changhuang Liang

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=20260515-eligible-greasily-257029ab1720@wendy \
    --to=conor.dooley@microchip.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=brgl@kernel.org \
    --cc=changhuang.liang@starfivetech.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@esmil.dk \
    --cc=krzk+dt@kernel.org \
    --cc=lianfeng.ouyang@starfivetech.com \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=p.zabel@pengutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.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