From: Neil Armstrong <neil.armstrong@linaro.org>
To: xianwei.zhao@amlogic.com, Yiting Deng <yiting.deng@amlogic.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: dts: amlogic: C3: Add RTC controller node
Date: Tue, 22 Jul 2025 12:05:54 +0200 [thread overview]
Message-ID: <4a78f570-62fd-4779-aba2-1c9c558989f2@linaro.org> (raw)
In-Reply-To: <20250717-rtc-c3-node-v1-2-4f9ae059b8e6@amlogic.com>
On 17/07/2025 11:38, Xianwei Zhao via B4 Relay wrote:
> From: Xianwei Zhao <xianwei.zhao@amlogic.com>
>
> Add the RTC controller node for C3 SoC family.
>
> Signed-off-by: Xianwei Zhao <xianwei.zhao@amlogic.com>
> ---
> arch/arm64/boot/dts/amlogic/amlogic-c3.dtsi | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/amlogic/amlogic-c3.dtsi b/arch/arm64/boot/dts/amlogic/amlogic-c3.dtsi
> index cb9ea3ca6ee0..b81bffac7732 100644
> --- a/arch/arm64/boot/dts/amlogic/amlogic-c3.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/amlogic-c3.dtsi
> @@ -53,6 +53,13 @@ xtal: xtal-clk {
> #clock-cells = <0>;
> };
>
> + xtal_32k: xtal-clk-32k {
> + compatible = "fixed-clock";
> + clock-frequency = <32768>;
> + clock-output-names = "xtal_32k";
> + #clock-cells = <0>;
> + };
> +
> sm: secure-monitor {
> compatible = "amlogic,meson-gxbb-sm";
>
> @@ -967,6 +974,15 @@ nand: nand-controller@8d000 {
> clock-names = "core", "device";
> status = "disabled";
> };
> +
> + rtc@9a000 {
> + compatible = "amlogic,c3-rtc",
> + "amlogic,a5-rtc";
> + reg = <0x0 0x9a000 0x0 0x38>;
> + interrupts = <GIC_SPI 131 IRQ_TYPE_EDGE_RISING>;
> + clocks = <&xtal_32k>, <&clkc_periphs CLKID_SYS_RTC>;
> + clock-names = "osc", "sys";
> + };
> };
>
> ethmac: ethernet@fdc00000 {
>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-07-22 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 9:38 [PATCH 0/2] rtc: add amlogic C3 RTC node Xianwei Zhao via B4 Relay
2025-07-17 9:38 ` [PATCH 1/2] dt-bindings: rtc: amlogic,a4-rtc: Add compatible string for C3 Xianwei Zhao via B4 Relay
2025-07-20 23:30 ` Rob Herring (Arm)
2025-07-23 21:44 ` (subset) " Alexandre Belloni
2025-07-17 9:38 ` [PATCH 2/2] arm64: dts: amlogic: C3: Add RTC controller node Xianwei Zhao via B4 Relay
2025-07-22 10:05 ` Neil Armstrong [this message]
2025-09-04 13:28 ` (subset) [PATCH 0/2] rtc: add amlogic C3 RTC node Neil Armstrong
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=4a78f570-62fd-4779-aba2-1c9c558989f2@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=alexandre.belloni@bootlin.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=linux-rtc@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=robh@kernel.org \
--cc=xianwei.zhao@amlogic.com \
--cc=yiting.deng@amlogic.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
all inboxes | Powered by JetHome®