From: Fabien Parent <fparent@baylibre.com>
To: linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org
Cc: matthias.bgg@gmail.com, robh+dt@kernel.org, pmeerw@pmeerw.net,
lars@metafoo.de, knaack.h@gmx.de, jic23@kernel.org,
Fabien Parent <fparent@baylibre.com>
Subject: [PATCH 2/2] arm64: dts: mediatek: mt8516: add auxadc node
Date: Mon, 12 Oct 2020 22:52:18 +0200 [thread overview]
Message-ID: <20201012205218.3010868-2-fparent@baylibre.com> (raw)
In-Reply-To: <20201012205218.3010868-1-fparent@baylibre.com>
Add node for the auxadc IP. The IP is compatible with the one found
in MT8173 SoC.
Signed-off-by: Fabien Parent <fparent@baylibre.com>
---
arch/arm64/boot/dts/mediatek/mt8516.dtsi | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8516.dtsi b/arch/arm64/boot/dts/mediatek/mt8516.dtsi
index 89af661e7f63..943c426e9aaf 100644
--- a/arch/arm64/boot/dts/mediatek/mt8516.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt8516.dtsi
@@ -470,5 +470,15 @@ usb0_port: usb-phy@11110800 {
#phy-cells = <1>;
};
};
+
+ auxadc: adc@11003000 {
+ compatible = "mediatek,mt8516-auxadc",
+ "mediatek,mt8173-auxadc";
+ reg = <0 0x11003000 0 0x1000>;
+ clocks = <&topckgen CLK_TOP_AUX_ADC>;
+ clock-names = "main";
+ #io-channel-cells = <1>;
+ status = "disabled";
+ };
};
};
--
2.28.0
next prev parent reply other threads:[~2020-10-12 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 20:52 [PATCH 1/2] dt-bindings: iio: adc: auxadc: add doc for MT8516 SoC Fabien Parent
2020-10-12 20:52 ` Fabien Parent [this message]
2020-10-13 6:01 ` [PATCH 2/2] arm64: dts: mediatek: mt8516: add auxadc node Matthias Brugger
2020-10-13 9:06 ` Fabien Parent
2020-10-13 15:29 ` Matthias Brugger
2020-10-19 10:21 ` Matthias Brugger
2020-10-13 6:00 ` [PATCH 1/2] dt-bindings: iio: adc: auxadc: add doc for MT8516 SoC Matthias Brugger
2020-10-18 10:11 ` Jonathan Cameron
2020-10-13 17:22 ` Rob Herring
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=20201012205218.3010868-2-fparent@baylibre.com \
--to=fparent@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).