From: Andre Przywara <andre.przywara@arm.com>
To: Rajan Yadav via B4 Relay <devnull+rajanyadav0307.gmail.com@kernel.org>
Cc: rajanyadav0307@gmail.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chen-Yu Tsai <wens@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Maxime Ripard <mripard@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev,
Paul Kocialkowski <paulk@sys-base.io>
Subject: Re: [PATCH 3/4] arm64: dts: allwinner: a100: Add I2C3 pins on PH12/PH13
Date: Fri, 20 Nov 2026 17:55:11 +0100 [thread overview]
Message-ID: <20261120175511.70ec8a36@ryzen.lan> (raw)
In-Reply-To: <20261120-k5c-dt-v1-v1-3-d9681df67bc0@gmail.com>
On Fri, 20 Nov 2026 01:22:15 -0600
Rajan Yadav via B4 Relay <devnull+rajanyadav0307.gmail.com@kernel.org>
wrote:
> From: Rajan Yadav <rajanyadav0307@gmail.com>
>
> The I2C3 controller can use PH12 (SCK) and PH13 (SDA). The KickPi K5C
> connects its HYM8563 RTC there.
>
> Add a pin group for them, marked /omit-if-no-ref/ like mmc1_pins, so
> it is only kept in the boards that use it.
>
> Claude Code (Anthropic) drafted this change and its message; I
> reviewed it and tested it on a KickPi K5C.
>
Checked against the manual, and the pinctrl driver (to map the function
number to the pin mux):
> Signed-off-by: Rajan Yadav <rajanyadav0307@gmail.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Cheers,
Andre
> ---
> arch/arm64/boot/dts/allwinner/sun50i-a100.dtsi | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a100.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-a100.dtsi
> index fce91dc2c28..3b53d64f25e 100644
> --- a/arch/arm64/boot/dts/allwinner/sun50i-a100.dtsi
> +++ b/arch/arm64/boot/dts/allwinner/sun50i-a100.dtsi
> @@ -215,6 +215,12 @@ pio: pinctrl@300b000 {
> interrupt-controller;
> #interrupt-cells = <3>;
>
> + /omit-if-no-ref/
> + i2c3_ph_pins: i2c3-ph-pins {
> + pins = "PH12", "PH13";
> + function = "i2c3";
> + };
> +
> mmc0_pins: mmc0-pins {
> pins = "PF0", "PF1", "PF2", "PF3",
> "PF4", "PF5";
>
next prev parent reply other threads:[~2026-11-20 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 7:22 [PATCH 0/4] arm64: dts: allwinner: Add KickPi K5C Rajan Yadav via B4 Relay
2026-11-20 7:22 ` [PATCH 1/4] dt-bindings: vendor-prefixes: Add Shenzhen Kickpi Digital Technology Rajan Yadav via B4 Relay
2026-11-20 7:22 ` [PATCH 2/4] dt-bindings: arm: sunxi: Add KickPi K5C Rajan Yadav via B4 Relay
2026-11-20 7:22 ` [PATCH 3/4] arm64: dts: allwinner: a100: Add I2C3 pins on PH12/PH13 Rajan Yadav via B4 Relay
2026-11-20 16:55 ` Andre Przywara [this message]
2026-11-20 7:22 ` [PATCH 4/4] arm64: dts: allwinner: a133: Add KickPi K5C Rajan Yadav via B4 Relay
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=20261120175511.70ec8a36@ryzen.lan \
--to=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+rajanyadav0307.gmail.com@kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=paulk@sys-base.io \
--cc=rajanyadav0307@gmail.com \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@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