public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Nick Xie <nick@khadas.com>
To: neil.armstrong@linaro.org, khilman@baylibre.com,
	jbrunet@baylibre.com, martin.blumenstingl@googlemail.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org
Cc: krzk+dt@kernel.org, robh@kernel.org, conor+dt@kernel.org,
	xieqinick@gmail.com, Nick Xie <nick@khadas.com>
Subject: [PATCH 5/6] arm64: dts: amlogic: meson-s4: add internal SARADC controller
Date: Fri, 23 Jan 2026 10:22:57 +0800	[thread overview]
Message-ID: <20260123022258.136448-6-nick@khadas.com> (raw)
In-Reply-To: <20260123022258.136448-1-nick@khadas.com>

Add the SARADC (Successive Approximation Register ADC) controller
node to the Meson S4 SoC dtsi.

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 b1d66054a6e87..cd768f9f4db80 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-g12a-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



  parent reply	other threads:[~2026-01-23  2:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23  2:22 [PATCH 0/6] arm64: dts: amlogic: meson-s4-khadas-vim1s: enable LEDs, Keys and Bluetooth Nick Xie
2026-01-23  2:22 ` [PATCH 1/6] arm64: dts: amlogic: meson-s4: add UART_A node Nick Xie
2026-02-26 21:26   ` Martin Blumenstingl
2026-01-23  2:22 ` [PATCH 2/6] arm64: dts: amlogic: meson-s4-s905y4-khadas-vim1s: enable bluetooth Nick Xie
2026-02-26 21:28   ` Martin Blumenstingl
2026-01-23  2:22 ` [PATCH 3/6] arm64: dts: amlogic: meson-s4-s905y4-khadas-vim1s: add PWM LED support Nick Xie
2026-02-26 21:31   ` Martin Blumenstingl
2026-01-23  2:22 ` [PATCH 4/6] arm64: dts: amlogic: meson-s4-s905y4-khadas-vim1s: add POWER key support Nick Xie
2026-02-26 21:32   ` Martin Blumenstingl
2026-01-23  2:22 ` Nick Xie [this message]
2026-02-26 21:49   ` [PATCH 5/6] arm64: dts: amlogic: meson-s4: add internal SARADC controller Martin Blumenstingl
2026-01-23  2:22 ` [PATCH 6/6] arm64: dts: amlogic: meson-s4-s905y4-khadas-vim1s: add Function key support Nick Xie
2026-02-26 21:52   ` 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=20260123022258.136448-6-nick@khadas.com \
    --to=nick@khadas.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neil.armstrong@linaro.org \
    --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