kever has quit [Quit: No Ping reply in 180 seconds.]
kever has joined #linux-rockchip
xerpi has joined #linux-rockchip
kever has quit [Ping timeout: 268 seconds]
kever has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
chewitt has quit [Quit: Adios!]
ldevulder has joined #linux-rockchip
DuClare has joined #linux-rockchip
<DuClare>
Anyone know anything about hsic on rk3288? I'm not sure how it's supposed to show up on the host.. should it show up as its own HCI? (in rk3288.dtsi it's usb_hsic@ff5c0000, compatible = "generic-ehci")
BenG83 has quit [Ping timeout: 258 seconds]
MoeIcenowy has quit [Quit: ZNC 1.6.5+deb1+deb9u1 - http://znc.in]
MoeIcenowy has joined #linux-rockchip
BenG83 has joined #linux-rockchip
<kever>
DuClare: rk3288 hsic is ehci based controller, just different phy...
<kever>
just enable the dts node and it should be able to init in kernel, no difference with other driver.
kever has quit [Ping timeout: 246 seconds]
kaspter has quit [Quit: kaspter]
kaspter has joined #linux-rockchip
xerpi has quit [Remote host closed the connection]
xerpi has joined #linux-rockchip
vicencb has joined #linux-rockchip
cristian__c has joined #linux-rockchip
cristian_c has quit [Ping timeout: 250 seconds]
_whitelogger has joined #linux-rockchip
sb35 has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
xerpi has quit [Remote host closed the connection]
xerpi has joined #linux-rockchip
xerpi has quit [Remote host closed the connection]
xerpi has joined #linux-rockchip
xerpi has quit [Remote host closed the connection]
xerpi has joined #linux-rockchip
xerpi has quit [Remote host closed the connection]
afaerber has joined #linux-rockchip
stikonas_ has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
stikonas_ has quit [Remote host closed the connection]
<DuClare>
Ok, I'm at a bit of a loss here..
<DuClare>
HSIC on SoC does indeed show up in dmesg with no errors or other suspicious stuff
<DuClare>
It's supposedly connected to a usb3503a hub, which should run with its default internal config (so not using i2c to configure it)
<DuClare>
But that thing never appears
<DuClare>
And I can't for the life of me figure out how to diagnose the connection between the soc & that chip
<DuClare>
The soc side shows up as having one port, which makes sense.. can I reset the port somehow? Is there any way to check its status, maybe see whether the system thinks it's connected to the downstream hub or not?
<DuClare>
But I'm not power cycling or using soft resets so..
stikonas_ has quit [Remote host closed the connection]
<DuClare>
(Can I check the bus state in linux somehow)
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
<mmind00>
DuClare: maybe "just" a missing regulator / enable-gpio for that usb hub?
<mmind00>
DuClare: also, are the i2c lines connected and if so, does the i2c-device turn up?
<mmind00>
DuClare: aka basically checking if the hub ic is actually running
<DuClare>
mmind00: Hmm, how do you check that the i2c is actually up?
<DuClare>
But, aiui, i2c shouldn't be needed -- the hub should configure itself using built in defaults after a short timeout (<100ms)
<DuClare>
After that, i2c on it is .. undefined
<DuClare>
If I recall the datasheet correctly
<mmind00>
DuClare: that may be true, going through i2c was meant to check if the chip is actually running
<mmind00>
DuClare: and if the i2c controller the hub is connected to is running there are some i2c tools to just query registers of i2c devices
<DuClare>
Aha
<mmind00>
DuClare: that way you could check if the chip does talk (and hence has power)
<DuClare>
Multimeter seems to indicate that it has power but I could try i2c.. I'm just not sure if it's properly wired :)
<mmind00>
DuClare: that's why I asked about "if it is connected" :-)
<DuClare>
Yup
<DuClare>
As for the regulator.. the chip ought to be hardwired to an external one or it's using it's internal regulator so I don't think that needs to be set in dts
<mmind00>
DuClare: other than that, you might want to check if the RESET_N of the hub is properly configured
<DuClare>
It reads high
<mmind00>
then I guess it really should be up ... are you on mainline or vendor-kernel?
<DuClare>
Mainline
<mmind00>
I'm not sure if someone already tried this yet, so you're charting new territory it seems :-D
cristian_c has quit [Read error: Connection reset by peer]
ayaka has quit [Ping timeout: 250 seconds]
ayaka has joined #linux-rockchip
BenG83 has quit [Quit: Leaving]
BenG83 has joined #linux-rockchip
<mmind00>
DuClare: yeah, the vendor kernel in a lot of cases uses devicetree bindings that didn't get reviewed at all, so changed on the switch to mainline and an actual binding review
<mmind00>
DuClare: in any case, for the GRF voodoo, you could take a look a drivers/phy/rockchip/phy-rockchip-usb.c where this might fit in