From: Guodong Liu <guodong.liu@mediatek.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sean Wang <sean.wang@kernel.org>
Cc: Sean Wang <sean.wang@mediatek.com>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Guodong Liu <guodong.liu@mediatek.com>
Subject: [PATCH v3 0/2] pinctrl: mediatek: Support pinctrl driver on mt8186
Date: Thu, 10 Feb 2022 14:21:19 +0800 [thread overview]
Message-ID: <20220210062122.23974-1-guodong.liu@mediatek.com> (raw)
changes since v2:
- update reg property
- update reg-names property
- sync rsel resistance selection property same as patch 3
- repair constraints is not indented correctly for bias-pull-{up,down}
- add "type: boolean" to the list of valid values. This corresponds to having bias-pull-{up,down} without any arguments.
- add dual file license for file "mt8186-pinfunc.h"
- add patch 3 to change "mediatek,rsel_resistance_in_si_unit" to "mediatek,rsel-resistance-in-si-unit"
changes since v1:
- add default pinctrl config to consistent with other MTK pinctrl drivers
Patch 1 add pinctrl file and binding document.
Patch 2 add pinctrl chip driver on mt8186.
Patch 3 canonical rsel resistance selection property.
Guodong Liu (3):
dt-bindings: pinctrl: mt8186: add pinctrl file and binding document
pinctrl: add pinctrl driver on mt8186
pinctrl: canonical rsel resistance selection property
.../bindings/pinctrl/pinctrl-mt8186.yaml | 313 +++
drivers/pinctrl/mediatek/Kconfig | 7 +
drivers/pinctrl/mediatek/Makefile | 1 +
drivers/pinctrl/mediatek/pinctrl-mt8186.c | 1313 ++++++++++
drivers/pinctrl/mediatek/pinctrl-mtk-mt8186.h | 2186 +++++++++++++++++
drivers/pinctrl/mediatek/pinctrl-paris.c | 2 +-
include/dt-bindings/pinctrl/mt8186-pinfunc.h | 1174 +++++++++
7 files changed, 4995 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-mt8186.yaml
create mode 100644 drivers/pinctrl/mediatek/pinctrl-mt8186.c
create mode 100644 drivers/pinctrl/mediatek/pinctrl-mtk-mt8186.h
create mode 100644 include/dt-bindings/pinctrl/mt8186-pinfunc.h
--
2.25.1
next reply other threads:[~2022-02-10 6:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 6:21 Guodong Liu [this message]
2022-02-10 6:21 ` [PATCH v3 1/3] dt-bindings: pinctrl: mt8186: add pinctrl file and binding document Guodong Liu
2022-02-10 14:47 ` Rob Herring
2022-02-14 3:03 ` Guodong Liu
2022-02-11 0:10 ` Linus Walleij
2022-02-11 12:28 ` Rob Herring
2022-02-14 3:04 ` Guodong Liu
2022-02-10 6:21 ` [PATCH v3 2/3] pinctrl: add pinctrl driver on mt8186 Guodong Liu
2022-02-10 8:57 ` AngeloGioacchino Del Regno
2022-02-14 3:02 ` Guodong Liu
2022-02-10 6:21 ` [PATCH v3 3/3] pinctrl: canonical rsel resistance selection property Guodong Liu
2022-02-10 8:50 ` AngeloGioacchino Del Regno
2022-02-14 3:03 ` Guodong Liu
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=20220210062122.23974-1-guodong.liu@mediatek.com \
--to=guodong.liu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.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=robh+dt@kernel.org \
--cc=sean.wang@kernel.org \
--cc=sean.wang@mediatek.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).