From: Andrew-CT Chen <andrew-ct.chen@mediatek.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
srv_heupstream@mediatek.com,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>
Subject: [PATCH v2 3/3] dts: arm64: Add EFUSE device node
Date: Thu, 19 Nov 2015 18:46:54 +0800 [thread overview]
Message-ID: <1447930014-19579-4-git-send-email-andrew-ct.chen@mediatek.com> (raw)
In-Reply-To: <1447930014-19579-1-git-send-email-andrew-ct.chen@mediatek.com>
Add Mediatek MT8173 EFUSE device node
Signed-off-by: Andrew-CT Chen <andrew-ct.chen@mediatek.com>
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
index 4dd5f93..d67e23b 100644
--- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
@@ -267,6 +267,11 @@
reg = <0 0x10200620 0 0x20>;
};
+ efuse: efuse@10206000 {
+ compatible = "mediatek,mt8173-efuse";
+ reg = <0 0x10206000 0 0x1000>;
+ };
+
apmixedsys: clock-controller@10209000 {
compatible = "mediatek,mt8173-apmixedsys";
reg = <0 0x10209000 0 0x1000>;
--
1.9.1
next prev parent reply other threads:[~2015-11-19 10:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 10:46 [PATCH v2 0/3] Mediatek EFUSE Support Andrew-CT Chen
2015-11-19 10:46 ` [PATCH v2 2/3] nvmem: mediatek: Add Mediatek EFUSE driver Andrew-CT Chen
[not found] ` <1447930014-19579-3-git-send-email-andrew-ct.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-08 4:52 ` Nicolas Boichat
2015-11-19 10:46 ` Andrew-CT Chen [this message]
[not found] ` <1447930014-19579-4-git-send-email-andrew-ct.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2016-02-10 17:48 ` [PATCH v2 3/3] dts: arm64: Add EFUSE device node Matthias Brugger
[not found] ` <1447930014-19579-1-git-send-email-andrew-ct.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-11-19 10:46 ` [PATCH v2 1/3] dt-bindings: add document of mediatek efuse driver Andrew-CT Chen
2015-11-20 15:40 ` Rob Herring
2015-12-14 4:27 ` [PATCH v2 0/3] Mediatek EFUSE Support Daniel Kurtz
2015-12-14 10:07 ` Srinivas Kandagatla
2016-01-21 9:33 ` Matthias Brugger
[not found] ` <56A0A5E1.5050105-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-21 14:32 ` Srinivas Kandagatla
2016-01-21 14:46 ` Matthias Brugger
2016-01-21 14:49 ` Srinivas Kandagatla
2016-02-01 10:23 ` 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=1447930014-19579-4-git-send-email-andrew-ct.chen@mediatek.com \
--to=andrew-ct.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=maxime.ripard@free-electrons.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=srinivas.kandagatla@linaro.org \
--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).