All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Rafał Miłecki" <rafal@milecki.pl>,
	"Broadcom internal kernel review list"
	<bcm-kernel-feedback-list@broadcom.com>,
	"William Zhang" <william.zhang@broadcom.com>,
	"Anand Gore" <anand.gore@broadcom.com>,
	"Kursad Oney" <kursad.oney@broadcom.com>,
	"Florian Fainelli" <florian.fainelli@broadcom.com>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 5/6] dt-bindings: pinctrl: Add binding for BCM6846 pinctrl
Date: Wed, 1 Oct 2025 07:54:06 -0500	[thread overview]
Message-ID: <20251001125406.GA1138855-robh@kernel.org> (raw)
In-Reply-To: <20250930-bcmbca-pinctrl-v1-5-73218459a094@linaro.org>

On Tue, Sep 30, 2025 at 02:02:52PM +0200, Linus Walleij wrote:
> This SoC is part of the Broadcom Broadband Carrier Access (BCA)
> series. The BCM6846 has 79 muxable pins, these bindings define
> functions and groups for these.
> 
> The bindings are inspired by the other BCA pin control bindings
> for the BCM4908.
> 
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
>  .../bindings/pinctrl/brcm,bcm6846-pinctrl.yaml     | 82 ++++++++++++++++++++++
>  1 file changed, 82 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/pinctrl/brcm,bcm6846-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/brcm,bcm6846-pinctrl.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..e9c3b1e9ae0501574b5c15d4adfc5421f535c306
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/brcm,bcm6846-pinctrl.yaml
> @@ -0,0 +1,82 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pinctrl/brcm,bcm6846-pinctrl.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom BCM6846 pin controller
> +
> +maintainers:
> +  - Linus Walleij <linus.walleij@linaro.org>
> +
> +description:
> +  Binding for pin controller present on BCM6846 family SoCs.

This doesn't add any more than what 'title' says, so just drop.

> +
> +properties:
> +  compatible:
> +    const: brcm,bcm6846-pinctrl
> +
> +  reg:
> +    maxItems: 1
> +
> +patternProperties:
> +  '-pins$':
> +    type: object
> +    $ref: pinmux-node.yaml#
> +    additionalProperties: false
> +
> +    properties:
> +      function:
> +        enum: [ led_0, led_1, led_2, led_3, led_4, led_5, led_6, led_7, led_8,
> +                led_9, led_10, led_11, led_12, led_13, led_14, led_15, led_16,
> +                led_17, ser_led, nand, emmc, spim, usb0_pwr, usb1_pwr, i2c,
> +                rgmii, mii, signal_detect, one_sec_pls, rogue_onu, wan, uart0,
> +                uart2 ]
> +
> +      groups:
> +        minItems: 1
> +        # SPIM uses up to 5 groups for different select signals
> +        maxItems: 5
> +        items:
> +          enum: [ led_0_grp_a, led_0_grp_b, led_1_grp_a, led_1_grp_b,
> +                  led_2_grp_a, led_2_grp_b, led_3_grp_a, led_3_grp_b,
> +                  led_4_grp_a, led_4_grp_b, led_5_grp_a, led_5_grp_b,
> +                  led_6_grp_a, led_6_grp_b, led_7_grp_a, led_7_grp_b,
> +                  led_8_grp_a, led_8_grp_b, led_9_grp_a, led_9_grp_b,
> +                  led_10_grp_a, led_10_grp_b, led_11_grp_a, led_11_grp_b,
> +                  led_12_grp_a, led_12_grp_b, led_13_grp,
> +                  led_14_grp, led_15_grp, led_16_grp, led_17_grp,
> +                  ser_led_grp_a, ser_led_grp_b, nand_ctrl_grp, nand_data_grp,
> +                  nand_wp_grp, emmc_ctrl_grp, spim_grp_a, spim_ss0_grp_a,
> +                  spim_ss1_grp_a, spim_ss2_grp_a, spim_ss3_grp_a, spim_grp_b,
> +                  spim_ss0_grp_b, spim_ss1_grp_b, spim_ss2_grp_b, spim_ss3_grp_b,
> +                  spim_grp_c, spim_ss0_grp_c, spim_ss1_grp_c, spis_grp_a,
> +                  spis_ss_grp_a, spis_grp_b, spis_ss_grp_b, usb0_pwr_grp
> +                  usb1_pwr_grp, i2c_grp, rgmii_grp, rgmii_rx_ok_grp,
> +                  rgmii_start_stop_grp, mii_grp,
> +                  signal_detect_grp_a, signal_detect_grp_b, one_sec_pls_grp_a,
> +                  one_sec_pls_grp_b, rogue_onu_grp_a, rogue_onu_grp_b,
> +                  wan_mdio_grp, wan_nco_grp, wan_early_txen_grp_a,
> +                  wan_early_txen_grp_b, wan_nco_1pps_sig_grp_a,
> +                  wan_nco_1pps_sig_grp_b, uart0_grp, uart2_grp ]

Nothing required?

> +
> +allOf:
> +  - $ref: pinctrl.yaml#
> +
> +required:
> +  - compatible
> +  - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    pinctrl@ff800550 {
> +        compatible = "brcm,bcm6846-pinctrl";
> +        reg = <0xff800550 0x10>;
> +
> +        led-0-a-pins {
> +            function = "led_0";
> +            groups = "led_0_grp_a";
> +        };
> +    };
> 
> -- 
> 2.51.0
> 

  reply	other threads:[~2025-10-01 12:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 12:02 [PATCH 0/6] pinctrl: bcmbca: Refactor and add BCM6846 Linus Walleij
2025-09-30 12:02 ` [PATCH 1/6] pinctrl: bcm: Rename bcm4908 to bcmbca Linus Walleij
2025-09-30 12:02 ` [PATCH 2/6] pinctrl: bcm: bcmbca: Parameterize pins, groups, funcs Linus Walleij
2025-09-30 12:02 ` [PATCH 3/6] pinctrl: bcm: bcmbca: Prefix all BCM4908 data Linus Walleij
2025-09-30 12:02 ` [PATCH 4/6] pinctrl: bcm: bcmbca: Use a guarded mutex Linus Walleij
2025-09-30 12:02 ` [PATCH 5/6] dt-bindings: pinctrl: Add binding for BCM6846 pinctrl Linus Walleij
2025-10-01 12:54   ` Rob Herring [this message]
2025-09-30 12:02 ` [PATCH 6/6] pinctrl: bcm: bcmbca: Add support for BCM6846 Linus Walleij
2025-10-01  0:44   ` kernel test robot
2025-10-01  6:42 ` [PATCH 0/6] pinctrl: bcmbca: Refactor and add BCM6846 William Zhang
2025-10-01  7:59   ` Linus Walleij
2025-10-01 17:37     ` William Zhang
2025-10-01 22:43       ` Linus Walleij
2025-10-02  6:34         ` William Zhang

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=20251001125406.GA1138855-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=anand.gore@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=krzk+dt@kernel.org \
    --cc=kursad.oney@broadcom.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=william.zhang@broadcom.com \
    /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.