public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
* [0/3] Add support for different mediatek pinctrl designs
@ 2022-03-10  4:31 Sam Shih
  2022-03-10  4:31 ` [1/3] pinctrl: mediatek: rewrite mtk_pinconf_set and related functions Sam Shih
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Sam Shih @ 2022-03-10  4:31 UTC (permalink / raw)
  To: Tom Rini, Ryder Lee, Weijie Gao, Chunfeng Yun,
	GSS_MTK_Uboot_upstream, u-boot
  Cc: Sam Shih

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.


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 | 217 ++++++++++++++----
 drivers/pinctrl/mediatek/pinctrl-mtk-common.h |  79 ++++++-
 2 files changed, 243 insertions(+), 53 deletions(-)

-- 
2.29.2


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2022-03-25 20:42 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-03-10  4:31 [0/3] Add support for different mediatek pinctrl designs Sam Shih
2022-03-10  4:31 ` [1/3] pinctrl: mediatek: rewrite mtk_pinconf_set and related functions Sam Shih
2022-03-25 20:42   ` Tom Rini
2022-03-10  4:31 ` [2/3] pinctrl: mediatek: introduce multiple memory bases support Sam Shih
2022-03-10  4:31 ` [3/3] pinctrl: mediatek: add support for different types of IO pins Sam Shih

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox