[PATCH v1] board: rockchip: Add Bananapi R2Pro Board

[Frank Wunderlich]

Am 12. August 2023 03:50:14 MESZ schrieb Kever Yang <kever.yang at rock-chips.com>:
>Hi Frank,
>
>On 2023/8/8 01:14, Frank Wunderlich wrote:
>> From: Frank Wunderlich <frank-w at public-files.de>
>> 
>> Add rk3568 based Bananapi R2 Pro board.
>> 
>> Signed-off-by: Frank Wunderlich <frank-w at public-files.de>
>> ---
>> because iodomain is different to evb and now iodomain driver is sent as
>> patch we need to separate between EVB and R2Pro else board can be bricked.
>What's the detail difference before and after the iodomain driver for this board?

Sorry, missed this question somehow.

Evb defines these iodomains

&pmu_io_domains {
	pmuio1-supply = <&vcc3v3_pmu>;
	pmuio2-supply = <&vcc3v3_pmu>;
	vccio1-supply = <&vccio_acodec>;
	vccio2-supply = <&vcc_1v8>;
	vccio3-supply = <&vccio_sd>;
	vccio4-supply = <&vcc_1v8>;
	vccio5-supply = <&vcc_3v3>;
	vccio6-supply = <&vcc_1v8>;
	vccio7-supply = <&vcc_3v3>;
	status = "okay";
};

So vccio2 and vccio4 are 1v8 too which will brick these 2 io if still using this dts on r2pro which has these 2 3v3 (default).

>> diff --git a/arch/arm/dts/rk3568-bpi-r2pro.dts b/arch/arm/dts/rk3568-bpi-r2pro.dts
>> new file mode 100644
>> index 000000000000..9295e9836a56
>> --- /dev/null
>> +++ b/arch/arm/dts/rk3568-bpi-r2pro.dts
...
>> +&pmu_io_domains {
>> +	pmuio1-supply = <&vcc3v3_pmu>;
>> +	pmuio2-supply = <&vcc3v3_pmu>;
>> +	vccio1-supply = <&vccio_acodec>;
>> +	vccio3-supply = <&vccio_sd>;
>> +	vccio4-supply = <&vcc_3v3>;
>> +	vccio5-supply = <&vcc_3v3>;
>> +	vccio6-supply = <&vcc_1v8>;
>> +	vccio7-supply = <&vcc_3v3>;
>> +	status = "okay";
>> +};


regards Frank