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, 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 v4 0/4] PINCTRL: Mediatek pinctrl patch on mt8183
Date: Mon, 1 Apr 2019 11:35:31 +0800 [thread overview]
Message-ID: <20190401033535.16910-1-zhiyong.tao@mediatek.com> (raw)
This series includes 4 patches:
1.add pinctrl binding document on mt8183.
2.add pinctrl file on mt8183.
3.add pinctrl device node on mt8183.
4.add drive for I2C related pins on MT8183.
Changes in patch v4:
1)patch [1/4] is based on patch "https://patchwork.kernel.org/patch/10778511/".
2)patch [2/4] is based on patch "https://patchwork.kernel.org/patch/10814251/".
3)patch [3/4] is based on patch "https://patchwork.kernel.org/patch/10814239/".
4)modify correct title on patch [2/4] and patch [3/4].
5)add Reviewed-by on patch [1/4] and [2/4].
6)modify the function "mtk_pinconf_adv_pull_get" and "mtk_pinconf_adv_pull_set"
7)change "drive-strengt-adv" to "drive-strength-adv".
8)call "mtk_pinconf_adv_pull_get" in "mtk_pinconf_get".
Changes in patch v3:
1)add the patch "dt-bindings: pinctrl: mt8183: add binding document".
2)add the patch "arm64: dts: mt8183: add pintcrl file".
3)add the patch "arm64: dts: mt8183: add pintcrl device node".
4)add more datail information for the specific driving setup in commit message.
5)use "mediatek,drive-strength-adv" instead of
"mediatek,drive-enable-adv" and "mediatek,drive-enable-disable".
6)change "PINCTRL_PIN_REG_DRV_EN_DIS" to "PINCTRL_PIN_REG_DRV_EN".
7)change the function "mtk_pinconf_adv_drive_set".
Changes in patch v2:
1)add the details strength specification of the I2c pins.
2)change "mt8183_pin_drv_en_dis_range" to "mt8183_pin_e1e0en_range".
3)change "mt8183_pin_drv_e0_range" to "mt8183_pin_e0_range".
4)change "mt8183_pin_drv_e1_range" to "mt8183_pin_e1_range".
Zhiyong Tao (4):
dt-bindings: pinctrl: mt8183: add binding document
arm64: dts: mt8183: add pinctrl file
arm64: dts: mt8183: add pinctrl device node
pinctrl: add drive for I2C related pins on MT8183
.../devicetree/bindings/pinctrl/pinctrl-mt8183.txt | 132 +++
arch/arm64/boot/dts/mediatek/mt8183-pinfunc.h | 1120 ++++++++++++++++++++
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 26 +-
drivers/pinctrl/mediatek/pinctrl-mt8183.c | 50 +
drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.c | 49 +
drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.h | 11 +
drivers/pinctrl/mediatek/pinctrl-paris.c | 21 +
7 files changed, 1408 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-mt8183.txt
create mode 100644 arch/arm64/boot/dts/mediatek/mt8183-pinfunc.h
--
2.12.5
next reply other threads:[~2019-04-01 3:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 3:35 Zhiyong Tao [this message]
2019-04-01 3:35 ` [PATCH v4 1/4] dt-bindings: pinctrl: mt8183: add binding document Zhiyong Tao
2019-04-05 3:44 ` Linus Walleij
2019-04-01 3:35 ` [PATCH v4 2/4] arm64: dts: mt8183: add pinctrl file Zhiyong Tao
2019-04-05 3:41 ` Linus Walleij
2019-04-01 3:35 ` [PATCH v4 3/4] arm64: dts: mt8183: add pinctrl device node Zhiyong Tao
2019-04-05 3:42 ` Linus Walleij
2019-04-01 3:35 ` [PATCH v4 4/4] pinctrl: add drive for I2C related pins on MT8183 Zhiyong Tao
2019-04-05 3:45 ` Linus Walleij
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=20190401033535.16910-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=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=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).