[PATCH v3 0/3] Cleanup Mediatek pinctrl device tree binding

From: Alexandre Mergnat
Date: Tue Apr 04 2023 - 12:30:19 EST


Deprecate properties which shall not exist, leaked upstream from downstream
kernels, there's no reason to use them. Here the deprecated properties and
the generic properties which will replace them:

- mediatek,drive-strength-adv => drive-strength-microamp
- mediatek,pull-up-adv => bias-pull-up
- mediatek,pull-down-adv => bias-pull-down

Another commit has been added in v3 to make it easier to merge. [2]

Thanks AngeloGioacchino Del Regno to reported it. [1]

[1]: https://lore.kernel.org/all/6e08d78f-ef4c-b228-f7d2-d63767ea87b8@xxxxxxxxxxxxx/
[2]: https://lore.kernel.org/all/20230203-evk-board-support-v4-2-5cffe66a38c0@xxxxxxxxxxxx/
[3]: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=devel

Signed-off-by: Alexandre Mergnat <amergnat@xxxxxxxxxxxx>
---
Changes in v3:
- Port another commit which modify the pinctrl from this serie [2].
- Rebased to linusw/linux-pinctrl as requested by the maintainer [3].
- Link to v2: https://lore.kernel.org/r/20230327-cleanup-pinctrl-binding-v2-0-f21fbcc3016e@xxxxxxxxxxxx

Changes in v2:
- Change the bias-pull enum values to match with other Mediatek SoC.
That allows to use MTK generic define and be compliant with the MTK
common pinctrl driver.
- Link to v1: https://lore.kernel.org/r/20230327-cleanup-pinctrl-binding-v1-0-b695e32e4f2e@xxxxxxxxxxxx

---
Alexandre Mergnat (3):
dt-bindings: pinctrl: mediatek: deprecate custom drive strength property
dt-bindings: pinctrl: mediatek: deprecate custom bias pull properties for mt8365
dt-bindings: pinctrl: mediatek,mt8365-pinctrl: add drive strength property

.../bindings/pinctrl/mediatek,mt8183-pinctrl.yaml | 8 +++-
.../bindings/pinctrl/mediatek,mt8365-pinctrl.yaml | 43 +++++++++++++++++++---
2 files changed, 43 insertions(+), 8 deletions(-)
---
base-commit: 743d3336029ffe2bb38e982a3b572ced243c6d43
change-id: 20230327-cleanup-pinctrl-binding-8064a8f8bf68

Best regards,
--
Alexandre Mergnat <amergnat@xxxxxxxxxxxx>