Stat_headcrabed has quit [Read error: Connection reset by peer]
Stat_headcrabed has joined #linux-rockchip
Stat_headcrabed has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas_ has joined #linux-rockchip
stikonas has quit [Ping timeout: 240 seconds]
warpme has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
psydroid has joined #linux-rockchip
<lvrp16>
does anyone know how to fix the "dwc3: probe of fe900000.usb failed with error -110" due to regulator deferment? "vcc_vbus_typec1: could not add device link phy-ff770000.syscon:usb2phy@e460.10: -ENOENT"
warpme has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery1 is now known as kevery
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dsimic has quit [Ping timeout: 260 seconds]
dsimic has joined #linux-rockchip
Stat_headcrabed has joined #linux-rockchip
Stat_headcrabed has quit [Remote host closed the connection]
dsimic has quit [Quit: Going offline for now]
dsimic has joined #linux-rockchip
Daanct12 has quit [Quit: WeeChat 4.0.4]
Danct12 has quit [Read error: Connection reset by peer]
Stat_headcrabed has joined #linux-rockchip
mripard has quit [Remote host closed the connection]
<macromorgan>
montjoie: Ping me with your crypto driver, I was just looking at this earlier...
<macromorgan>
I'm testing mainline enablement on an RK3588S board (the Indiedroid Nova) and contemplating getting an RK3588 based router, in which case I'll want a working crypto accelerator.
mripard has joined #linux-rockchip
Danct12 has joined #linux-rockchip
warpme has joined #linux-rockchip
vvn has joined #linux-rockchip
mripard has quit [Quit: mripard]
mripard has joined #linux-rockchip
<montjoie>
macromorgan: I will upload a working version very soon
wcarson has quit [Read error: Connection reset by peer]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
wcarson has joined #linux-rockchip
<vvn>
hi there -- I have a Rock 4 SE with an ov5647 camera module plugged in. I cannot see the camera, but I have CONFIG_IMX5647=y. I tried to add #intfc:dtoverlay=ov5647, intfc:dtoverlay=ov5647 or dtoverlay=ov5647 in /boot/hw_intfc.conf, but that has no effect. Any idea how to get camera module to work?
<vvn>
I also have an imx219 if that can help.
warpme has joined #linux-rockchip
<macromorgan>
vvn: That will depend entirely on your OS, sadly. You might get with the OS distributor first (Armbian?). Assume you need a CSI port and an I2C port active, plus the correct device tree bindings and all drivers. But how that is done depends entirely on your OS.
<macromorgan>
montjoie: Okay. I'm looking at an RNG driver as well, thinking that can be a "sub" driver since depending upon the hardware it's either integrated with the crypto or its standalone.
<montjoie>
the code is done, but I dont remember in what state I leave it 6 month ago
<montjoie>
probably I will add it tomorow (I remember it was working, but I need to be sure)
<vvn>
macromorgan: thanks! I'm using the official meta-rockchip Yocto layer from Radxa. I'll look at their kernel recipe to see how the device tree bindings are set.