From: Christian Marangi <ansuelsmth@gmail.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>,
Sam Shih <sam.shih@mediatek.com>,
Christian Marangi <ansuelsmth@gmail.com>,
"SkyLake.Huang" <skylake.huang@mediatek.com>,
John Crispin <john@phrozen.org>,
Dong Huang <dong.huang@mediatek.com>,
u-boot@lists.denx.de
Subject: [PATCH 2/8] pinctrl: mediatek: mt7986: rename reg-names to upstream linux format
Date: Mon, 27 Jan 2025 14:40:39 +0100 [thread overview]
Message-ID: <20250127134046.26345-3-ansuelsmth@gmail.com> (raw)
In-Reply-To: <20250127134046.26345-1-ansuelsmth@gmail.com>
Rename reg-names to upstream linux format. Upstream linux drop the
"_base". To make use of upstream DTSI, align to the upstream naming.
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
---
arch/arm/dts/mt7986.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/dts/mt7986.dtsi b/arch/arm/dts/mt7986.dtsi
index f871f2394c5..64ce45a6530 100644
--- a/arch/arm/dts/mt7986.dtsi
+++ b/arch/arm/dts/mt7986.dtsi
@@ -132,9 +132,9 @@
<0x11f00000 0x1000>,
<0x11f10000 0x1000>,
<0x1000b000 0x1000>;
- reg-names = "gpio_base", "iocfg_rt_base", "iocfg_rb_base",
- "iocfg_lt_base", "iocfg_lb_base", "iocfg_tr_base",
- "iocfg_tl_base", "eint";
+ reg-names = "gpio", "iocfg_rt", "iocfg_rb",
+ "iocfg_lt", "iocfg_lb", "iocfg_tr",
+ "iocfg_tl", "eint";
gpio: gpio-controller {
gpio-controller;
#gpio-cells = <2>;
--
2.47.1
next prev parent reply other threads:[~2025-01-27 13:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 13:40 [PATCH 0/8] mediatek: final preparation for OF_UPSTREAM support Christian Marangi
2025-01-27 13:40 ` [PATCH 1/8] pinctrl: mediatek: mt7981: rename reg-names to upstream linux format Christian Marangi
2025-01-31 6:47 ` Weijie Gao
2025-01-27 13:40 ` Christian Marangi [this message]
2025-01-31 6:47 ` [PATCH 2/8] pinctrl: mediatek: mt7986: " Weijie Gao
2025-01-27 13:40 ` [PATCH 3/8] mediatek: mt7986: move gpio-controller up and rename pinctrl to pio Christian Marangi
2025-01-31 6:49 ` Weijie Gao
2025-01-27 13:40 ` [PATCH 4/8] pinctrl: mediatek: mt7988: rename reg-names to upstream linux format Christian Marangi
2025-01-31 6:50 ` Weijie Gao
2025-01-27 13:40 ` [PATCH 5/8] mediatek: mt7988: move gpio-controller up and rename pinctrl to pio Christian Marangi
2025-01-31 6:50 ` Weijie Gao (高惟杰)
2025-01-27 13:40 ` [PATCH 6/8] mediatek: mt7981: " Christian Marangi
2025-01-31 6:50 ` Weijie Gao (高惟杰)
2025-01-27 13:40 ` [PATCH 7/8] arm: dts: mediatek: add USB nodes for MT7981 Christian Marangi
2025-01-31 6:51 ` Weijie Gao
2025-01-27 13:40 ` [PATCH 8/8] arm: dts: mediatek: add PCIe node " Christian Marangi
2025-01-31 6:51 ` Weijie Gao
2025-02-04 19:43 ` [PATCH 0/8] mediatek: final preparation for OF_UPSTREAM support 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=20250127134046.26345-3-ansuelsmth@gmail.com \
--to=ansuelsmth@gmail.com \
--cc=GSS_MTK_Uboot_upstream@mediatek.com \
--cc=chunfeng.yun@mediatek.com \
--cc=dong.huang@mediatek.com \
--cc=john@phrozen.org \
--cc=ryder.lee@mediatek.com \
--cc=sam.shih@mediatek.com \
--cc=skylake.huang@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