From: Sam Shih <sam.shih@mediatek.com>
To: Tom Rini <trini@konsulko.com>, Ryder Lee <ryder.lee@mediatek.com>,
"Weijie Gao" <weijie.gao@mediatek.com>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
GSS_MTK_Uboot_upstream <GSS_MTK_Uboot_upstream@mediatek.com>,
<u-boot@lists.denx.de>
Cc: Sam Shih <sam.shih@mediatek.com>
Subject: [v3,0/3] Add support for different mediatek pinctrl designs
Date: Fri, 1 Apr 2022 16:55:07 +0800 [thread overview]
Message-ID: <20220401085510.28668-1-sam.shih@mediatek.com> (raw)
There are some issues with patch series v2,
some of the modifications in patch 2/3 are misapplied in patch 3/3
MediaTek SoC's pinconf register usage varies by SoC,
So the original code uses V0/V1 to mark different pinconf design.
But actually, the real difference is the design of the "pin" itself.
Different SoCs will choose specify "pin design", which we call the
"io_type" of the pin.
For a better understanding of mediatek pinctrl design. and make the
driver clear and flexible, this patch series changes common parts
of mediatek pinctrl driver to support various pinctrl controller
designs.
---
v3: fix v2 patch series misapplied
v2: fix build fail caused by patch [2/3]
Sam Shih (3):
pinctrl: mediatek: rewrite mtk_pinconf_set and related functions
pinctrl: mediatek: introduce multiple memory bases support
pinctrl: mediatek: add support for different types of IO pins
drivers/pinctrl/mediatek/pinctrl-mtk-common.c | 219 ++++++++++++++----
drivers/pinctrl/mediatek/pinctrl-mtk-common.h | 78 ++++++-
2 files changed, 246 insertions(+), 51 deletions(-)
--
2.18.0
next reply other threads:[~2022-04-01 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 8:55 Sam Shih [this message]
2022-04-01 8:55 ` [v3, 1/3] pinctrl: mediatek: rewrite mtk_pinconf_set and related functions Sam Shih
2022-04-01 8:55 ` [v3,2/3] pinctrl: mediatek: introduce multiple memory bases support Sam Shih
2022-04-01 8:55 ` [v3, 3/3] pinctrl: mediatek: add support for different types of IO pins Sam Shih
2022-04-14 13:46 ` Tom Rini
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=20220401085510.28668-1-sam.shih@mediatek.com \
--to=sam.shih@mediatek.com \
--cc=GSS_MTK_Uboot_upstream@mediatek.com \
--cc=chunfeng.yun@mediatek.com \
--cc=ryder.lee@mediatek.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=weijie.gao@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