From: Zhiyong Tao <zhiyong.tao@mediatek.com>
To: <robh+dt@kernel.org>, <linus.walleij@linaro.org>,
<mark.rutland@arm.com>, <matthias.bgg@gmail.com>,
<sean.wang@kernel.org>
Cc: <srv_heupstream@mediatek.com>, <zhiyong.tao@mediatek.com>,
<hui.liu@mediatek.com>, <eddie.huang@mediatek.com>,
<chuanjia.liu@mediatek.com>, <biao.huang@mediatek.com>,
<hongzhou.yang@mediatek.com>, <erin.lo@mediatek.com>,
<sean.wang@mediatek.com>, <sj.huang@mediatek.com>,
<seiya.wang@mediatek.com>, <jg_poxu@mediatek.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-gpio@vger.kernel.org>
Subject: [PATCH v2 0/3] Mediatek pinctrl patch on mt8192
Date: Sat, 1 Aug 2020 12:33:00 +0800 [thread overview]
Message-ID: <20200801043303.32149-1-zhiyong.tao@mediatek.com> (raw)
This series includes 3 patches:
1.add pinctrl file on mt8192.
2.add pinctrl binding document on mt8192.
3.add pinctrl driver on MT8192.
Changes in patch v2:
1)change maintainers name in pinctrl-mt8192.yaml.
2)remove unused description for "reg-names".
3)change 'subnode format:' which is not a child name to "^pins".
4)add ('|') after "description:".
5)remove "i2c0_pins_a: i2c0" and "i2c0_pins_a: i2c1".
6)add properties for pin configuration nodes.
Zhiyong Tao (3):
dt-bindings: pinctrl: mt8192: add pinctrl file
dt-bindings: pinctrl: mt8192: add binding document
pinctrl: add pinctrl driver on mt8192
.../bindings/pinctrl/pinctrl-mt8192.yaml | 151 ++
drivers/pinctrl/mediatek/Kconfig | 7 +
drivers/pinctrl/mediatek/Makefile | 1 +
drivers/pinctrl/mediatek/pinctrl-mt8192.c | 1453 +++++++++++
drivers/pinctrl/mediatek/pinctrl-mtk-mt8192.h | 2228 +++++++++++++++++
include/dt-bindings/pinctrl/mt8192-pinfunc.h | 1344 ++++++++++
6 files changed, 5184 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-mt8192.yaml
create mode 100644 drivers/pinctrl/mediatek/pinctrl-mt8192.c
create mode 100644 drivers/pinctrl/mediatek/pinctrl-mtk-mt8192.h
create mode 100644 include/dt-bindings/pinctrl/mt8192-pinfunc.h
--
2.18.0
next reply other threads:[~2020-08-01 4:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 4:33 Zhiyong Tao [this message]
2020-08-01 4:33 ` [PATCH v2 1/3] dt-bindings: pinctrl: mt8192: add pinctrl file Zhiyong Tao
2020-08-01 4:33 ` [PATCH v2 2/3] dt-bindings: pinctrl: mt8192: add binding document Zhiyong Tao
2020-08-03 21:40 ` Rob Herring
2020-08-04 0:14 ` zhiyong tao
2020-08-03 21:46 ` Rob Herring
2020-08-04 2:09 ` zhiyong tao
2020-08-01 4:33 ` [PATCH v2 3/3] pinctrl: add pinctrl driver on mt8192 Zhiyong Tao
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=20200801043303.32149-1-zhiyong.tao@mediatek.com \
--to=zhiyong.tao@mediatek.com \
--cc=biao.huang@mediatek.com \
--cc=chuanjia.liu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=erin.lo@mediatek.com \
--cc=hongzhou.yang@mediatek.com \
--cc=hui.liu@mediatek.com \
--cc=jg_poxu@mediatek.com \
--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=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=seiya.wang@mediatek.com \
--cc=sj.huang@mediatek.com \
--cc=srv_heupstream@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).