[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFGrd9rZxwtxx5f8Gp35-5152EPGiyEdZjps1Mhn5bL6QfufnA@mail.gmail.com>
Date: Wed, 15 Mar 2023 09:11:11 +0100
From: Alexandre Mergnat <amergnat@...libre.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Zhiyong Tao <zhiyong.tao@...iatek.com>,
Guenter Roeck <linux@...ck-us.net>,
Linus Walleij <linus.walleij@...aro.org>,
Bernhard Rosenkränzer <bero@...libre.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Chaotian Jing <chaotian.jing@...iatek.com>,
Rob Herring <robh+dt@...nel.org>,
Wenbin Mei <wenbin.mei@...iatek.com>,
Matthias Brugger <matthias.bgg@...il.com>,
linux-mmc@...r.kernel.org, Alexandre Bailon <abailon@...libre.com>,
devicetree@...r.kernel.org,
Amjad Ouled-Ameur <aouledameur@...libre.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-watchdog@...r.kernel.org,
linux-mediatek@...ts.infradead.org,
Fabien Parent <fparent@...libre.com>
Subject: Re: [PATCH v2 03/18] dt-bindings: pinctrl: mediatek,mt8365-pinctrl:
add drive strength property
Le ven. 10 mars 2023 à 10:49, AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com> a écrit :
>
> Il 10/03/23 10:46, AngeloGioacchino Del Regno ha scritto:
> >
> > Anyway, Alexandre: can you please perform a cleanup to the MT8365 pinctrl binding?
Yes I can ! :D
Should I do it directly in this patch series or (I prefer) in a new one ?
> > The cleanup means you're setting mediatek,drive-strength-adv as deprecated and
> > adding the right properties (...and possibly changing the devicetrees to use it).
> >
> > For more information, you can look at commit history for the (unfortunately, named
> > incorrectly) MT8195 pinctrl documentation: bindings/pinctrl/pinctrl-mt8195.yaml
> > where we performed the same cleanup that I'm asking you to do, except we didn't
> > have to set any property as deprecated because there was *no devicetree upstream*
> > that was actually using that property (hence not an ABI breakage).
Thanks for the information, that helps.
Regards,
Alex
Powered by blists - more mailing lists