From: Rob Herring <robh@kernel.org>
To: Andrea della Porta <andrea.porta@suse.com>
Cc: linus.walleij@linaro.org, krzk+dt@kernel.org,
conor+dt@kernel.org, florian.fainelli@broadcom.com,
wahrenst@gmx.net, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
iivanov@suse.de, svarbanov@suse.de, mbrugger@suse.com,
Jonathan Bell <jonathan@raspberrypi.com>,
Phil Elwell <phil@raspberrypi.com>
Subject: Re: [PATCH v3 1/3] dt-bindings: pinctrl: Add support for Broadcom STB pin controller
Date: Mon, 18 Aug 2025 12:20:40 -0500 [thread overview]
Message-ID: <20250818172040.GA1483013-robh@kernel.org> (raw)
In-Reply-To: <6fdbaf2bd0b72badbb5384e43b97bebcda4cc2f0.1754922935.git.andrea.porta@suse.com>
On Mon, Aug 11, 2025 at 04:46:51PM +0200, Andrea della Porta wrote:
> From: "Ivan T. Ivanov" <iivanov@suse.de>
>
> The STB pin controller represents a family whose silicon instances
> are found e.g. on BCM2712 SoC.
>
> In particular, on RaspberryPi 5, there are two separate instantiations
> of the same IP block which differ in the number of pins that are
> associated and the pinmux functions for each of those pins. The
> -aon- variant stands for 'Always On'.
>
> Depending on the revision of the BCM2712 (CO or D0), the pin
> controller instance has slight differences in the register layout.
>
> Signed-off-by: Ivan T. Ivanov <iivanov@suse.de>
> Signed-off-by: Andrea della Porta <andrea.porta@suse.com>
> ---
> .../pinctrl/brcm,bcm2712c0-pinctrl.yaml | 135 ++++++++++++++++++
> 1 file changed, 135 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,bcm2712c0-pinctrl.yaml
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/brcm,bcm2712c0-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/brcm,bcm2712c0-pinctrl.yaml
> new file mode 100644
> index 000000000000..28d66336aa2e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/brcm,bcm2712c0-pinctrl.yaml
> @@ -0,0 +1,135 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pinctrl/brcm,bcm2712c0-pinctrl.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom STB family pin controller
> +
> +maintainers:
> + - Ivan T. Ivanov <iivanov@suse.de>
> + - A. della Porta <andrea.porta@suse.com>
Why is your first name abbrievated here?
> +
> +description:
> + Broadcom's STB family of memory-mapped pin controllers.
> + This includes the pin controllers inside the BCM2712 SoC which
> + are instances of the STB family and has two silicon variants,
> + C0 and D0, which differs slightly in terms of registers layout.
> + The -aon- (Always On) variant is the same IP block but differs
> + in the number of pins that are associated and the pinmux functions
> + for each of those pins.
Wrap lines at 80. If there are paragraphs, then blank line in between
and use the '>' modifier.
> +
> +allOf:
> + - $ref: pinctrl.yaml#
> +
> +properties:
> + compatible:
> + enum:
> + - brcm,bcm2712c0-pinctrl
> + - brcm,bcm2712c0-aon-pinctrl
> + - brcm,bcm2712d0-pinctrl
> + - brcm,bcm2712d0-aon-pinctrl
> +
> + reg:
> + maxItems: 1
> +
> +patternProperties:
> + '-state$':
> + oneOf:
> + - $ref: '#/$defs/brcmstb-pinctrl-state'
> + - patternProperties:
> + '-pins$':
> + $ref: '#/$defs/brcmstb-pinctrl-state'
> + additionalProperties: false
> +
> +$defs:
> + brcmstb-pinctrl-state:
> + allOf:
> + - $ref: pincfg-node.yaml#
> + - $ref: pinmux-node.yaml#
> +
> + description:
> + Pin controller client devices use pin configuration subnodes (children
> + and grandchildren) for desired pin configuration.
> + Client device subnodes use below standard properties.
Paragraphs here?
> +
> + properties:
> + pins:
> + description:
> + List of gpio pins affected by the properties specified in this
> + subnode (either this or "groups" must be specified).
> + items:
> + pattern: '^((aon_)?s?gpio[0-6]?[0-9])|(emmc_(clk|cmd|dat[0-7]|ds))$'
> +
> + function:
> + enum: [ gpio, alt1, alt2, alt3, alt4, alt5, alt6, alt7, alt8,
> + aon_cpu_standbyb, aon_fp_4sec_resetb, aon_gpclk, aon_pwm,
> + arm_jtag, aud_fs_clk0, avs_pmu_bsc, bsc_m0, bsc_m1, bsc_m2,
> + bsc_m3, clk_observe, ctl_hdmi_5v, enet0, enet0_mii, enet0_rgmii,
> + ext_sc_clk, fl0, fl1, gpclk0, gpclk1, gpclk2, hdmi_tx0_auto_i2c,
> + hdmi_tx0_bsc, hdmi_tx1_auto_i2c, hdmi_tx1_bsc, i2s_in, i2s_out,
> + ir_in, mtsif, mtsif_alt, mtsif_alt1, pdm, pkt, pm_led_out, sc0,
> + sd0, sd2, sd_card_a, sd_card_b, sd_card_c, sd_card_d, sd_card_e,
> + sd_card_f, sd_card_g, spdif_out, spi_m, spi_s, sr_edm_sense, te0,
> + te1, tsio, uart0, uart1, uart2, usb_pwr, usb_vbus, uui, vc_i2c0,
> + vc_i2c3, vc_i2c4, vc_i2c5, vc_i2csl, vc_pcm, vc_pwm0, vc_pwm1,
> + vc_spi0, vc_spi3, vc_spi4, vc_spi5, vc_uart0, vc_uart2, vc_uart3,
> + vc_uart4 ]
> +
> + description:
> + Specify the alternative function to be configured for the specified
> + pins.
Be consistent with putting 'description' first or last.
> +
> + bias-disable: true
> + bias-pull-down: true
> + bias-pull-up: true
> +
> + required:
> + - pins
> +
> + if:
> + properties:
> + pins:
> + not:
> + contains:
> + pattern: "^emmc_(clk|cmd|dat[0-7]|ds)$"
> + then:
> + required:
> + - function
> + else:
> + properties:
> + function: false
> +
> + additionalProperties: false
> +
> +required:
> + - compatible
> + - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + brcm_pinctrl: pinctrl@7d504100 {
> + compatible = "brcm,bcm2712c0-pinctrl";
> + reg = <0x7d504100 0x30>;
> +
> + bt-shutdown-default-state {
> + function = "gpio";
> + pins = "gpio29";
> + };
> +
> + uarta-default-state {
> + rts-tx-pins {
> + function = "uart0";
> + pins = "gpio24", "gpio26";
> + bias-disable;
> + };
> +
> + cts-rx-pins {
> + function = "uart0";
> + pins = "gpio25", "gpio27";
> + bias-pull-up;
> + };
> + };
> + };
> --
> 2.35.3
>
next prev parent reply other threads:[~2025-08-18 18:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 14:46 [PATCH v3 0/3] Add pin control driver for BCM2712 SoC Andrea della Porta
2025-08-11 14:46 ` [PATCH v3 1/3] dt-bindings: pinctrl: Add support for Broadcom STB pin controller Andrea della Porta
2025-08-18 17:20 ` Rob Herring [this message]
2025-08-27 9:58 ` Andrea della Porta
2025-08-11 14:46 ` [PATCH v3 2/3] pinctrl: bcm: Add STB family pin controller driver Andrea della Porta
2025-08-19 7:40 ` Stanimir Varbanov
2025-08-19 8:14 ` Andrea della Porta
2025-08-19 8:19 ` Stanimir Varbanov
2025-08-19 8:40 ` Andrea della Porta
2025-08-19 9:18 ` Stefan Wahren
2025-08-21 15:36 ` Andrea della Porta
2025-08-27 16:32 ` Florian Fainelli
2025-08-27 16:31 ` Florian Fainelli
2025-08-19 9:37 ` Linus Walleij
2025-08-21 15:46 ` Andrea della Porta
2025-08-24 9:57 ` Stefan Wahren
2025-08-27 14:00 ` Andrea della Porta
2025-08-11 14:46 ` [PATCH v3 3/3] arm64: defconfig: Enable BCM2712 on-chip " Andrea della Porta
2025-08-19 7:25 ` Stanimir Varbanov
2025-08-21 9:35 ` Andrea della Porta
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=20250818172040.GA1483013-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrea.porta@suse.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=iivanov@suse.de \
--cc=jonathan@raspberrypi.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=mbrugger@suse.com \
--cc=phil@raspberrypi.com \
--cc=svarbanov@suse.de \
--cc=wahrenst@gmx.net \
--cc=will@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 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.