Skip to contentSkip to conversation

Enable dual OV5640 cameras on i.MX8MQ EVK board

PATCH In review Robby Cai 3 participants 7 messages Apr 17 – Apr 30

Subsystems (2)
lore
Share & tools
lore

Robby Cai

author
#0 lore raw

cover Enable dual OV5640 cameras on i.MX8MQ EVK board

This series adds dual-camera support for the i.MX8MQ EVK board.

Patch 1 fixes the MIPI CSI clock configuration in the i.MX8MQ device tree. The previous configuration violated a timing constraint defined in the i.MX8MQ Reference Manual:

"The frequency of clk must be exactly equal to or greater than the RX byte clock coming from the RX DPHY."

This mismatch could lead to unstable operation, observed as intermittent capture failures. The updated clock ratios align with those used in NXP��s downstream BSP and were verified to resolve the issue.

Patch 2 enables full MIPI CSI support and dual OV5640 camera operation on the i.MX8MQ EVK. This includes enabling both CSI controllers and their corresponding MIPI CSI-2 host interfaces, as well as adding two OV5640 sensor nodes on I2C1 and I2C2.

Note:
This series depends on patch [1] currently under review, as well as commit 6d79bb8fd2aa ("media: imx8mq-mipi-csi2: Explicitly release reset").

[1] https://lore.kernel.org/imx/[email protected]/

Robby Cai (2):
arm64: dts: imx8mq: Correct MIPI CSI clocks
arm64: dts: imx8mq-evk: Enable MIPI CSI and dual OV5640 cameras

 arch/arm64/boot/dts/freescale/imx8mq-evk.dts | 149 +++++++++++++++++++
 arch/arm64/boot/dts/freescale/imx8mq.dtsi    |   4 +-
 2 files changed, 151 insertions(+), 2 deletions(-)
Signature · 1 line
2.37.1
author
#1 lore raw

PATCH 1/2 arm64: dts: imx8mq: Correct MIPI CSI clocks

CSI capture may intermittently fail due to mismatched clock rates. The previous configuration violated the timing requirement stated in the i.MX8MQ Reference Manual:

"The frequency of clk must be exactly equal to or greater than the RX
byte clock coming from the RX DPHY."

Update the clock configuration to ensure that the CSI core clock rate is equal to or greater than the incoming DPHY byte clock. The updated clock ratios are consistent with those used in NXP's downstream BSP.

Fixes bcadd5f66c2a ("arm64: dts: imx8mq: add mipi csi phy and csi bridge descriptions")
---
 arch/arm64/boot/dts/freescale/imx8mq.dtsi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm64/boot/dts/freescale/imx8mq.dtsi +2 -2
index 6a25e219832c..165716d08e64 100644
@@ -1377,7 +1377,7 @@ mipi_csi1: csi@30a70000 {
 				assigned-clocks = <&clk IMX8MQ_CLK_CSI1_CORE>,
 				    <&clk IMX8MQ_CLK_CSI1_PHY_REF>,
 				    <&clk IMX8MQ_CLK_CSI1_ESC>;
-				assigned-clock-rates = <266000000>, <333000000>, <66000000>;
+				assigned-clock-rates = <133000000>, <100000000>, <66000000>;
 				assigned-clock-parents = <&clk IMX8MQ_SYS1_PLL_266M>,
 					<&clk IMX8MQ_SYS2_PLL_1000M>,
 					<&clk IMX8MQ_SYS1_PLL_800M>;
@@ -1429,7 +1429,7 @@ mipi_csi2: csi@30b60000 {
 				assigned-clocks = <&clk IMX8MQ_CLK_CSI2_CORE>,
 				    <&clk IMX8MQ_CLK_CSI2_PHY_REF>,
 				    <&clk IMX8MQ_CLK_CSI2_ESC>;
-				assigned-clock-rates = <266000000>, <333000000>, <66000000>;
+				assigned-clock-rates = <133000000>, <100000000>, <66000000>;
 				assigned-clock-parents = <&clk IMX8MQ_SYS1_PLL_266M>,
 					<&clk IMX8MQ_SYS2_PLL_1000M>,
 					<&clk IMX8MQ_SYS1_PLL_800M>;
Signature · 1 line
2.37.1
maintainer
#2 lore raw

Re: [PATCH 1/2] arm64: dts: imx8mq: Correct MIPI CSI clocks

Quoted 9 lines · Robby Cai

CSI capture may intermittently fail due to mismatched clock rates. The previous configuration violated the timing requirement stated in the i.MX8MQ Reference Manual:

"The frequency of clk must be exactly equal to or greater than the RX
byte clock coming from the RX DPHY."

Update the clock configuration to ensure that the CSI core clock rate is equal to or greater than the incoming DPHY byte clock.

You reduce clock, how to make sure it >= ?

Quoted 2 lines

The updated clock
ratios are consistent with those used in NXP's downstream BSP.

"downstream BSP" is not solidate reference for clock rate, it'd better refer to date sheet, dose datasheet require such frequecy

Frank

Quoted 33 lines
Fixes bcadd5f66c2a ("arm64: dts: imx8mq: add mipi csi phy and csi bridge descriptions")
---
 arch/arm64/boot/dts/freescale/imx8mq.dtsi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm64/boot/dts/freescale/imx8mq.dtsi +2 -3
index 6a25e219832c..165716d08e64 100644
@@ -1377,7 +1377,7 @@ mipi_csi1: csi@30a70000 {
 				assigned-clocks = <&clk IMX8MQ_CLK_CSI1_CORE>,
 				    <&clk IMX8MQ_CLK_CSI1_PHY_REF>,
 				    <&clk IMX8MQ_CLK_CSI1_ESC>;
-				assigned-clock-rates = <266000000>, <333000000>, <66000000>;
+				assigned-clock-rates = <133000000>, <100000000>, <66000000>;
 				assigned-clock-parents = <&clk IMX8MQ_SYS1_PLL_266M>,
 					<&clk IMX8MQ_SYS2_PLL_1000M>,
 					<&clk IMX8MQ_SYS1_PLL_800M>;
@@ -1429,7 +1429,7 @@ mipi_csi2: csi@30b60000 {
 				assigned-clocks = <&clk IMX8MQ_CLK_CSI2_CORE>,
 				    <&clk IMX8MQ_CLK_CSI2_PHY_REF>,
 				    <&clk IMX8MQ_CLK_CSI2_ESC>;
-				assigned-clock-rates = <266000000>, <333000000>, <66000000>;
+				assigned-clock-rates = <133000000>, <100000000>, <66000000>;
 				assigned-clock-parents = <&clk IMX8MQ_SYS1_PLL_266M>,
 					<&clk IMX8MQ_SYS2_PLL_1000M>,
 					<&clk IMX8MQ_SYS1_PLL_800M>;
--

2.37.1

author
#3 lore raw

Re: [PATCH 1/2] arm64: dts: imx8mq: Correct MIPI CSI clocks

Quoted 5 lines · Frank Li
Quoted 4 lines · Robby Cai

CSI capture may intermittently fail due to mismatched clock rates. The previous configuration violated the timing requirement stated in the i.MX8MQ Reference Manual:

Quoted 7 lines
Quoted 5 lines

"The frequency of clk must be exactly equal to or greater than the RX
byte clock coming from the RX DPHY."

Update the clock configuration to ensure that the CSI core clock rate is equal to or greater than the incoming DPHY byte clock.

You reduce clock, how to make sure it >= ?

This is a mistake in the commit message. IMX8MQ_CLK_CSIX_PHY_REF refers to the UI clock (clk_ui), not the RX DPHY byte clock. There is no direct >= relationship with the CSI core clock other than the documented bandwidth requirement.

Quoted 8 lines
Quoted 3 lines

The updated clock
ratios are consistent with those used in NXP's downstream BSP.

"downstream BSP" is not solidate reference for clock rate, it'd better refer to date sheet, dose datasheet require such frequecy

Frank

I will revisit the clock assumptions in the next revision.

Regards,
Robby

Quoted 5 lines
Quoted 5 lines
Fixes bcadd5f66c2a ("arm64: dts: imx8mq: add mipi csi phy and csi bridge descriptions")

---

[...]

#4 lore raw

Re: [PATCH 1/2] arm64: dts: imx8mq: Correct MIPI CSI clocks

In reply to Robby Cai
Quoted 10 lines · On piątek, 17 kwietnia 2026 13:01:59 czas środkowoeuropejski letni Robby Cai…

CSI capture may intermittently fail due to mismatched clock rates. The previous configuration violated the timing requirement stated in the i.MX8MQ Reference Manual:

"The frequency of clk must be exactly equal to or greater than the RX
byte clock coming from the RX DPHY."

Update the clock configuration to ensure that the CSI core clock rate is equal to or greater than the incoming DPHY byte clock. The updated clock ratios are consistent with those used in NXP's downstream BSP.

I believe this is a misreading of the docs.

IMX8MQ_CLK_CSIX_PHY_REF refers to the UI pixel clock (clk_ui), not the RX DPHY byte clock. All this change would do is to break streaming with more than 100 Mpixels per second / 1064 Mbps per MIPI lane.

As mentioned in the reference manual:

"The frequency of clk_ui must be such that the data received on the data_out output is greater than or equal to the total bandwidth of the physical MIPI interface. Clk_ui has no relationship requirement with regards to ‘clk’ other than the bandwidth requirement mentioned previously."

Quoted 13 lines
Fixes bcadd5f66c2a ("arm64: dts: imx8mq: add mipi csi phy and csi bridge

descriptions") Cc: [email protected]

---
 arch/arm64/boot/dts/freescale/imx8mq.dtsi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
(quoted diff) +0 -0

b/arch/arm64/boot/dts/freescale/imx8mq.dtsi index
6a25e219832c..165716d08e64 100644

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi1: csi@30a70000 { · line 1377

Quoted 1 line
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -0
@@ -1377,7 +1377,7 @@ mipi_csi1: csi@30a70000 {
 				assigned-clocks = <&clk 

IMX8MQ_CLK_CSI1_CORE>,

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi1: csi@30a70000 { · line 1378

Quoted 1 line
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -0
 				    <&clk 

IMX8MQ_CLK_CSI1_PHY_REF>,

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi1: csi@30a70000 { · line 1380

Quoted 2 lines
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -1
 				    <&clk IMX8MQ_CLK_CSI1_ESC>;
-				assigned-clock-rates = 

<266000000>, <333000000>, <66000000>;

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi1: csi@30a70000 { · line 1380

Quoted 1 line
arch/arm64/boot/dts/freescale/imx8mq.dtsi +1 -0
+				assigned-clock-rates = 

<133000000>, <100000000>, <66000000>;

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi1: csi@30a70000 { · line 1381

Quoted 1 line
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -0
 				assigned-clock-parents = <&clk 

IMX8MQ_SYS1_PLL_266M>,

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi1: csi@30a70000 { · line 1382

Quoted 1 line
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -0
 					<&clk 

IMX8MQ_SYS2_PLL_1000M>,

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi1: csi@30a70000 { · line 1383

Quoted 1 line
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -0
 					<&clk 

IMX8MQ_SYS1_PLL_800M>;

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi2: csi@30b60000 { · line 1429

Quoted 2 lines
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -0
@@ -1429,7 +1429,7 @@ mipi_csi2: csi@30b60000 {
 				assigned-clocks = <&clk 

IMX8MQ_CLK_CSI2_CORE>,

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi2: csi@30b60000 { · line 1430

Quoted 1 line
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -0
 				    <&clk 

IMX8MQ_CLK_CSI2_PHY_REF>,

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi2: csi@30b60000 { · line 1432

Quoted 2 lines
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -1
 				    <&clk IMX8MQ_CLK_CSI2_ESC>;
-				assigned-clock-rates = 

<266000000>, <333000000>, <66000000>;

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi2: csi@30b60000 { · line 1432

Quoted 1 line
arch/arm64/boot/dts/freescale/imx8mq.dtsi +1 -0
+				assigned-clock-rates = 

<133000000>, <100000000>, <66000000>;

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi2: csi@30b60000 { · line 1433

Quoted 1 line
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -0
 				assigned-clock-parents = <&clk 

IMX8MQ_SYS1_PLL_266M>,

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi2: csi@30b60000 { · line 1434

Quoted 1 line
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -0
 					<&clk 

IMX8MQ_SYS2_PLL_1000M>,

arch/arm64/boot/dts/freescale/imx8mq.dtsi mipi_csi2: csi@30b60000 { · line 1435

Quoted 1 line
arch/arm64/boot/dts/freescale/imx8mq.dtsi +0 -0
 					<&clk 

IMX8MQ_SYS1_PLL_800M>;

author
#5 lore raw

Re: [PATCH 1/2] arm64: dts: imx8mq: Correct MIPI CSI clocks

Quoted 19 lines · Sebastian Krzyszkowiak
Quoted 10 lines · On piątek, 17 kwietnia 2026 13:01:59 czas środkowoeuropejski letni Robby Cai…

CSI capture may intermittently fail due to mismatched clock rates. The previous configuration violated the timing requirement stated in the i.MX8MQ Reference Manual:

"The frequency of clk must be exactly equal to or greater than the RX
byte clock coming from the RX DPHY."

Update the clock configuration to ensure that the CSI core clock rate is equal to or greater than the incoming DPHY byte clock. The updated clock ratios are consistent with those used in NXP's downstream BSP.

I believe this is a misreading of the docs.

IMX8MQ_CLK_CSIX_PHY_REF refers to the UI pixel clock (clk_ui), not the RX DPHY byte clock. All this change would do is to break streaming with more than 100 Mpixels per second / 1064 Mbps per MIPI lane.

Quoted 7 lines

As mentioned in the reference manual:

"The frequency of clk_ui must be such that the data received on the data_out output is greater than or equal to the total bandwidth of the physical MIPI interface. Clk_ui has no relationship requirement with regards to ‘clk’ other than the bandwidth requirement mentioned previously."

You are right — thank you for the detailed clarification.

Given this, the commit message and the rationale behind this change are incorrect, and the current patch could indeed break higher-bandwidth streaming use cases. Thank you for catching this.

I will revisit the clock assumptions and drop or rework this change based strictly on the documented bandwidth requirements in the next revision.

Regards,
Robby

[...]

author
#6 lore raw

PATCH 2/2 arm64: dts: imx8mq-evk: Enable MIPI CSI and dual OV5640 cameras

In reply to Robby Cai

Enable CSI1/CSI2 bridges and the MIPI-CSI host interfaces, and add two OV5640 MIPI camera sensor nodes on I2C1 and I2C2.

The resulting camera pipelines are as follows:

- OV5640 on I2C2 -> MIPI CSI1 -> CSI1
- OV5640 on I2C1 -> MIPI CSI2 -> CSI2

---

Tested with following commands:

On CSI1:

media-ctl -d 0 -l "'ov5640 1-003c':0 -> 'imx8mq-mipi-csi2 30a70000.csi':0 [1]" media-ctl -d 0 -V "'ov5640 1-003c':0 [fmt:YUYV8_1X16/640x480 field:none]" media-ctl -d 0 -V "'imx8mq-mipi-csi2 30a70000.csi':0 [fmt:YUYV8_1X16/640x480 field:none]" media-ctl -d 0 -V "'csi':0 [fmt:YUYV8_1X16/640x480 field:none]"
v4l2-ctl -d 0 --set-fmt-video=width=640,height=480,pixelformat=YUYV --stream-mmap

On CSI2:

media-ctl -d 1 -l "'ov5640 0-003c':0 -> 'imx8mq-mipi-csi2 30b60000.csi':0 [1]" media-ctl -d 1 -V "'ov5640 0-003c':0 [fmt:YUYV8_1X16/640x480 field:none]" media-ctl -d 1 -V "'imx8mq-mipi-csi2 30b60000.csi':0 [fmt:YUYV8_1X16/640x480 field:none]" media-ctl -d 1 -V "'csi':0 [fmt:YUYV8_1X16/640x480 field:none]"
v4l2-ctl -d 1 --set-fmt-video=width=640,height=480,pixelformat=YUYV --stream-mmap

---
 arch/arm64/boot/dts/freescale/imx8mq-evk.dts | 149 +++++++++++++++++++
 1 file changed, 149 insertions(+)
arch/arm64/boot/dts/freescale/imx8mq-evk.dts +149 -0
index d48f901487d4..8bdfbfebfcc9 100644
@@ -6,6 +6,8 @@
 
 /dts-v1/;
 
+#include <dt-bindings/media/video-interfaces.h>
+
 #include "imx8mq.dtsi"
 
 / {
@@ -50,6 +52,20 @@ reg_usdhc2_vmmc: regulator-vsd-3v3 {
 		enable-active-high;
 	};
 
+	reg_1v5: regulator-1v5 {
+		compatible = "regulator-fixed";
+		regulator-name = "VDD_1V5";
+		regulator-min-microvolt = <1500000>;
+		regulator-max-microvolt = <1500000>;
+	};
+
+	reg_2v8: regulator-2v8 {
+		compatible = "regulator-fixed";
+		regulator-name = "VDD_2V8";
+		regulator-min-microvolt = <1800000>;
+		regulator-max-microvolt = <1800000>;
+	};
+
 	buck2_reg: regulator-buck2 {
 		pinctrl-names = "default";
 		pinctrl-0 = <&pinctrl_buck2>;
@@ -172,6 +188,14 @@ &A53_3 {
 	cpu-supply = <&buck2_reg>;
 };
 
+&csi1 {
+	status = "okay";
+};
+
+&csi2 {
+	status = "okay";
+};
+
 &ddrc {
 	operating-points-v2 = <&ddrc_opp_table>;
 	status = "okay";
@@ -330,12 +354,101 @@ vgen6_reg: vgen6 {
 			};
 		};
 	};
+
+	camera@3c {
+		compatible = "ovti,ov5640";
+		reg = <0x3c>;
+		pinctrl-names = "default";
+		pinctrl-0 = <&pinctrl_camera2_pwdn>;
+		clocks = <&clk IMX8MQ_CLK_CLKO2>;
+		clock-names = "xclk";
+		assigned-clocks = <&clk IMX8MQ_CLK_CLKO2>;
+		assigned-clock-parents = <&clk IMX8MQ_SYS2_PLL_200M>;
+		assigned-clock-rates = <20000000>;
+		powerdown-gpios = <&gpio1 5 GPIO_ACTIVE_HIGH>;
+		DOVDD-supply = <&sw4_reg>;
+		AVDD-supply = <&reg_2v8>;
+		DVDD-supply = <&reg_1v5>;
+		status = "okay";
+
+		port {
+			camera2_ep: endpoint {
+				remote-endpoint = <&mipi_csi2_in_ep>;
+				clock-lanes = <0>;
+				data-lanes = <1 2>;
+			};
+		};
+	};
+};
+
+&i2c2 {
+	clock-frequency = <100000>;
+	pinctrl-names = "default";
+	pinctrl-0 = <&pinctrl_i2c2>;
+	status = "okay";
+
+	camera@3c {
+		compatible = "ovti,ov5640";
+		reg = <0x3c>;
+		pinctrl-names = "default";
+		pinctrl-0 = <&pinctrl_camera1_pwdn>, <&pinctrl_camera_rst>;
+		clocks = <&clk IMX8MQ_CLK_CLKO2>;
+		clock-names = "xclk";
+		assigned-clocks = <&clk IMX8MQ_CLK_CLKO2>;
+		assigned-clock-parents = <&clk IMX8MQ_SYS2_PLL_200M>;
+		assigned-clock-rates = <20000000>;
+		powerdown-gpios = <&gpio1 3 GPIO_ACTIVE_HIGH>;
+		DOVDD-supply = <&sw4_reg>;
+		AVDD-supply = <&reg_2v8>;
+		DVDD-supply = <&reg_1v5>;
+		status = "okay";
+
+		port {
+			camera1_ep: endpoint {
+				remote-endpoint = <&mipi_csi1_in_ep>;
+				clock-lanes = <0>;
+				data-lanes = <1 2>;
+			};
+		};
+	};
 };
 
 &lcdif {
 	status = "okay";
 };
 
+&mipi_csi1 {
+	status = "okay";
+
+	ports {
+		port@0 {
+			reg = <0>;
+
+			mipi_csi1_in_ep: endpoint {
+				remote-endpoint = <&camera1_ep>;
+				data-lanes = <1 2>;
+				bus-type = <MEDIA_BUS_TYPE_CSI2_DPHY>;
+			};
+		};
+	};
+};
+
+&mipi_csi2 {
+	status = "okay";
+
+	ports {
+		port@0 {
+			reg = <0>;
+
+			mipi_csi2_in_ep: endpoint {
+				remote-endpoint = <&camera2_ep>;
+				data-lanes = <1 2>;
+				bus-type = <4>;
+			};
+		};
+	};
+};
+
 &mipi_dsi {
 	#address-cells = <1>;
 	#size-cells = <0>;
@@ -532,12 +645,41 @@ &wdog1 {
 };
 
 &iomuxc {
+	pinctrl-names = "default";
+	pinctrl-0 = <&pinctrl_hog>;
+
+	pinctrl_hog: hoggrp {
+		fsl,pins = <
+			/* MCLK for cameras on both CSI1 and CSI2 */
+			MX8MQ_IOMUXC_GPIO1_IO15_CCMSRCGPCMIX_CLKO2	0x59
+		>;
+	};
+
 	pinctrl_buck2: vddarmgrp {
 		fsl,pins = <
 			MX8MQ_IOMUXC_GPIO1_IO13_GPIO1_IO13		0x19
 		>;
 	};
 
+	pinctrl_camera1_pwdn: camera1pwdngrp {
+		fsl,pins = <
+			MX8MQ_IOMUXC_GPIO1_IO03_GPIO1_IO3		0x19
+		>;
+	};
+
+	pinctrl_camera2_pwdn: camera2pwdngrp {
+		fsl,pins = <
+			MX8MQ_IOMUXC_GPIO1_IO05_GPIO1_IO5		0x19
+		>;
+	};
+
+	pinctrl_camera_rst: camerarstgrp {
+		fsl,pins = <
+			/* Reset PIN for cameras on both CSI1 and CSI2 */
+			MX8MQ_IOMUXC_GPIO1_IO06_GPIO1_IO6		0x19
+		>;
+	};
+
 	pinctrl_fec1: fec1grp {
 		fsl,pins = <
 			MX8MQ_IOMUXC_ENET_MDC_ENET1_MDC			0x3
@@ -565,6 +707,13 @@ MX8MQ_IOMUXC_I2C1_SDA_I2C1_SDA			0x4000007f
 		>;
 	};
 
+	pinctrl_i2c2: i2c2grp {
+		fsl,pins = <
+			MX8MQ_IOMUXC_I2C2_SCL_I2C2_SCL			0x4000007f
+			MX8MQ_IOMUXC_I2C2_SDA_I2C2_SDA			0x4000007f
+		>;
+	};
+
 	pinctrl_ir: irgrp {
 		fsl,pins = <
 			MX8MQ_IOMUXC_GPIO1_IO12_GPIO1_IO12		0x4f
Signature · 1 line
2.37.1