Enable I2C2 on UNIHIKER M10 V1.2

Enable the onboard I2C2 controller at 400 kHz. The rk3308.dtsi pinmux provides GPIO2_A2/A3. This common board preparation is independent of the pending touchscreen device binding and driver.

Changes since v1:
- Normalize author/sender identity and preserve it in the patch body.
- Recheck ordinary and strict checkpatch and the DTS schemas.

Mizuno Miotsuki (1):
arm64: dts: rockchip: Enable I2C2 on UNIHIKER M10 V1.2

 arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts | 5 +++++
 1 file changed, 5 insertions(+)

base-commit: ae965b9856f033145e292b0c29082a26bcc45efd

2.56.0

From: Mizuno Miotsuki <[email protected]>

The onboard resistive touchscreen controller is connected to I2C2. Enable the controller at the tested 400 kHz bus frequency. Its GPIO2_A2 and GPIO2_A3 pinmux is provided by rk3308.dtsi.

Keep the bus enablement separate from the touchscreen device node so it can be reviewed without depending on the pending NS2009 binding and driver. The controller-only configuration was booted on M10 V1.2 with no NS2009 device instantiated.

---
 arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts | 5 +++++
 1 file changed, 5 insertions(+)

index 270ea970c95a..0c03f118378a 100644
@@ -131,6 +131,11 @@ &emmc {
 	status = "okay";
 };
 
+&i2c2 {
+	clock-frequency = <400000>;
+	status = "okay";
+};
+
 &io_domains {
 	vccio0-supply = <&vcc_io>;
 	vccio1-supply = <&vcc_io>;

2.56.0