From: Andre Przywara <andre.przywara@arm.com>
To: Chris Morgan <macroalpha82@gmail.com>
Cc: linux-sunxi@lists.linux.dev, devicetree@vger.kernel.org,
mripard@kernel.org, ryan@testtoast.com, samuel@sholland.org,
jernej.skrabec@gmail.com, wens@csie.org, conor+dt@kernel.org,
krzk+dt@kernel.org, robh@kernel.org,
Chris Morgan <macromorgan@hotmail.com>,
Philippe Simons <simons.philippe@gmail.com>
Subject: Re: [PATCH V3 3/4] arm64: dts: allwinner: h616: Change RG35XX Series from r_rsb to r_i2c
Date: Thu, 11 Jul 2024 10:52:56 +0100 [thread overview]
Message-ID: <20240711105256.61d1f00e@donnerap.manchester.arm.com> (raw)
In-Reply-To: <20240710231718.106894-4-macroalpha82@gmail.com>
On Wed, 10 Jul 2024 18:17:17 -0500
Chris Morgan <macroalpha82@gmail.com> wrote:
Hi,
> From: Chris Morgan <macromorgan@hotmail.com>
>
> Change the Anbernic RG35XX series to use the r_i2c bus for the PMIC
> instead of the r_rsb bus. This is to keep the device tree consistent
> as there are at least 3 devices (the RG35XX-SP, RG28XX, and RG40XX-H)
> that have an external RTC on the r_i2c bus.
The change itself looks alright, but I would like to see some Tested-by:s
from people with those Allwinner Anbernic devices, since the change affects
all of them.
> Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Cheers,
Andre
> ---
> .../boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-2024.dts | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-2024.dts b/arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-2024.dts
> index ee30584b6ad7..e2bbd22bd80a 100644
> --- a/arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-2024.dts
> +++ b/arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-2024.dts
> @@ -201,12 +201,12 @@ &pio {
> vcc-pi-supply = <®_cldo3>;
> };
>
> -&r_rsb {
> +&r_i2c {
> status = "okay";
>
> - axp717: pmic@3a3 {
> + axp717: pmic@34 {
> compatible = "x-powers,axp717";
> - reg = <0x3a3>;
> + reg = <0x34>;
> interrupt-controller;
> #interrupt-cells = <1>;
> interrupt-parent = <&nmi_intc>;
next prev parent reply other threads:[~2024-07-11 9:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 23:17 [PATCH V3 0/4] Add Anbernic RG35XX-SP Chris Morgan
2024-07-10 23:17 ` [PATCH V3 1/4] dt-bindings: arm: sunxi: Add Anbernic RG35XXSP Chris Morgan
2024-07-11 6:35 ` Krzysztof Kozlowski
2024-07-10 23:17 ` [PATCH V3 2/4] arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes Chris Morgan
2024-07-10 23:17 ` [PATCH V3 3/4] arm64: dts: allwinner: h616: Change RG35XX Series from r_rsb to r_i2c Chris Morgan
2024-07-11 9:52 ` Andre Przywara [this message]
2024-07-14 8:48 ` Ryan Walklin
2024-07-10 23:17 ` [PATCH V3 4/4] arm64: dts: allwinner: h700: Add Anbernic RG35XX-SP Chris Morgan
2024-07-11 10:10 ` Andre Przywara
2024-07-11 14:20 ` [PATCH V3 0/4] " Rob Herring (Arm)
2024-07-11 14:44 ` Andre Przywara
2024-08-01 16:25 ` Chen-Yu Tsai
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=20240711105256.61d1f00e@donnerap.manchester.arm.com \
--to=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=ryan@testtoast.com \
--cc=samuel@sholland.org \
--cc=simons.philippe@gmail.com \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).