From: Rob Herring <robh@kernel.org>
To: frank-w@public-files.de
Cc: Frank Wunderlich <linux@fw-web.de>,
Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Sean Wang <sean.wang@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, daniel@makrotopia.org,
john@phrozen.org, ansuelsmth@gmail.com, eladwf@gmail.com
Subject: Re: [PATCH v1 3/4] dt-bindings: pinctrl: add binding for MT7988 SoC
Date: Mon, 7 Oct 2024 11:08:19 -0500 [thread overview]
Message-ID: <CAL_JsqKvJHf0OFpQf0uWeoqyCEvA4gdAyCdd7fD83_qQRSMErA@mail.gmail.com> (raw)
In-Reply-To: <DA1815FE-D2A6-46A3-9219-9216A3C6D61A@public-files.de>
On Sat, Oct 5, 2024 at 2:41 PM Frank Wunderlich <frank-w@public-files.de> wrote:
>
> Hi Rob
>
> Thank you for first review
>
> Am 5. Oktober 2024 20:44:49 MESZ schrieb Rob Herring <robh@kernel.org>:
> >On Fri, Oct 04, 2024 at 02:34:17PM +0200, Frank Wunderlich wrote:
>
> >> +patternProperties:
> >> + '-pins$':
> >> + type: object
> >> + additionalProperties: false
> >> +
> >> + patternProperties:
> >> + '^.*mux.*$':
> >
> >Do you really need 'mux' anywhere in the name?
> >
> >> + type: object
> >> + additionalProperties: false
> >> + description: |
> >> + pinmux configuration nodes.
> ...
> >> + '^.*conf.*$':
> >
> >Really need 'conf' anywhere in the name?
> >
> >> + type: object
> >> + additionalProperties: false
> >> + description:
> >> + pinconf configuration nodes.
> >> + $ref: /schemas/pinctrl/pincfg-node.yaml
>
> mux and conf are used to match subnodes see example for mdio0_pins
>
> mdio0_pins: mdio0-pins {
> mux {
> function = "eth";
> groups = "mdc_mdio0";
> };
>
> conf {
> pins = "SMI_0_MDC", "SMI_0_MDIO";
> drive-strength = <MTK_DRIVE_8mA>;
> };
> };
>
> This is same as done for previous SoC like mt7986.
Why do you need foomuxbar? Please define a prefix or suffix (separated
by a '-') or just a fixed string.
Either we missed it on mt7986 or it was documenting something already in use.
Rob
next prev parent reply other threads:[~2024-10-07 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 12:34 [PATCH v1 0/4] Add pinctrl support for mt7988 Frank Wunderlich
2024-10-04 12:34 ` [PATCH v1 1/4] pinctrl: mediatek: add support for MTK_PULL_PD_TYPE Frank Wunderlich
2024-10-04 12:34 ` [PATCH v1 2/4] pinctrl: mediatek: add MT7988 pinctrl driver Frank Wunderlich
2024-10-04 12:34 ` [PATCH v1 3/4] dt-bindings: pinctrl: add binding for MT7988 SoC Frank Wunderlich
2024-10-05 18:44 ` Rob Herring
2024-10-05 19:41 ` Frank Wunderlich
2024-10-07 16:08 ` Rob Herring [this message]
2024-10-04 12:34 ` [PATCH v1 4/4] arm64: dts: mediatek: mt7988: add pinctrl support Frank Wunderlich
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=CAL_JsqKvJHf0OFpQf0uWeoqyCEvA4gdAyCdd7fD83_qQRSMErA@mail.gmail.com \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ansuelsmth@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=eladwf@gmail.com \
--cc=frank-w@public-files.de \
--cc=john@phrozen.org \
--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@fw-web.de \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@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).