From: Rob Herring <robh@kernel.org>
To: Artur Weber <aweber.kernel@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Stanislav Jakubek <stano.jakubek@gmail.com>,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v2 1/6] dt-bindings: pinctrl: Add bindings for BCM21664 pin controller
Date: Mon, 24 Feb 2025 11:37:36 -0600 [thread overview]
Message-ID: <20250224173736.GA3566877-robh@kernel.org> (raw)
In-Reply-To: <2b3059be-2a82-44c9-9bf3-d1c98f66b0e8@gmail.com>
On Fri, Feb 21, 2025 at 09:37:48PM +0100, Artur Weber wrote:
> On 21.02.2025 21:32, Artur Weber wrote:
> > Add device tree bindings for the pin controller included in the
> > BCM21664 chip. The bindings are based off brcm,bcm11351-pinctrl.yaml;
> > both chips use the same driver, but have different pins, and the
> > BCM21664 has 6 alt modes instead of 4.
> >
> > Signed-off-by: Artur Weber <aweber.kernel@gmail.com>
> > ---
> > (...)
> > +examples:
> > + - |
> > + pinctrl@35004800 {
> > + compatible = "brcm,bcm21664-pinctrl";
> > + reg = <0x35004800 0x7f0>;
> > +
> > + dev-a-active-pins {
> > + /* group node defining 1 standard pin */
> > + std-grp0 {
> > + pins = "gpio00";
> > + function = "alt1";
> > + input-schmitt-enable;
> > + bias-disable;
> > + slew-rate = <1>;
> > + drive-strength = <4>;
> > + };
> > +
> > + /* group node defining 2 I2C pins */
> > + i2c-grp0 {
> > + pins = "bsc1clk", "bsc1dat";
> > + function = "alt2";
> > + bias-pull-up = <720>;
> > + input-enable;
>
> bias-pull-up should not have a value (pull up strength is not
> supported). Will fix this in the next version.
Please make the schema enforce that, not just fix the example.
Rob
next prev parent reply other threads:[~2025-02-24 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 20:32 [PATCH v2 0/6] pinctrl: bcm281xx: Add support for BCM21664 pinmux Artur Weber
2025-02-21 20:32 ` [PATCH v2 1/6] dt-bindings: pinctrl: Add bindings for BCM21664 pin controller Artur Weber
2025-02-21 20:37 ` Artur Weber
2025-02-24 17:37 ` Rob Herring [this message]
2025-02-21 20:32 ` [PATCH v2 2/6] pinctrl: bcm281xx: Use "unsigned int" instead of bare "unsigned" Artur Weber
2025-02-21 20:32 ` [PATCH v2 3/6] pinctrl: bcm281xx: Provide pinctrl device info as OF platform data Artur Weber
2025-02-21 20:32 ` [PATCH v2 4/6] pinctrl: bcm281xx: Add support for BCM21664 pinmux Artur Weber
2025-02-21 20:32 ` [PATCH v2 5/6] ARM: dts: bcm2166x-common: Add pinctrl node Artur Weber
2025-02-21 20:32 ` [PATCH v2 6/6] ARM: dts: bcm2166x: Add bcm2166x-pinctrl DTSI Artur Weber
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=20250224173736.GA3566877-robh@kernel.org \
--to=robh@kernel.org \
--cc=aweber.kernel@gmail.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=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=stano.jakubek@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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.