From: Nick Xie <nick@khadas.com>
To: neil.armstrong@linaro.org, khilman@baylibre.com,
martin.blumenstingl@googlemail.com, jbrunet@baylibre.com,
krzk+dt@kernel.org, jic23@kernel.org, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org
Cc: linux-iio@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, xieqinick@gmail.com,
Nick Xie <nick@khadas.com>
Subject: [PATCH v1 3/4] arm64: dts: amlogic: meson-s4: add internal SARADC controller
Date: Sat, 28 Feb 2026 14:58:39 +0800 [thread overview]
Message-ID: <20260228065840.702651-4-nick@khadas.com> (raw)
In-Reply-To: <20260228065840.702651-1-nick@khadas.com>
Add the SARADC controller node to the Meson S4 SoC dtsi.
Uses the newly introduced S4-specific compatible string.
Signed-off-by: Nick Xie <nick@khadas.com>
---
arch/arm64/boot/dts/amlogic/meson-s4.dtsi | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-s4.dtsi b/arch/arm64/boot/dts/amlogic/meson-s4.dtsi
index 4a3e9ad82d280..a1c0ef91d7cfb 100644
--- a/arch/arm64/boot/dts/amlogic/meson-s4.dtsi
+++ b/arch/arm64/boot/dts/amlogic/meson-s4.dtsi
@@ -77,6 +77,20 @@ pwrc: power-controller {
};
};
+ saradc: adc@fe026000 {
+ compatible = "amlogic,meson-s4-saradc",
+ "amlogic,meson-saradc";
+ reg = <0x0 0xfe026000 0x0 0x48>;
+ #io-channel-cells = <1>;
+ interrupts = <GIC_SPI 181 IRQ_TYPE_EDGE_RISING>;
+ clocks = <&xtal>,
+ <&clkc_periphs CLKID_SAR_ADC>,
+ <&clkc_periphs CLKID_SARADC>,
+ <&clkc_periphs CLKID_SARADC_SEL>;
+ clock-names = "clkin", "core", "adc_clk", "adc_sel";
+ status = "disabled";
+ };
+
soc {
compatible = "simple-bus";
#address-cells = <2>;
--
2.34.1
next prev parent reply other threads:[~2026-02-28 6:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 6:58 [PATCH v1 0/4] iio: adc: meson-saradc: add support for Meson S4 Nick Xie
2026-02-28 6:58 ` [PATCH v1 1/4] dt-bindings: iio: adc: amlogic,meson-saradc: add S4 compatible Nick Xie
2026-02-28 11:18 ` Krzysztof Kozlowski
2026-02-28 11:20 ` Krzysztof Kozlowski
2026-03-02 11:58 ` Martin Blumenstingl
2026-03-02 13:59 ` Krzysztof Kozlowski
2026-03-02 21:03 ` Martin Blumenstingl
2026-03-03 6:25 ` Krzysztof Kozlowski
2026-02-28 6:58 ` [PATCH v1 2/4] iio: adc: meson-saradc: add support for Meson S4 Nick Xie
2026-03-02 11:50 ` Martin Blumenstingl
2026-02-28 6:58 ` Nick Xie [this message]
2026-03-02 11:50 ` [PATCH v1 3/4] arm64: dts: amlogic: meson-s4: add internal SARADC controller Martin Blumenstingl
2026-02-28 6:58 ` [PATCH v1 4/4] arm64: dts: amlogic: meson-s4-s905y4-khadas-vim1s: add Function key support Nick Xie
2026-02-28 16:14 ` kernel test robot
2026-03-02 12:00 ` Martin Blumenstingl
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=20260228065840.702651-4-nick@khadas.com \
--to=nick@khadas.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jbrunet@baylibre.com \
--cc=jic23@kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=xieqinick@gmail.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