From: Christopher Obbard <chris.obbard@collabora.com>
To: Shreeya Patel <shreeya.patel@collabora.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
heiko@sntech.de
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH] arm64: dts: rockchip: Add RTC support for RK3588
Date: Tue, 04 Apr 2023 13:03:07 +0100 [thread overview]
Message-ID: <b1c27c7499660d0601927e8fdc5e9b1f6c691e57.camel@collabora.com> (raw)
In-Reply-To: <20230404115802.33693-1-shreeya.patel@collabora.com>
Hi Shreeya,
On Tue, 2023-04-04 at 17:28 +0530, Shreeya Patel wrote:
> Add DT node to enable RTC support on RK3588 board.
>
> Signed-off-by: Shreeya Patel <shreeya.patel@collabora.com>
nit: It'd be great to make the subject something more descriptive about the supported hardware, since this patch doesn't enable the RTC for _all_ RK3588 boards your subject could be a bit misleading.
Something like "arm64: dts: rockchip: Enable RTC support for Rock 5B" could be better.
Reviewed-by: Christopher Obbard <chris.obbard@collabora.com>
> ---
> .../boot/dts/rockchip/rk3588-rock-5b.dts | 27 +++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts b/arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts
> index 95805cb0adfa..a32bfa8d914a 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts
> @@ -27,6 +27,31 @@ vcc5v0_sys: vcc5v0-sys-regulator {
> };
> };
>
> +&i2c6 {
> + status = "okay";
> +
> + hym8563: hym8563@51 {
> + compatible = "haoyu,hym8563";
> + reg = <0x51>;
> + #clock-cells = <0>;
> + clock-frequency = <32768>;
> + clock-output-names = "hym8563";
> + pinctrl-names = "default";
> + pinctrl-0 = <&hym8563_int>;
> + interrupt-parent = <&gpio0>;
> + interrupts = <RK_PB0 IRQ_TYPE_LEVEL_LOW>;
> + wakeup-source;
> + };
> +};
> +
> +&pinctrl {
> + hym8563 {
> + hym8563_int: hym8563-int {
> + rockchip,pins = <0 RK_PB0 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> + };
> +};
> +
> &sdhci {
> bus-width = <8>;
> no-sdio;
> @@ -42,3 +67,5 @@ &uart2 {
> pinctrl-0 = <&uart2m0_xfer>;
> status = "okay";
> };
> +
> +
> --
> 2.30.2
prev parent reply other threads:[~2023-04-04 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 11:58 Shreeya Patel
2023-04-04 12:03 ` Christopher Obbard [this message]
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=b1c27c7499660d0601927e8fdc5e9b1f6c691e57.camel@collabora.com \
--to=chris.obbard@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=shreeya.patel@collabora.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®