HOW TO CONFIGURE THE SPIDEV0 on KHADAS EDGE V BOARD

HOW TO CONFIGURE THE SPIDEV0 on KHADAS EDGE V BOARD ?
WHICH DTSI file as to modifed ?
which config file i have to modifie ?
please give the solutions.

@jack.zhao Please help to check this issue.

@ramesh hello,
Spi3 from the 40gpio port,

Add the following patch configuration:

diff --git a/arch/arm64/boot/dts/rockchip/rk3399-khadas-edge.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-khadas-edge.dtsi
index 16c0ac7c5109..cc40f74fc6be 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-khadas-edge.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-khadas-edge.dtsi
@@ -1157,10 +1157,17 @@

&spi3 {
-       status = "disabled";
+       status = "okay";

-       cs-gpios = <&gpio1 17 GPIO_ACTIVE_LOW>, <&gpio1 16 GPIO_ACTIVE_LOW>;
-       max-freq = <48000000>;
+//     cs-gpios = <&gpio1 18 GPIO_ACTIVE_LOW>;
+//     max-freq = <48000000>;
+       max-freq = <50000000>;
+       spi_test@00 {
+               compatible = "rockchip,spidev";
+               reg = <0>;
+               spi-max-frequency = <5000000>;
+               status = "okay";
+       };

 };

Then recompile the firmware burning,

Test method reference link:

check the nodes generated under /dev:

ls /dev/spi*
/dev/spidev32766.0

40p row pin inner connection 22&23,
Finally, spidev dmeo is tested according to the node name, make corresponding changes in the document:

static const char *device = "/dev/spidev32766.0";

after doing this
ls /dev

it is showing spidev32766.0

is this is same as spidev3.0 ?

@ramesh hello,
This node is generated. That’s right.

If you need to test with dmeo, you need to change the spidev_ test. C name of equipment document in the document:

static const char *device = "/dev/spidev32766.0";
1 Like

@ramesh hi,
Is the function of this problem working properly ?
No problem, please click a like!!!
The follow-up will provide you with better service.
Thank you! :smile: