ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
<Tenkawa> Do any of you know if the usb-c port on the rockpro64 has any way to route data? right now it appears to just be power only. I was curious at first glance if it could be dts related or if that port is purely power only. Thanks for any thoughts.
vagrantc has joined #linux-rockchip
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-rockchip
s1b1 has quit [Read error: Connection reset by peer]
kevery has quit [Quit: kevery]
stikonas has quit [Ping timeout: 250 seconds]
lurchi_ is now known as lurchi__
s1b1 has joined #linux-rockchip
Tenkawa has quit [Quit: Leaving.]
kevery has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
lurchi__ has quit [Ping timeout: 245 seconds]
lurchi_ has joined #linux-rockchip
lurchi_ is now known as lurchi__
Net147 has quit [Quit: Quit]
Net147 has joined #linux-rockchip
Net147 has quit [Changing host]
Net147 has joined #linux-rockchip
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #linux-rockchip
Net147 has quit [Changing host]
Net147 has joined #linux-rockchip
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #linux-rockchip
Net147 has joined #linux-rockchip
Net147 has quit [Changing host]
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #linux-rockchip
Net147 has joined #linux-rockchip
Net147 has quit [Changing host]
lurchi__ is now known as lurchi_
<mort> Hey, meta-rockchip used to be hosted here: https://github.com/rockchip-linux/meta-rockchip, but that no longer exists. Does anyone know what happened to it? Was it deprecated? Was it just a dev repo for rockchip which gets merged into something else? Or what
ldevulder has joined #linux-rockchip
Max1Truc[m] has quit [Quit: You have been kicked for being idle]
<mriesch> it seems (e.g. on rk3399) there is a rockchip specific usb 3.0 controller node and an embedded node targetting the synopsis ip core. are those node merged since they have the same name (usb@fe800000)?
crabbedhaloablut has quit [Ping timeout: 240 seconds]
<mriesch> i am having troubles to understand which property should be where. both node and subnode require the specification of clocks, for example
crabbedhaloablut has joined #linux-rockchip
chewitt has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
<robmur01> yeah, dwc3 is a bit of a mess...
<robmur01> essentially, the dwc3 node owns the clocks that are fundamental to the core, while the outer platform glue-layer node owns any others that are particular to the integration (e.g. external clocking for the register interface)
stikonas has joined #linux-rockchip
<robmur01> except the generic core clock support is relatively recent, so there are still plenty of cases where the glue layer handles all clocks
<robmur01> IIRC, Johan had some patches for RK3399 and RK3328 a while back squashing the glue layer description entirely, since it wasn't doing anything that the dwc3 core device can't now handle by itself
kevery has quit [Ping timeout: 240 seconds]
chewitt has quit [Quit: Zzz..]
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
<mriesch> robmur01: ah ok.. well in general i like the separation between soc-specific glue and common dwc3 things. but i think rockchip,dwc3.yaml is too strict for the 3399
<mriesch> indeed both drivers require and handle clocks, but seems to be required to have "rockchip,rk3399-dwc3", "snps,dwc3"; as compatible
<mriesch> the latter does not make sense to me as the snps,dwc3 part is embedded in the subnode
rembo10 has quit [Quit: ZNC 1.8.2 - https://znc.in]
rembo10 has joined #linux-rockchip
<robmur01> oh, indeed it looks like the transparent-glue-layer approach *did* get into the schema and rk3328.dtsi, but rk3399.dtsi never caught up - I know I tested that missing patch on my RK3399 at the time and it did work fine (even though it looked like it shouldn't...)
<robmur01> heh, in fact it looks like my board is still running that DTB today :)
<mriesch> ok, maybe it makes sense to squash the nodes seeing that they share the same registers...
<mriesch> i am somewhat used to another soc where the glue had its own register range
<mriesch> and why is RK3568_PD_PIPE in rk3568 exclusively? hmm...
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
matthias_bgg has quit [Ping timeout: 250 seconds]
lurchi_ is now known as lurchi__
Tenkawa has joined #linux-rockchip
lurchi__ is now known as lurchi_
<Tenkawa> Did any of you see my question from last night by chance or should I repost it?
<Tenkawa> I'll repost just in case: Do any of you know if the usb-c port on the rockpro64 has any way to route data? right now it appears to just be power only. I was curious at first glance if it could be dts related or if that port is purely power only. Thanks for any thoughts.
<robmur01> Tenkawa: AFAICS it should sort-of-work already, since the USB3 port has "dr_mode" in the DT to force it into host mode. What it won't do is any proper Type C business, since there is a long-standing issue of the RK3399 phy driver not implementing the right API to talk to the FUSB302 Type C controller
<robmur01> by the same note it may not detect devices being plugged/unplugged very well
<robmur01> (I did play with the comparable situation on my NanoPC-T4 some time ago, but now I fail to recall the exact details)
<Tenkawa> interesting.. yeah it doesn't seem to see them either method.. I did read something about that usb-c port being power iffy
<Tenkawa> the lsusb tree see's it mapped which tells me the board sees it.. but then.... nothing
<robmur01> it may be a case of having to force the FUSB302's power role and/or data role appropriately by adding a connector node there as well
<Tenkawa> ahh
<Tenkawa> no big deal.. was more curiosity
<Tenkawa> I'll just use it for power
<Tenkawa> Its(If I use it at all)
<Tenkawa> I bought 5A supply for it
<Tenkawa> I am really enjoying the rk's sdo far
<Tenkawa> er so
matthias_bgg has joined #linux-rockchip
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
vagrantc has joined #linux-rockchip
lurchi_ is now known as lurchi__
crabbedhaloablut has quit [Ping timeout: 240 seconds]
crabbedhaloablut has joined #linux-rockchip
lurchi__ is now known as lurchi_
matthias_bgg has quit [Quit: Leaving]
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
lurchi_ is now known as lurchi__
diederik has quit [Ping timeout: 252 seconds]
diederik has joined #linux-rockchip
Tenkawa has quit [Quit: Leaving.]