From: Rob Herring <robh@kernel.org>
To: Yassine Oudjana <yassine.oudjana@gmail.com>
Cc: Sean Wang <sean.wang@kernel.org>,
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>,
Yassine Oudjana <y.oudjana@protonmail.com>,
Andy Teng <andy.teng@mediatek.com>,
linux-mediatek@lists.infradead.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 1/8] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Pull pinctrl node changes from MT6795 document
Date: Fri, 11 Oct 2024 11:56:40 -0500 [thread overview]
Message-ID: <20241011165640.GA2475122-robh@kernel.org> (raw)
In-Reply-To: <20241011120520.140318-2-y.oudjana@protonmail.com>
On Fri, Oct 11, 2024 at 03:03:46PM +0300, Yassine Oudjana wrote:
> From: Yassine Oudjana <y.oudjana@protonmail.com>
>
> mediatek,pinctrl-mt6795.yaml has different node name patterns which match
> bindings of other MediaTek pin controllers, ref for pinmux-node.yaml which
> has a description of the pinmux property, as well as some additional
> descriptions for some pin configuration properties. Pull those changes
> into mediatek,mt6779-pinctrl.yaml and adjust the example DTS to match in
> preparation to combine the MT6795 document into it.
>
> Signed-off-by: Yassine Oudjana <y.oudjana@protonmail.com>
> ---
> .../pinctrl/mediatek,mt6779-pinctrl.yaml | 38 ++++++++++++++-----
> 1 file changed, 28 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml
> index 3bbc00df5548d..352a88d7b135e 100644
> --- a/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml
> @@ -111,12 +111,12 @@ allOf:
> - "#interrupt-cells"
>
> patternProperties:
> - '-[0-9]*$':
> + '-pins$':
Worst case, this could be an ABI break. Best case, it's churn for
mt6779. Is it worth unifying?
Rob
next prev parent reply other threads:[~2024-10-11 16:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 12:03 [PATCH v6 0/8] MediaTek pinctrl DT binding cleanup and MT6735 pinctrl support Yassine Oudjana
2024-10-11 12:03 ` [PATCH v6 1/8] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Pull pinctrl node changes from MT6795 document Yassine Oudjana
2024-10-11 16:56 ` Rob Herring [this message]
2024-10-12 8:09 ` Yassine Oudjana
2024-10-14 18:57 ` Rob Herring
2024-10-14 8:27 ` AngeloGioacchino Del Regno
2024-10-14 19:02 ` Rob Herring
2024-10-14 19:47 ` Rob Herring
2024-10-30 6:33 ` Yassine Oudjana
2024-10-14 8:01 ` AngeloGioacchino Del Regno
2024-10-11 12:03 ` [PATCH v6 2/8] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Improve pinctrl subnode and property descriptions Yassine Oudjana
2024-10-11 12:03 ` [PATCH v6 3/8] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Add MT6795 Yassine Oudjana
2024-10-14 8:02 ` AngeloGioacchino Del Regno
2024-10-11 12:03 ` [PATCH v6 4/8] arm64: dts: mediatek: mt6797: Make pin configuration nodes follow DT bindings Yassine Oudjana
2024-10-11 12:03 ` [PATCH v6 5/8] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Document MT6765 pin controller Yassine Oudjana
2024-10-11 12:03 ` [PATCH v6 6/8] dt-bindings: pinctrl: mediatek: Add bindings for MT6735 " Yassine Oudjana
2024-10-11 16:58 ` Rob Herring
2024-10-12 8:01 ` Yassine Oudjana
2024-10-14 7:59 ` AngeloGioacchino Del Regno
2024-10-11 12:03 ` [PATCH v6 7/8] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Document " Yassine Oudjana
2024-10-14 8:03 ` AngeloGioacchino Del Regno
2024-10-11 12:03 ` [PATCH v6 8/8] pinctrl: mediatek: Add MT6735 pinctrl driver Yassine Oudjana
2024-10-14 7:55 ` AngeloGioacchino Del Regno
2024-10-11 19:59 ` [PATCH v6 0/8] MediaTek pinctrl DT binding cleanup and MT6735 pinctrl support 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=20241011165640.GA2475122-robh@kernel.org \
--to=robh@kernel.org \
--cc=andy.teng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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=matthias.bgg@gmail.com \
--cc=sean.wang@kernel.org \
--cc=y.oudjana@protonmail.com \
--cc=yassine.oudjana@gmail.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 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).