<Guest16>
CounterPillow is there any way I can force the device to just stay in host mode and ignore all other usbc stuff? i tried adding fusb302 nodes to the dt but that didnt seem to help.
<Guest16>
Or can i add a temporary patch in the naneng combophy to force the device to be in host mode?
Daanct12 has quit [Quit: WeeChat 4.7.0]
Guest16 has quit [Ping timeout: 252 seconds]
stikonas has quit [Quit: Konversation terminated!]
manawyrm has quit [Quit: Read error: 2.99792458 x 10^8 meters/second (Excessive speed of light)]
manawyrm has joined #linux-rockchip
<CounterPillow>
dr_mode = "host"; in the DT should do it I think
psydroid2 has joined #linux-rockchip
rgolledge has quit [Ping timeout: 245 seconds]
dsimic has quit [Ping timeout: 248 seconds]
dsimic has joined #linux-rockchip
raster has joined #linux-rockchip
Guest16 has joined #linux-rockchip
<Guest16>
CounterPillow: The tree should already have that. I've tried adding the FUSB302 entried to the device tree but they dont seem to help
Guest16 has quit [Ping timeout: 252 seconds]
cbeznea has quit [Ping timeout: 260 seconds]
raster has quit [Quit: Gettin' stinky!]
<Ermine>
Hello, so I was fucking with MPP kernel driver this week. It pokes in power management and clk and opp stuff (and in also that rockchip_dmc thing...). Are there power management bits that need to be upstreamed, in case if future upstream rkvenc/rkvdec drivers would need them?
<Ermine>
At least rockchip tree has more smc calls defined than mainline
<CounterPillow>
rkvdec for several SoCs and codecs either already exists upstream (rk3399, rk3328) or has been sent to the list (rk3588/rk3576) by detlevc, so I think we're good on that front. Usually it's best to implement some of the more intricate power/clock stuff when you have a way to test it upstream, i.e. a user of it; vendor code has a tendency to do more things than necessary or do them in a different way than what upstream would want for