From: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: <angelogioacchino.delregno@collabora.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
"Chen-Yu Tsai" <wenst@chromium.org>,
Allen-KH Cheng <allen-kh.cheng@mediatek.com>
Subject: [PATCH 0/2] MT8186 pinctrl properties adjustments
Date: Mon, 25 Jul 2022 18:02:51 +0800 [thread overview]
Message-ID: <20220725100253.10687-1-allen-kh.cheng@mediatek.com> (raw)
Based on tag: next-20220720, linux-next/master.
In commit e5fabbe43f3f ("pinctrl: mediatek: paris: Support generic
PIN_CONFIG_DRIVE_STRENGTH_UA"), added support for using
drive-strength-microamp instead of mediatek,drive-strength-adv.
We replace the custom mediatek,drive-strength-adv property with
'drive-strength-microamp' in the mt8186 pinctrl dt-binding which
have a clearer meaning and is more standardized, also add
gpio-line-names property used in devicetrees to describe pin names.
Allen-KH Cheng (2):
dt-bindings: pinctrl: mt8186: Add gpio-line-names property
dt-bindings: pinctrl: mt8186: Add and use drive-strength-microamp
.../bindings/pinctrl/pinctrl-mt8186.yaml | 31 +++----------------
1 file changed, 5 insertions(+), 26 deletions(-)
--
2.18.0
next reply other threads:[~2022-07-25 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 10:02 Allen-KH Cheng [this message]
2022-07-25 10:02 ` [PATCH 1/2] dt-bindings: pinctrl: mt8186: Add gpio-line-names property Allen-KH Cheng
2022-07-25 10:35 ` AngeloGioacchino Del Regno
2022-07-25 10:02 ` [PATCH 2/2] dt-bindings: pinctrl: mt8186: Add and use drive-strength-microamp Allen-KH Cheng
2022-07-25 10:35 ` AngeloGioacchino Del Regno
2022-07-25 11:05 ` allen-kh.cheng
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=20220725100253.10687-1-allen-kh.cheng@mediatek.com \
--to=allen-kh.cheng@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wenst@chromium.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