The Linux Kernel Mailing List
 help / color / mirror / Atom feed
* [PATCH 0/4] arm64: dts: allwinner: Add KickPi K5C
@ 2026-11-20  7:22 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
                   ` (3 more replies)
  0 siblings, 4 replies; 6+ messages in thread
From: Rajan Yadav via B4 Relay @ 2026-11-20  7:22 UTC (permalink / raw)
  To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Chen-Yu Tsai,
	Jernej Skrabec, Samuel Holland, Maxime Ripard
  Cc: devicetree, linux-kernel, linux-arm-kernel, linux-sunxi,
	Andre Przywara, Paul Kocialkowski, Rajan Yadav

Andre asked [1] to get the device tree for the KickPi K5C upstream and
to work with Paul on it. Paul, I have not heard back from you yet [2], so
here is my version; I am happy to rework it with your input, and a review
or a test on your board would be very welcome.

The KickPi K5C is a single board computer with an Allwinner A133. This
series adds a vendor prefix for KickPi (patch 1), the board compatible
(patch 2), a pin group for I2C3 on PH12/PH13, where the board's RTC sits
(patch 3), and the board device tree (patch 4). It is based on
sunxi/for-next, which has the A100 CPU thermal trips.

A correction to my mail of 18 November [2]: I wrote that I do not have
the board schematic. That was wrong. KickPi publishes the V1.3 schematic
on its documentation site; the regulators and pins in patch 4 follow it
and were checked against the vendor's device tree and on the board.

The vendor prefix uses the company name that KickPi gives on its own
documentation site and as the registered owner of the KICKPI trademark
(Shenzhen Kickpi Digital Technology Co., Ltd., US registration
7747802 [4]). KickPi confirmed this name and the "kickpi" prefix by
e-mail, and their engineers would like to follow the review; I will send
them the link to this thread.

Patch 4 describes only what I could verify on the board. Left out for
now, with the reason in the commit message: Ethernet (the PHY driver is
not in mainline yet), the Wi-Fi/BT module (no mainline driver, and its
SDIO card did not come up after a cold boot in my tests), USB data on
the USB-C port (not tested) and the RTC alarm interrupt (on PB8; it will
follow once fully tested). The CPU uses the A100 OPP table, like the
other A133 boards; once the A133 speed grade series [3] is merged, I
will send a one-line patch to switch the K5C to the A133 table.

Testing (KickPi K5C, PCB V1.3, powered from a PC's USB port through the
USB-C connector; sunxi/for-next plus "cpufreq: sun50i: Handle boards
with the allwinner,sun50i-a133 compatible" [5], which is applied to the
cpufreq tree and in linux-next; without it cpufreq does not start on
this board, but there is no build dependency):
- dtbs_check W=1 adds no warning (only the existing /soc one from
  sun50i-a100.dtsi), also on linux-next; dt_binding_check, checkpatch
  --strict and dt-check-style (relaxed: clean; strict: only property
  names defined by existing bindings); each patch builds on its own
- PMIC: every enabled rail read back from the AXP registers matches the
  device tree; unused rails are off; DCDC2/3 dual phase confirmed
- eMMC: HS200, 8-bit, 150 MHz; two full reads of the 15.6 GB device give
  the same checksum
- SD card: 256 MB written, read back after dropping caches, identical
- USB-A: the on-board GL852G hub enumerates; a USB stick reads back
  identically at high speed
- RTC: time set and read back, kept across reboots (no backup battery
  is fitted on my board, so it is lost on power-off)
- status LED: lights up when switched on and blinks with the heartbeat
  trigger
- cpufreq: every OPP runs at the expected clock and PMIC voltage; the
  90 C passive and 110 C critical trips are in place
- 30 warm reboots and 3 cold boots of this version, each checked (eMMC
  HS200, SD, USB hub, RTC, LED, cpufreq, thermal trips)
- 10034 random cpufreq transitions under load: every OPP ran at the
  expected clock and PMIC voltage
- soaks of 1 and 3 hours with full load on all four cores and, in
  parallel, repeated eMMC reads, SD card write/read-back and USB stick
  reads (477 passes each): no mismatch, no I/O error, no new kernel
  warning; without a heatsink the CPU sits at the 90 C passive trip
  and is throttled by one step, never near the 110 C critical trip
- the RTC kept time to within 1 s over 3 hours

How this was made (Documentation/process/generated-content.rst): I used
Claude Code (Anthropic, Claude Opus 5.5) throughout. It used the board
schematic, KickPi's documentation and the vendor device tree as sources
of hardware facts, compared the existing A133 board files for style,
drafted the device tree, the binding changes and all commit messages,
and wrote the test scripts. No text or code was copied from vendor
sources. I reviewed every patch and ran the tests on my board myself,
and I take responsibility for the series.

[1] https://lore.kernel.org/all/d4d89cf9-884d-424b-927d-5b6692f50327@arm.com/
[2] https://lore.kernel.org/all/CANxy8yTA7Nqmggk=qn7tCnXn50vS2ceHdZYZC0_OancmZhnKcg@mail.gmail.com/
[3] https://lore.kernel.org/all/20261118-a133-series-v2-0-8bcec9c9aadf@gmail.com/
[4] https://tsdr.uspto.gov/statusview/sn98032871
[5] https://lore.kernel.org/all/20261104-a133-fix-v1-1-d0b5ad3d4c5d@gmail.com/

---
Rajan Yadav (4):
      dt-bindings: vendor-prefixes: Add Shenzhen Kickpi Digital Technology
      dt-bindings: arm: sunxi: Add KickPi K5C
      arm64: dts: allwinner: a100: Add I2C3 pins on PH12/PH13
      arm64: dts: allwinner: a133: Add KickPi K5C

 Documentation/devicetree/bindings/arm/sunxi.yaml   |   5 +
 .../devicetree/bindings/vendor-prefixes.yaml       |   2 +
 arch/arm64/boot/dts/allwinner/Makefile             |   1 +
 arch/arm64/boot/dts/allwinner/sun50i-a100.dtsi     |   6 +
 .../boot/dts/allwinner/sun50i-a133-kickpi-k5c.dts  | 228 +++++++++++++++++++++
 5 files changed, 242 insertions(+)
---
base-commit: 03b3355ed7a39b4416f0d0a39061479b1aa13196
change-id: 20261120-k5c-dt-v1-387e65a841c4

Best regards,
--  
Rajan Yadav <rajanyadav0307@gmail.com>



^ permalink raw reply	[flat|nested] 6+ messages in thread

* [PATCH 1/4] dt-bindings: vendor-prefixes: Add Shenzhen Kickpi Digital Technology
  2026-11-20  7:22 [PATCH 0/4] arm64: dts: allwinner: Add KickPi K5C Rajan Yadav via B4 Relay
@ 2026-11-20  7:22 ` 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
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 6+ messages in thread
From: Rajan Yadav via B4 Relay @ 2026-11-20  7:22 UTC (permalink / raw)
  To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Chen-Yu Tsai,
	Jernej Skrabec, Samuel Holland, Maxime Ripard
  Cc: devicetree, linux-kernel, linux-arm-kernel, linux-sunxi,
	Andre Przywara, Paul Kocialkowski, Rajan Yadav

From: Rajan Yadav <rajanyadav0307@gmail.com>

Shenzhen Kickpi Digital Technology Co., Ltd. makes single board
computers under the KickPi name, such as the KickPi K5C with an
Allwinner A133 SoC. Add a vendor prefix for them.

The company name is the one KickPi uses on its documentation site
(doc.kickpi.com) and as the registered owner of the KICKPI trademark
(US registration 7747802); their e-mail and web domain is kickpi.com.

Claude Code (Anthropic) drafted this change and its message; I
reviewed it and checked it with dt_binding_check.

Link: https://www.kickpi.com/
Signed-off-by: Rajan Yadav <rajanyadav0307@gmail.com>
---
 Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
index 5471a06f93f..a67f9c1c896 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -919,6 +919,8 @@ patternProperties:
     description: Keymile GmbH
   "^khadas,.*":
     description: Khadas
+  "^kickpi,.*":
+    description: Shenzhen Kickpi Digital Technology Co., Ltd.
   "^kiebackpeter,.*":
     description: Kieback & Peter GmbH
   "^kinetic,.*":

-- 
2.34.1



^ permalink raw reply related	[flat|nested] 6+ messages in thread

* [PATCH 2/4] dt-bindings: arm: sunxi: Add KickPi K5C
  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 ` 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  7:22 ` [PATCH 4/4] arm64: dts: allwinner: a133: Add KickPi K5C Rajan Yadav via B4 Relay
  3 siblings, 0 replies; 6+ messages in thread
From: Rajan Yadav via B4 Relay @ 2026-11-20  7:22 UTC (permalink / raw)
  To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Chen-Yu Tsai,
	Jernej Skrabec, Samuel Holland, Maxime Ripard
  Cc: devicetree, linux-kernel, linux-arm-kernel, linux-sunxi,
	Andre Przywara, Paul Kocialkowski, Rajan Yadav

From: Rajan Yadav <rajanyadav0307@gmail.com>

The KickPi K5C is a single board computer with an Allwinner A133 SoC,
2 GB of DDR3 DRAM, eMMC, an SD card slot, Gigabit Ethernet, a Wi-Fi/BT
module, USB host ports and a USB-C OTG port.

Add its compatible. Like the Teclast P80, it names the SoC as
allwinner,sun50i-a133.

Claude Code (Anthropic) drafted this change and its message; I
reviewed it and checked it with dt_binding_check.

Signed-off-by: Rajan Yadav <rajanyadav0307@gmail.com>
---
 Documentation/devicetree/bindings/arm/sunxi.yaml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/arm/sunxi.yaml b/Documentation/devicetree/bindings/arm/sunxi.yaml
index 7da84e2de74..b21205f327f 100644
--- a/Documentation/devicetree/bindings/arm/sunxi.yaml
+++ b/Documentation/devicetree/bindings/arm/sunxi.yaml
@@ -405,6 +405,11 @@ properties:
           - const: jesurun,q5
           - const: allwinner,sun4i-a10
 
+      - description: KickPi K5C
+        items:
+          - const: kickpi,k5c
+          - const: allwinner,sun50i-a133
+
       - description: Lamobo R1
         items:
           - const: lamobo,lamobo-r1

-- 
2.34.1



^ permalink raw reply related	[flat|nested] 6+ messages in thread

* [PATCH 3/4] arm64: dts: allwinner: a100: Add I2C3 pins on PH12/PH13
  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 ` Rajan Yadav via B4 Relay
  2026-11-20 16:55   ` Andre Przywara
  2026-11-20  7:22 ` [PATCH 4/4] arm64: dts: allwinner: a133: Add KickPi K5C Rajan Yadav via B4 Relay
  3 siblings, 1 reply; 6+ messages in thread
From: Rajan Yadav via B4 Relay @ 2026-11-20  7:22 UTC (permalink / raw)
  To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Chen-Yu Tsai,
	Jernej Skrabec, Samuel Holland, Maxime Ripard
  Cc: devicetree, linux-kernel, linux-arm-kernel, linux-sunxi,
	Andre Przywara, Paul Kocialkowski, Rajan Yadav

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.

Signed-off-by: Rajan Yadav <rajanyadav0307@gmail.com>
---
 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";

-- 
2.34.1



^ permalink raw reply related	[flat|nested] 6+ messages in thread

* [PATCH 4/4] arm64: dts: allwinner: a133: Add KickPi K5C
  2026-11-20  7:22 [PATCH 0/4] arm64: dts: allwinner: Add KickPi K5C Rajan Yadav via B4 Relay
                   ` (2 preceding siblings ...)
  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  7:22 ` Rajan Yadav via B4 Relay
  3 siblings, 0 replies; 6+ messages in thread
From: Rajan Yadav via B4 Relay @ 2026-11-20  7:22 UTC (permalink / raw)
  To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Chen-Yu Tsai,
	Jernej Skrabec, Samuel Holland, Maxime Ripard
  Cc: devicetree, linux-kernel, linux-arm-kernel, linux-sunxi,
	Andre Przywara, Paul Kocialkowski, Rajan Yadav

From: Rajan Yadav <rajanyadav0307@gmail.com>

The KickPi K5C is a single board computer with an Allwinner A133 SoC.
Mainline Linux has no support for it yet; its factory firmware runs a
vendor Linux 4.9 kernel. Add a device tree for PCB version V1.3, which
has:
- 2 GB DDR3 DRAM, 8-bit eMMC (HS200) and a micro SD card slot
- an X-Powers AXP707 PMIC, which drives VDD-CPU from DCDC2 and DCDC3
  in dual phase mode
- a HYM8563 RTC on I2C3 (PH12/PH13)
- power input through a 12 V DC jack or the USB-C port (5 V)
- two USB-A ports behind an on-board USB hub on USB1, whose power
  switch is enabled by PL8
- a blue status LED on PL10
- the debug UART on PB9/PB10

The regulator assignment and the pins come from the board schematic
(V1.3) and were checked against the vendor's device tree and on the
board. The pin bank supplies are the same as on the Baijie HelperBoard
A133. All tests were done with the board powered through the USB-C
port.

Mainline has no binding for the AXP707. Its chip ID register reads 0x51,
which U-Boot's AXP803 code accepts, it works with the AXP803 driver, and
the vendor device tree also describes it as an AXP803, so the PMIC node
uses the AXP803 compatible.

Not described yet:
- Ethernet: the board has a Maxio MAE0621A PHY, which needs a driver
  that is not in mainline yet
- the Wi-Fi/BT module (VS6621S40, Seekwave SWT6621S) on MMC1: there is
  no mainline driver for it, and in my tests its SDIO card did not come
  up after a cold boot, so the slot is left out until that is understood
- USB data on the USB-C port (USB0): the vendor's firmware uses it as
  a peripheral port, but I could not test that yet
- the RTC alarm interrupt on PB8: first tests pass, and it will follow
  in a separate patch after more testing
- display, camera, audio, the IR receiver, the fan header and the
  battery connector

The CPU uses the A100 OPP table, like the other A133 boards today.

Claude Code (Anthropic) drafted this device tree and its message from
the schematic, KickPi's documentation, the vendor device tree (as a
reference for values only) and my board measurements; I reviewed it
and tested it on a KickPi K5C.

Suggested-by: Andre Przywara <andre.przywara@arm.com>
Link: https://lore.kernel.org/all/d4d89cf9-884d-424b-927d-5b6692f50327@arm.com/
Signed-off-by: Rajan Yadav <rajanyadav0307@gmail.com>
---
 arch/arm64/boot/dts/allwinner/Makefile             |   1 +
 .../boot/dts/allwinner/sun50i-a133-kickpi-k5c.dts  | 228 +++++++++++++++++++++
 2 files changed, 229 insertions(+)

diff --git a/arch/arm64/boot/dts/allwinner/Makefile b/arch/arm64/boot/dts/allwinner/Makefile
index da39f02252d..0176de509fb 100644
--- a/arch/arm64/boot/dts/allwinner/Makefile
+++ b/arch/arm64/boot/dts/allwinner/Makefile
@@ -25,6 +25,7 @@ dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-teres-i.dtb
 dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h64-remix-mini-pc.dtb
 dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a100-allwinner-perf1.dtb
 dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a133-helperboard.dtb
+dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a133-kickpi-k5c.dtb
 dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a133-liontron-h-a133l.dtb
 dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a133-teclast-p80.dtb
 dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-bananapi-m2-plus.dtb
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a133-kickpi-k5c.dts b/arch/arm64/boot/dts/allwinner/sun50i-a133-kickpi-k5c.dts
new file mode 100644
index 00000000000..ce977e9edbd
--- /dev/null
+++ b/arch/arm64/boot/dts/allwinner/sun50i-a133-kickpi-k5c.dts
@@ -0,0 +1,228 @@
+// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
+/*
+ * Copyright (c) 2026 Rajan Yadav <rajanyadav0307@gmail.com>
+ */
+
+/dts-v1/;
+
+#include "sun50i-a100.dtsi"
+#include "sun50i-a100-cpu-opp.dtsi"
+
+#include <dt-bindings/gpio/gpio.h>
+#include <dt-bindings/interrupt-controller/irq.h>
+#include <dt-bindings/leds/common.h>
+
+/{
+	model = "KickPi K5C";
+	compatible = "kickpi,k5c", "allwinner,sun50i-a133";
+
+	aliases {
+		serial0 = &uart0;
+	};
+
+	chosen {
+		stdout-path = "serial0:115200n8";
+	};
+
+	leds {
+		compatible = "gpio-leds";
+
+		led {
+			function = LED_FUNCTION_STATUS;
+			color = <LED_COLOR_ID_BLUE>;
+			gpios = <&r_pio 0 10 GPIO_ACTIVE_HIGH>; /* PL10 */
+		};
+	};
+
+	reg_usb1_vbus: regulator-usb1-vbus {
+		/* USB-A port power switch, also powers the on-board USB hub */
+		compatible = "regulator-fixed";
+		enable-active-high;
+		gpio = <&r_pio 0 8 GPIO_ACTIVE_HIGH>; /* PL8 */
+		regulator-min-microvolt = <5000000>;
+		regulator-max-microvolt = <5000000>;
+		regulator-name = "usb1-vbus";
+		vin-supply = <&reg_vcc5v>;
+	};
+
+	reg_vcc5v: regulator-vcc5v {
+		/* 5V rail, powered from the USB-C port or the 12V DC jack */
+		compatible = "regulator-fixed";
+		regulator-always-on;
+		regulator-min-microvolt = <5000000>;
+		regulator-max-microvolt = <5000000>;
+		regulator-name = "vcc-5v";
+	};
+};
+
+&cpu0 {
+	cpu-supply = <&reg_dcdc2>;
+};
+
+&ehci1 {
+	status = "okay";
+};
+
+&i2c3 {
+	pinctrl-0 = <&i2c3_ph_pins>;
+	pinctrl-names = "default";
+
+	status = "okay";
+
+	rtc@51 {
+		compatible = "haoyu,hym8563";
+		reg = <0x51>;
+		#clock-cells = <0>;
+	};
+};
+
+&mmc0 {
+	bus-width = <4>;
+	cd-gpios = <&pio 5 6 GPIO_ACTIVE_LOW>; /* PF6 */
+	disable-wp;
+	vmmc-supply = <&reg_dcdc1>;
+
+	status = "okay";
+};
+
+&mmc2 {
+	bus-width = <8>;
+	cap-mmc-hw-reset;
+	mmc-ddr-1_8v;
+	mmc-hs200-1_8v;
+	non-removable;
+	vmmc-supply = <&reg_dcdc1>;
+	vqmmc-supply = <&reg_eldo1>;
+
+	status = "okay";
+};
+
+&ohci1 {
+	status = "okay";
+};
+
+&pio {
+	vcc-pb-supply = <&reg_dcdc1>;
+	vcc-pc-supply = <&reg_eldo1>;
+	vcc-pd-supply = <&reg_dcdc1>;
+	vcc-pe-supply = <&reg_dldo2>;
+	vcc-pf-supply = <&reg_dcdc1>;
+	vcc-pg-supply = <&reg_dldo1>;
+	vcc-ph-supply = <&reg_dcdc1>;
+};
+
+&r_i2c0 {
+	status = "okay";
+
+	axp803: pmic@34 {
+		compatible = "x-powers,axp803";
+		reg = <0x34>;
+		interrupt-parent = <&r_intc>;
+		interrupts = <0 IRQ_TYPE_LEVEL_LOW>;
+	};
+};
+
+#include "axp803.dtsi"
+
+&reg_aldo1 {
+	/* AVCC, PLL and DRAM 1.8V */
+	regulator-always-on;
+	regulator-min-microvolt = <1800000>;
+	regulator-max-microvolt = <1800000>;
+	regulator-name = "vcc-pll-avcc";
+};
+
+/* ALDO2 is for LPDDR and not used with the DDR3 on this board */
+
+&reg_aldo3 {
+	/*
+	 * Supply of the PL pin bank. It is not given to r_pio as
+	 * vcc-pl-supply: the PMIC is reached through PL0/PL1, so r_pio and
+	 * the PMIC would each wait for the other and the boot stops.
+	 */
+	regulator-always-on;
+	regulator-min-microvolt = <3300000>;
+	regulator-max-microvolt = <3300000>;
+	regulator-name = "vcc-pl";
+};
+
+&reg_dcdc1 {
+	/* SoC I/O, USB analog, eMMC and SD card */
+	regulator-always-on;
+	regulator-min-microvolt = <3300000>;
+	regulator-max-microvolt = <3300000>;
+	regulator-name = "vcc-3v3";
+};
+
+&reg_dcdc2 {
+	regulator-always-on;
+	regulator-min-microvolt = <810000>;
+	regulator-max-microvolt = <1200000>;
+	regulator-name = "vdd-cpux";
+};
+
+/* DCDC3 runs in dual phase with DCDC2 for VDD-CPUX and has no node */
+
+&reg_dcdc4 {
+	/* VDD-SYS, also used as VDD-USB */
+	regulator-always-on;
+	regulator-min-microvolt = <950000>;
+	regulator-max-microvolt = <950000>;
+	regulator-name = "vdd-sys";
+};
+
+&reg_dcdc5 {
+	/* DDR3 */
+	regulator-always-on;
+	regulator-min-microvolt = <1500000>;
+	regulator-max-microvolt = <1500000>;
+	regulator-name = "vcc-dram";
+};
+
+/* DCDC6 is not connected */
+&reg_dcdc6 {
+	status = "disabled";
+};
+
+&reg_dldo1 {
+	regulator-min-microvolt = <1800000>;
+	regulator-max-microvolt = <1800000>;
+	regulator-name = "vcc-pg";
+};
+
+&reg_dldo2 {
+	regulator-min-microvolt = <1800000>;
+	regulator-max-microvolt = <1800000>;
+	regulator-name = "vcc-pe";
+};
+
+&reg_eldo1 {
+	regulator-min-microvolt = <1800000>;
+	regulator-max-microvolt = <1800000>;
+	regulator-name = "vcc-pc";
+};
+
+&reg_fldo1 {
+	/* VDD-CPUS */
+	regulator-always-on;
+	regulator-min-microvolt = <900000>;
+	regulator-max-microvolt = <900000>;
+	regulator-name = "vdd-cpus";
+};
+
+&uart0 {
+	pinctrl-0 = <&uart0_pb_pins>;
+	pinctrl-names = "default";
+
+	status = "okay";
+};
+
+&usb_power_supply {
+	status = "okay";
+};
+
+&usbphy {
+	usb1_vbus-supply = <&reg_usb1_vbus>;
+
+	status = "okay";
+};

-- 
2.34.1



^ permalink raw reply related	[flat|nested] 6+ messages in thread

* Re: [PATCH 3/4] arm64: dts: allwinner: a100: Add I2C3 pins on PH12/PH13
  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
  0 siblings, 0 replies; 6+ messages in thread
From: Andre Przywara @ 2026-11-20 16:55 UTC (permalink / raw)
  To: Rajan Yadav via B4 Relay
  Cc: rajanyadav0307, Rob Herring, Krzysztof Kozlowski, Conor Dooley,
	Chen-Yu Tsai, Jernej Skrabec, Samuel Holland, Maxime Ripard,
	devicetree, linux-kernel, linux-arm-kernel, linux-sunxi,
	Paul Kocialkowski

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";
> 


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2026-11-20 16:55 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2026-11-20  7:22 ` [PATCH 4/4] arm64: dts: allwinner: a133: Add KickPi K5C Rajan Yadav via B4 Relay

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox