From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
Lee Jones <lee.jones@linaro.org>,
Michael Walle <michael@walle.cc>,
Jonas Gorski <jonas.gorski@gmail.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
devicetree@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 21/22] dt-bindings: add BCM6318 GPIO sysctl binding documentation
Date: Wed, 17 Mar 2021 11:48:55 +0100 [thread overview]
Message-ID: <DC3CDA11-CD67-474C-99CB-65895AE3EE36@gmail.com> (raw)
In-Reply-To: <CAL_JsqJuj6W=N1ATTYLg_Cz53-F11yz3UBOJd4kUzHfmKWXrLw@mail.gmail.com>
Hi Rob,
> El 16 mar 2021, a las 22:20, Rob Herring <robh+dt@kernel.org> escribió:
>
> On Mon, Mar 15, 2021 at 5:42 AM Álvaro Fernández Rojas
> <noltari@gmail.com> wrote:
>>
>> Add binding documentation for the GPIO sysctl found in BCM6318 SoCs.
>>
>> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
>> ---
>> v7: add changes suggested by Rob Herring
>>
>> .../mfd/brcm,bcm6318-gpio-sysctl.yaml | 179 ++++++++++++++++++
>> 1 file changed, 179 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/mfd/brcm,bcm6318-gpio-sysctl.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/mfd/brcm,bcm6318-gpio-sysctl.yaml b/Documentation/devicetree/bindings/mfd/brcm,bcm6318-gpio-sysctl.yaml
>> new file mode 100644
>> index 000000000000..7056a490a27d
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/mfd/brcm,bcm6318-gpio-sysctl.yaml
>> @@ -0,0 +1,179 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/mfd/brcm,bcm6318-gpio-sysctl.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Broadcom BCM6318 GPIO System Controller Device Tree Bindings
>> +
>> +maintainers:
>> + - Álvaro Fernández Rojas <noltari@gmail.com>
>> + - Jonas Gorski <jonas.gorski@gmail.com>
>> +
>> +description:
>> + Broadcom BCM6318 SoC GPIO system controller which provides a register map
>> + for controlling the GPIO and pins of the SoC.
>
> Perhaps a blurb about other registers in this block. From the
> registers, it looked like LED and PHY control at least.
I think it’s enough if I document this for now and others could add more information later on.
I’m not adding any more information about these system controllers, sorry.
>
>> +
>> +properties:
>> + "#address-cells": true
>> +
>> + "#size-cells": true
>> +
>> + compatible:
>> + items:
>> + - const: brcm,bcm6318-gpio-sysctl
>> + - const: syscon
>> + - const: simple-mfd
>> +
>> + ranges:
>> + maxItems: 1
>> +
>> + reg:
>> + maxItems: 1
>> +
>> +patternProperties:
>> + "^gpio@[0-9a-f]+$":
>> + # Child node
>> + type: object
>> + $ref: "../gpio/brcm,bcm63xx-gpio.yaml"
>> + description:
>> + GPIO controller for the SoC GPIOs. This child node definition
>> + should follow the bindings specified in
>> + Documentation/devicetree/bindings/gpio/brcm,bcm63xx-gpio.yaml.
>> +
>> + "^pinctrl@[0-9a-f]+$":
>> + # Child node
>> + type: object
>> + $ref: "../pinctrl/brcm,bcm6318-pinctrl.yaml"
>> + description:
>> + Pin controller for the SoC pins. This child node definition
>> + should follow the bindings specified in
>> + Documentation/devicetree/bindings/pinctrl/brcm,bcm6318-pinctrl.yaml.
>> +
>> +required:
>> + - "#address-cells"
>> + - compatible
>> + - ranges
>> + - reg
>> + - "#size-cells"
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + syscon@10000080 {
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + compatible = "brcm,bcm6318-gpio-sysctl", "syscon", "simple-mfd";
>> + reg = <0x10000080 0x80>;
>> + ranges = <0 0x10000080 0x80>;
>> +
>> + gpio@0 {
>> + compatible = "brcm,bcm6318-gpio";
>> + reg = <0x0 0x10>;
>> +
>> + data = <0xc>;
>> + dirout = <0x4>;
>> +
>> + gpio-controller;
>> + gpio-ranges = <&pinctrl 0 0 50>;
>> + #gpio-cells = <2>;
>> + };
>> +
>> + pinctrl: pinctrl@10 {
>> + compatible = "brcm,bcm6318-pinctrl";
>> + reg = <0x18 0x10>, <0x54 0x18>;
>> +
>> + pinctrl_ephy0_spd_led: ephy0_spd_led-pins {
>> + function = "ephy0_spd_led";
>> + pins = "gpio0";
>> + };
>> +
>> + pinctrl_ephy1_spd_led: ephy1_spd_led-pins {
>> + function = "ephy1_spd_led";
>> + pins = "gpio1";
>> + };
>> +
>> + pinctrl_ephy2_spd_led: ephy2_spd_led-pins {
>> + function = "ephy2_spd_led";
>> + pins = "gpio2";
>> + };
>> +
>> + pinctrl_ephy3_spd_led: ephy3_spd_led-pins {
>> + function = "ephy3_spd_led";
>> + pins = "gpio3";
>> + };
>> +
>> + pinctrl_ephy0_act_led: ephy0_act_led-pins {
>> + function = "ephy0_act_led";
>> + pins = "gpio4";
>> + };
>> +
>> + pinctrl_ephy1_act_led: ephy1_act_led-pins {
>> + function = "ephy1_act_led";
>> + pins = "gpio5";
>> + };
>> +
>> + pinctrl_ephy2_act_led: ephy2_act_led-pins {
>> + function = "ephy2_act_led";
>> + pins = "gpio6";
>> + };
>> +
>> + pinctrl_ephy3_act_led: ephy3_act_led-pins {
>> + function = "ephy3_act_led";
>> + pins = "gpio7";
>> + };
>> +
>> + pinctrl_serial_led: serial_led-pins {
>> + pinctrl_serial_led_data: serial_led_data-pins {
>> + function = "serial_led_data";
>> + pins = "gpio6";
>> + };
>> +
>> + pinctrl_serial_led_clk: serial_led_clk-pins {
>> + function = "serial_led_clk";
>> + pins = "gpio7";
>> + };
>> + };
>> +
>> + pinctrl_inet_act_led: inet_act_led-pins {
>> + function = "inet_act_led";
>> + pins = "gpio8";
>> + };
>> +
>> + pinctrl_inet_fail_led: inet_fail_led-pins {
>> + function = "inet_fail_led";
>> + pins = "gpio9";
>> + };
>> +
>> + pinctrl_dsl_led: dsl_led-pins {
>> + function = "dsl_led";
>> + pins = "gpio10";
>> + };
>> +
>> + pinctrl_post_fail_led: post_fail_led-pins {
>> + function = "post_fail_led";
>> + pins = "gpio11";
>> + };
>> +
>> + pinctrl_wlan_wps_led: wlan_wps_led-pins {
>> + function = "wlan_wps_led";
>> + pins = "gpio12";
>> + };
>> +
>> + pinctrl_usb_pwron: usb_pwron-pins {
>> + function = "usb_pwron";
>> + pins = "gpio13";
>> + };
>> +
>> + pinctrl_usb_device_led: usb_device_led-pins {
>> + function = "usb_device_led";
>> + pins = "gpio13";
>> + };
>> +
>> + pinctrl_usb_active: usb_active-pins {
>> + function = "usb_active";
>> + pins = "gpio40";
>> + };
>> + };
>> + };
>> --
>> 2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-17 10:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 11:41 [PATCH v7 00/22] pinctrl: add BCM63XX pincontrol support Álvaro Fernández Rojas
2021-03-15 11:41 ` [PATCH v7 01/22] gpio: guard gpiochip_irqchip_add_domain() with GPIOLIB_IRQCHIP Álvaro Fernández Rojas
2021-03-15 11:41 ` [PATCH v7 02/22] gpio: regmap: set gpio_chip of_node Álvaro Fernández Rojas
2021-03-15 11:41 ` [PATCH v7 03/22] dt-bindings: add BCM63XX GPIO binding documentation Álvaro Fernández Rojas
2021-03-16 20:54 ` Rob Herring
2021-03-17 10:46 ` Álvaro Fernández Rojas
2021-03-15 11:41 ` [PATCH v7 04/22] pinctrl: bcm: add bcm63xx base code Álvaro Fernández Rojas
2021-03-15 11:41 ` [PATCH v7 05/22] dt-bindings: add BCM6328 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-16 20:59 ` Rob Herring
2021-03-17 12:54 ` Álvaro Fernández Rojas
2021-03-15 11:41 ` [PATCH v7 06/22] dt-bindings: add BCM6328 GPIO sysctl " Álvaro Fernández Rojas
2021-03-15 11:41 ` [PATCH v7 07/22] pinctrl: add a pincontrol driver for BCM6328 Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 08/22] dt-bindings: add BCM6358 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 09/22] dt-bindings: add BCM6358 GPIO sysctl " Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 10/22] pinctrl: add a pincontrol driver for BCM6358 Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 11/22] dt-bindings: add BCM6362 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 12/22] dt-bindings: add BCM6362 GPIO sysctl " Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 13/22] pinctrl: add a pincontrol driver for BCM6362 Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 14/22] dt-bindings: add BCM6368 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 15/22] dt-bindings: add BCM6368 GPIO sysctl " Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 16/22] pinctrl: add a pincontrol driver for BCM6368 Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 17/22] dt-bindings: add BCM63268 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 18/22] dt-bindings: add BCM63268 GPIO sysctl " Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 19/22] pinctrl: add a pincontrol driver for BCM63268 Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 20/22] dt-bindings: add BCM6318 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-15 11:42 ` [PATCH v7 21/22] dt-bindings: add BCM6318 GPIO sysctl " Álvaro Fernández Rojas
2021-03-16 21:20 ` Rob Herring
2021-03-17 10:48 ` Álvaro Fernández Rojas [this message]
2021-03-15 11:42 ` [PATCH v7 22/22] pinctrl: add a pincontrol driver for BCM6318 Álvaro Fernández Rojas
2021-03-16 10:13 ` [PATCH v7 00/22] pinctrl: add BCM63XX pincontrol support Linus Walleij
2021-03-17 11:20 ` Álvaro Fernández Rojas
2021-03-20 11:38 ` 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=DC3CDA11-CD67-474C-99CB-65895AE3EE36@gmail.com \
--to=noltari@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=fazilyildiran@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=lee.jones@linaro.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=michael@walle.cc \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).