All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
	"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
	"Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: erkin.bozoglu@xeront.com, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-mips@vger.kernel.org
Subject: Re: [PATCH 11/14] dt-bindings: pinctrl: add binding for Ralink MT7620 pinctrl
Date: Wed, 13 Apr 2022 17:37:30 +0200	[thread overview]
Message-ID: <41fa58ee-728b-7f0d-eea7-448c59641d85@linaro.org> (raw)
In-Reply-To: <20220413060729.27639-12-arinc.unal@arinc9.com>

On 13/04/2022 08:07, Arınç ÜNAL wrote:
> Add binding for the Ralink MT7620 pin controller for MT7620, MT7628 and
> MT7688 SoCs.
> 
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> ---
>  .../pinctrl/ralink,mt7620-pinctrl.yaml        | 87 +++++++++++++++++++
>  1 file changed, 87 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> 
> diff --git a/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> new file mode 100644
> index 000000000000..01578b8aa277
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> @@ -0,0 +1,87 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pinctrl/ralink,mt7620-pinctrl.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Ralink MT7620 Pin Controller
> +
> +maintainers:
> +  - Arınç ÜNAL <arinc.unal@arinc9.com>
> +  - Sergio Paracuellos <sergio.paracuellos@gmail.com>
> +
> +description:
> +  Ralink MT7620 pin controller for MT7620, MT7628 and MT7688 SoCs.
> +  The pin controller can only set the muxing of pin groups. Muxing indiviual pins

Run spellcheck on original bindings, don't copy same typos.

> +  is not supported. There is no pinconf support.
> +
> +properties:
> +  compatible:
> +    const: ralink,mt7620-pinctrl
> +
> +patternProperties:
> +  '-pins$':
> +    type: object
> +    patternProperties:
> +      '^(.*-)?pinmux$':

Why do you have two levels here? pins->pinmux->actual pin configuration?
Cannot be something like brcm,bcm636x has?

> +        type: object
> +        description: node for pinctrl.
> +        $ref: pinmux-node.yaml#
> +
> +        properties:
> +          groups:
> +            description: The pin group to select.

I wonder where do you configure particular pins because these are
groups... It's a bit confusing to configure "i2c" group into "i2c" -
looks obvious.

> +            enum: [
> +              # For MT7620 SoC
> +              ephy, i2c, mdio, nd_sd, pa, pcie, rgmii1, rgmii2, spi, spi refclk, uartf, uartlite, wdt, wled,
> +
> +              # For MT7628 and MT7688 SoCs
> +              gpio, i2c, i2s, p0led_an, p0led_kn, p1led_an, p1led_kn, p2led_an, p2led_kn, p3led_an,
> +              p3led_kn, p4led_an, p4led_kn, perst, pwm0, pwm1, refclk, sdmode, spi, spi cs1, spis, uart0,
> +              uart1, uart2, wdt, wled_an, wled_kn,
> +            ]
> +
> +          function:
> +            description: The mux function to select.
> +            enum: [
> +              # For MT7620 SoC
> +              ephy, gpio, gpio i2s, gpio uartf, i2c, i2s uartf, mdio, nand, pa, pcie refclk, pcie rst,
> +              pcm gpio, pcm i2s, pcm uartf, refclk, rgmii1, rgmii2, sd, spi, spi refclk, uartf, uartlite,
> +              wdt refclk, wdt rst, wled,
> +
> +              # For MT7628 and MT7688 SoCs
> +              antenna, debug, gpio, i2c, i2s, jtag, p0led_an, p0led_kn, p1led_an, p1led_kn, p2led_an,
> +              p2led_kn, p3led_an, p3led_kn, p4led_an, p4led_kn, pcie, pcm, perst, pwm, pwm0, pwm1,
> +              pwm_uart2, refclk, rsvd, sdxc, sdxc d5 d4, sdxc d6, sdxc d7, spi, spi cs1, spis, sw_r, uart0,
> +              uart1, uart2, utif, wdt, wled_an, wled_kn, -,

All these lines do not fit in 80-character limit. Linux coding style
still expects this in most of cases.

> +            ]
> +

Best regards,
Krzysztof

WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
	"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
	"Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: erkin.bozoglu@xeront.com, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-mips@vger.kernel.org
Subject: Re: [PATCH 11/14] dt-bindings: pinctrl: add binding for Ralink MT7620 pinctrl
Date: Wed, 13 Apr 2022 17:37:30 +0200	[thread overview]
Message-ID: <41fa58ee-728b-7f0d-eea7-448c59641d85@linaro.org> (raw)
In-Reply-To: <20220413060729.27639-12-arinc.unal@arinc9.com>

On 13/04/2022 08:07, Arınç ÜNAL wrote:
> Add binding for the Ralink MT7620 pin controller for MT7620, MT7628 and
> MT7688 SoCs.
> 
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> ---
>  .../pinctrl/ralink,mt7620-pinctrl.yaml        | 87 +++++++++++++++++++
>  1 file changed, 87 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> 
> diff --git a/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> new file mode 100644
> index 000000000000..01578b8aa277
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> @@ -0,0 +1,87 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pinctrl/ralink,mt7620-pinctrl.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Ralink MT7620 Pin Controller
> +
> +maintainers:
> +  - Arınç ÜNAL <arinc.unal@arinc9.com>
> +  - Sergio Paracuellos <sergio.paracuellos@gmail.com>
> +
> +description:
> +  Ralink MT7620 pin controller for MT7620, MT7628 and MT7688 SoCs.
> +  The pin controller can only set the muxing of pin groups. Muxing indiviual pins

Run spellcheck on original bindings, don't copy same typos.

> +  is not supported. There is no pinconf support.
> +
> +properties:
> +  compatible:
> +    const: ralink,mt7620-pinctrl
> +
> +patternProperties:
> +  '-pins$':
> +    type: object
> +    patternProperties:
> +      '^(.*-)?pinmux$':

Why do you have two levels here? pins->pinmux->actual pin configuration?
Cannot be something like brcm,bcm636x has?

> +        type: object
> +        description: node for pinctrl.
> +        $ref: pinmux-node.yaml#
> +
> +        properties:
> +          groups:
> +            description: The pin group to select.

I wonder where do you configure particular pins because these are
groups... It's a bit confusing to configure "i2c" group into "i2c" -
looks obvious.

> +            enum: [
> +              # For MT7620 SoC
> +              ephy, i2c, mdio, nd_sd, pa, pcie, rgmii1, rgmii2, spi, spi refclk, uartf, uartlite, wdt, wled,
> +
> +              # For MT7628 and MT7688 SoCs
> +              gpio, i2c, i2s, p0led_an, p0led_kn, p1led_an, p1led_kn, p2led_an, p2led_kn, p3led_an,
> +              p3led_kn, p4led_an, p4led_kn, perst, pwm0, pwm1, refclk, sdmode, spi, spi cs1, spis, uart0,
> +              uart1, uart2, wdt, wled_an, wled_kn,
> +            ]
> +
> +          function:
> +            description: The mux function to select.
> +            enum: [
> +              # For MT7620 SoC
> +              ephy, gpio, gpio i2s, gpio uartf, i2c, i2s uartf, mdio, nand, pa, pcie refclk, pcie rst,
> +              pcm gpio, pcm i2s, pcm uartf, refclk, rgmii1, rgmii2, sd, spi, spi refclk, uartf, uartlite,
> +              wdt refclk, wdt rst, wled,
> +
> +              # For MT7628 and MT7688 SoCs
> +              antenna, debug, gpio, i2c, i2s, jtag, p0led_an, p0led_kn, p1led_an, p1led_kn, p2led_an,
> +              p2led_kn, p3led_an, p3led_kn, p4led_an, p4led_kn, pcie, pcm, perst, pwm, pwm0, pwm1,
> +              pwm_uart2, refclk, rsvd, sdxc, sdxc d5 d4, sdxc d6, sdxc d7, spi, spi cs1, spis, sw_r, uart0,
> +              uart1, uart2, utif, wdt, wled_an, wled_kn, -,

All these lines do not fit in 80-character limit. Linux coding style
still expects this in most of cases.

> +            ]
> +

Best regards,
Krzysztof

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
	"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
	"Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: erkin.bozoglu@xeront.com, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-mips@vger.kernel.org
Subject: Re: [PATCH 11/14] dt-bindings: pinctrl: add binding for Ralink MT7620 pinctrl
Date: Wed, 13 Apr 2022 17:37:30 +0200	[thread overview]
Message-ID: <41fa58ee-728b-7f0d-eea7-448c59641d85@linaro.org> (raw)
In-Reply-To: <20220413060729.27639-12-arinc.unal@arinc9.com>

On 13/04/2022 08:07, Arınç ÜNAL wrote:
> Add binding for the Ralink MT7620 pin controller for MT7620, MT7628 and
> MT7688 SoCs.
> 
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> ---
>  .../pinctrl/ralink,mt7620-pinctrl.yaml        | 87 +++++++++++++++++++
>  1 file changed, 87 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> 
> diff --git a/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> new file mode 100644
> index 000000000000..01578b8aa277
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> @@ -0,0 +1,87 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pinctrl/ralink,mt7620-pinctrl.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Ralink MT7620 Pin Controller
> +
> +maintainers:
> +  - Arınç ÜNAL <arinc.unal@arinc9.com>
> +  - Sergio Paracuellos <sergio.paracuellos@gmail.com>
> +
> +description:
> +  Ralink MT7620 pin controller for MT7620, MT7628 and MT7688 SoCs.
> +  The pin controller can only set the muxing of pin groups. Muxing indiviual pins

Run spellcheck on original bindings, don't copy same typos.

> +  is not supported. There is no pinconf support.
> +
> +properties:
> +  compatible:
> +    const: ralink,mt7620-pinctrl
> +
> +patternProperties:
> +  '-pins$':
> +    type: object
> +    patternProperties:
> +      '^(.*-)?pinmux$':

Why do you have two levels here? pins->pinmux->actual pin configuration?
Cannot be something like brcm,bcm636x has?

> +        type: object
> +        description: node for pinctrl.
> +        $ref: pinmux-node.yaml#
> +
> +        properties:
> +          groups:
> +            description: The pin group to select.

I wonder where do you configure particular pins because these are
groups... It's a bit confusing to configure "i2c" group into "i2c" -
looks obvious.

> +            enum: [
> +              # For MT7620 SoC
> +              ephy, i2c, mdio, nd_sd, pa, pcie, rgmii1, rgmii2, spi, spi refclk, uartf, uartlite, wdt, wled,
> +
> +              # For MT7628 and MT7688 SoCs
> +              gpio, i2c, i2s, p0led_an, p0led_kn, p1led_an, p1led_kn, p2led_an, p2led_kn, p3led_an,
> +              p3led_kn, p4led_an, p4led_kn, perst, pwm0, pwm1, refclk, sdmode, spi, spi cs1, spis, uart0,
> +              uart1, uart2, wdt, wled_an, wled_kn,
> +            ]
> +
> +          function:
> +            description: The mux function to select.
> +            enum: [
> +              # For MT7620 SoC
> +              ephy, gpio, gpio i2s, gpio uartf, i2c, i2s uartf, mdio, nand, pa, pcie refclk, pcie rst,
> +              pcm gpio, pcm i2s, pcm uartf, refclk, rgmii1, rgmii2, sd, spi, spi refclk, uartf, uartlite,
> +              wdt refclk, wdt rst, wled,
> +
> +              # For MT7628 and MT7688 SoCs
> +              antenna, debug, gpio, i2c, i2s, jtag, p0led_an, p0led_kn, p1led_an, p1led_kn, p2led_an,
> +              p2led_kn, p3led_an, p3led_kn, p4led_an, p4led_kn, pcie, pcm, perst, pwm, pwm0, pwm1,
> +              pwm_uart2, refclk, rsvd, sdxc, sdxc d5 d4, sdxc d6, sdxc d7, spi, spi cs1, spis, sw_r, uart0,
> +              uart1, uart2, utif, wdt, wled_an, wled_kn, -,

All these lines do not fit in 80-character limit. Linux coding style
still expects this in most of cases.

> +            ]
> +

Best regards,
Krzysztof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-04-13 15:37 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  6:07 [PATCH 0/14] Refactor Ralink Pinctrl and Add Documentation Arınç ÜNAL
2022-04-13  6:07 ` Arınç ÜNAL
2022-04-13  6:07 ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 01/14] pinctrl: ralink: rename MT7628(an) functions to MT76X8 Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 02/14] pinctrl: ralink: rename pinctrl-rt2880 to pinctrl-ralink Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 03/14] pinctrl: ralink: rename pinmux functions to pinctrl Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 04/14] pinctrl: ralink: rename pinctrl-rt288x to pinctrl-rt2880 Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 05/14] pinctrl: ralink: rename variable names for functions on MT7620 and MT7621 Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 06/14] pinctrl: ralink: rename driver names to subdrivers Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 07/14] pinctrl: ralink: add new compatible strings for each pinctrl subdriver Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 08/14] MAINTAINERS: add Ralink pinctrl driver Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:27   ` Sergio Paracuellos
2022-04-13  6:27     ` Sergio Paracuellos
2022-04-13  6:27     ` Sergio Paracuellos
2022-04-13  8:29   ` Joe Perches
2022-04-13  8:29     ` Joe Perches
2022-04-13  8:29     ` Joe Perches
2022-04-13 10:40     ` Arınç ÜNAL
2022-04-13 10:40       ` Arınç ÜNAL
2022-04-13 10:40       ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 09/14] mips: dts: ralink: mt7621: use the new compatible string for MT7621 pinctrl Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13 15:27   ` Krzysztof Kozlowski
2022-04-13 15:27     ` Krzysztof Kozlowski
2022-04-13 15:27     ` Krzysztof Kozlowski
2022-04-14  8:38     ` Arınç ÜNAL
2022-04-14  8:38       ` Arınç ÜNAL
2022-04-14  8:38       ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 10/14] dt-bindings: pinctrl: rt2880: fix binding name, pin groups and functions Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13 15:25   ` Krzysztof Kozlowski
2022-04-13 15:25     ` Krzysztof Kozlowski
2022-04-13 15:25     ` Krzysztof Kozlowski
2022-04-14  8:34     ` Arınç ÜNAL
2022-04-14  8:34       ` Arınç ÜNAL
2022-04-14  8:34       ` Arınç ÜNAL
2022-04-14 16:17       ` Rob Herring
2022-04-14 16:17         ` Rob Herring
2022-04-14 16:17         ` Rob Herring
2022-04-14 16:37         ` Arınç ÜNAL
2022-04-14 16:37           ` Arınç ÜNAL
2022-04-14 16:37           ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 11/14] dt-bindings: pinctrl: add binding for Ralink MT7620 pinctrl Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13 15:37   ` Krzysztof Kozlowski [this message]
2022-04-13 15:37     ` Krzysztof Kozlowski
2022-04-13 15:37     ` Krzysztof Kozlowski
2022-04-14  1:52     ` Arınç ÜNAL
2022-04-14  1:52       ` Arınç ÜNAL
2022-04-14  1:52       ` Arınç ÜNAL
2022-04-14  6:33       ` Krzysztof Kozlowski
2022-04-14  6:33         ` Krzysztof Kozlowski
2022-04-14  6:33         ` Krzysztof Kozlowski
2022-04-14  8:16         ` Arınç ÜNAL
2022-04-14  8:16           ` Arınç ÜNAL
2022-04-14  8:16           ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 12/14] dt-bindings: pinctrl: add binding for Ralink MT7621 pinctrl Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 13/14] dt-bindings: pinctrl: add binding for Ralink RT305X pinctrl Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07 ` [PATCH 14/14] dt-bindings: pinctrl: add binding for Ralink RT3883 pinctrl Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:07   ` Arınç ÜNAL
2022-04-13  6:36 ` [PATCH 0/14] Refactor Ralink Pinctrl and Add Documentation Sergio Paracuellos
2022-04-13  6:36   ` Sergio Paracuellos
2022-04-13  6:36   ` Sergio Paracuellos
2022-04-13  7:52   ` Arınç ÜNAL
2022-04-13  7:52     ` Arınç ÜNAL
2022-04-13  7:52     ` Arınç ÜNAL
2022-04-13 15:39   ` Krzysztof Kozlowski
2022-04-13 15:39     ` Krzysztof Kozlowski
2022-04-13 15:39     ` Krzysztof Kozlowski
2022-04-14  8:26     ` Arınç ÜNAL
2022-04-14  8:26       ` Arınç ÜNAL
2022-04-14  8:26       ` Arınç ÜNAL
2022-04-21 14:27 ` Linus Walleij
2022-04-21 14:27   ` Linus Walleij
2022-04-21 14:27   ` Linus Walleij
2022-04-21 14:43   ` Arınç ÜNAL
2022-04-21 14:43     ` Arınç ÜNAL
2022-04-21 14:43     ` Arınç ÜNAL
2022-04-22  5:21     ` Sergio Paracuellos
2022-04-22  5:21       ` Sergio Paracuellos
2022-04-22  5:21       ` Sergio Paracuellos
2022-04-22  6:13       ` Arınç ÜNAL
2022-04-22  6:13         ` Arınç ÜNAL
2022-04-22  6:13         ` Arınç ÜNAL
2022-04-22 22:07         ` Linus Walleij
2022-04-22 22:07           ` Linus Walleij
2022-04-22 22:07           ` Linus Walleij

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=41fa58ee-728b-7f0d-eea7-448c59641d85@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=arinc.unal@arinc9.com \
    --cc=devicetree@vger.kernel.org \
    --cc=erkin.bozoglu@xeront.com \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=luizluca@gmail.com \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --cc=tsbogend@alpha.franken.de \
    /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.