public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Diederik de Haas" <diederik@cknow-tech.com>
To: "Gray Huang" <gray.huang@wesion.com>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.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>, <nick@khadas.com>
Subject: Re: [PATCH v2 2/7] arm64: dts: rockchip: Add HYM8563 RTC for Khadas Edge 2L
Date: Sat, 02 May 2026 12:29:40 +0200	[thread overview]
Message-ID: <DI84CXWVJPXB.1OG0PYJ5L31TX@cknow-tech.com> (raw)
In-Reply-To: <20260429063712.2150938-3-gray.huang@wesion.com>

On Wed Apr 29, 2026 at 8:37 AM CEST, Gray Huang wrote:
> The Khadas Edge 2L uses an on-board HYM8563 RTC connected to
> I2C2. Enable it and expose its 32.768kHz clock output so later
> board-level patches can reference it as the LPO clock source for
> the AP6275P wireless module.
>
> Mark the RTC as a wakeup source as well.
>
> Signed-off-by: Gray Huang <gray.huang@wesion.com>
> ---
>  .../boot/dts/rockchip/rk3576-khadas-edge-2l.dts     | 13 +++++++++++--
>  1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3576-khadas-edge-2l.dts b/arch/arm64/boot/dts/rockchip/rk3576-khadas-edge-2l.dts
> index 5781deae00d9..c85b219fe409 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3576-khadas-edge-2l.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3576-khadas-edge-2l.dts
> @@ -46,8 +46,6 @@ vcc_2v0_pldo_s3: regulator-vcc-2v0-pldo-s3 {
>  		regulator-max-microvolt = <2000000>;
>  		vin-supply = <&vcc_sys>;
>  	};
> -
> -
>  };

You're removing unneeded empty lines (good), but you introduced them in
patch 1 of this series ... thus fix patch 1? That also means you're no
longer adding an unrelated change in this patch.

Cheers,
  Diederik
  
>  &cpu_l0 {
> @@ -431,6 +429,17 @@ regulator-state-mem {
>  	};
>  };
>  
> +&i2c2 {
> +	status = "okay";
> +
> +	hym8563: hym8563@51 {
> +		compatible = "haoyu,hym8563";
> +		reg = <0x51>;
> +		#clock-cells = <0>;
> +		clock-output-names = "hym8563";
> +		wakeup-source;
> +	};
> +};
>  
>  &sdhci {
>  	bus-width = <8>;


  reply	other threads:[~2026-05-02 10:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29  6:37 [PATCH v2 0/7] arm64: dts: rockchip: Add peripheral support for Khadas Edge 2L Gray Huang
2026-04-29  6:37 ` [PATCH v2 1/7] arm64: dts: rockchip: Add PMIC " Gray Huang
2026-04-29  6:37 ` [PATCH v2 2/7] arm64: dts: rockchip: Add HYM8563 RTC " Gray Huang
2026-05-02 10:29   ` Diederik de Haas [this message]
2026-04-29  6:37 ` [PATCH v2 3/7] arm64: dts: rockchip: Add AP6275P wireless support " Gray Huang
2026-04-29  6:37 ` [PATCH v2 4/7] arm64: dts: rockchip: Enable GPU " Gray Huang
2026-04-29  6:37 ` [PATCH v2 5/7] arm64: dts: rockchip: Add HDMI and VOP support " Gray Huang
2026-05-02 17:19   ` Jimmy Hon
2026-04-29  6:37 ` [PATCH v2 6/7] arm64: dts: rockchip: Enable USB " Gray Huang
2026-04-29  6:37 ` [PATCH v2 7/7] arm64: dts: rockchip: Add Bluetooth support " Gray Huang

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=DI84CXWVJPXB.1OG0PYJ5L31TX@cknow-tech.com \
    --to=diederik@cknow-tech.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gray.huang@wesion.com \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=nick@khadas.com \
    --cc=robh@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