From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Eddie Hung <eddie.hung@mediatek.com>,
"Chunfeng Yun" <chunfeng.yun@mediatek.com>
Subject: [PATCH v6 4/4] arm64: dts: mediatek: mt8183: change efuse node name
Date: Fri, 17 Jun 2022 17:31:32 +0800 [thread overview]
Message-ID: <20220617093132.22578-4-chunfeng.yun@mediatek.com> (raw)
In-Reply-To: <20220617093132.22578-1-chunfeng.yun@mediatek.com>
Use the fixed "efuse" name for efuse nodes according to its yaml file
Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
---
v6: no changes
v5: new patch
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
index 01e650251928..82c6260998bd 100644
--- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
@@ -321,7 +321,7 @@
compatible = "simple-bus";
ranges;
- soc_data: soc_data@8000000 {
+ soc_data: efuse@8000000 {
compatible = "mediatek,mt8183-efuse",
"mediatek,efuse";
reg = <0 0x08000000 0 0x0010>;
--
2.18.0
next prev parent reply other threads:[~2022-06-17 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 9:31 [PATCH v6 1/4] dt-bindings: nvmem: convert mtk-efuse.txt to YAML schema Chunfeng Yun
2022-06-17 9:31 ` [PATCH v6 2/4] dt-bindings: nvmem: mediatek: efuse: add support mt8183 Chunfeng Yun
2022-06-17 9:31 ` [PATCH v6 3/4] arm64: dts: mediatek: mt8192: fix dtbs check warning of efuse Chunfeng Yun
2022-06-17 9:31 ` Chunfeng Yun [this message]
2022-06-17 19:41 ` [PATCH v6 1/4] dt-bindings: nvmem: convert mtk-efuse.txt to YAML schema Srinivas Kandagatla
2022-06-20 7:11 ` Chunfeng Yun
2022-06-22 14:10 ` Matthias Brugger
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=20220617093132.22578-4-chunfeng.yun@mediatek.com \
--to=chunfeng.yun@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.hung@mediatek.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
/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
all inboxes | Powered by JetHome®