13:16 <aalm> hi

13:17 <aalm> should dwc3 work as is on 54xx w/current mainline?

13:21 <aalm> [ 1.447655] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus-boost not found, using dummy regulator

13:22 <aalm> i don't see how that could work, no "vbus" nor "vbus-boost" in any .dts(i) i looked at..

13:23 <LiquidAcid> aalm, that's why it's using a dummy

13:26 <aalm> mm, i guess i'll try renaming vdd33-supply & vdd10-supply next

13:27 <LiquidAcid> not sure why you want to rename anything

13:27 <aalm> to get working usb3

13:28 <LiquidAcid> and why do you think that renaming something gets you working usb3?

13:30 <aalm> .. are you seriously asking that?

13:30 <aalm> i believe the driver would work if there was power

13:32 <LiquidAcid> again, why do you want to rename something? if you're missing regulators, then how about _adding_ stuff?

13:32 <aalm> i'

13:33 <aalm> i'm not

13:33 <aalm> missing regs

13:33 <aalm> &usbdrd3_1 {

13:33 <aalm> vdd33-supply = <&ldo12_reg>;

13:33 <aalm> vdd10-supply = <&ldo15_reg>;

13:33 <aalm> };

13:33 <aalm> they're just named wrong

13:34 <aalm> https://github.com/torvalds/linux/commit/a6867836db35d1e178744166765b57288bf4e8e5 <-- commit which added vbus-boost enabling to phy-exynos5-usbdrd.c

13:34 <aalm> no trace of dts changes in it

13:35 <aalm> possibly separate commit, or something, but my grep does fail to find "vbus-boost" at all from linux/arch/arm/boot/dts/exynos*

13:36 <LiquidAcid> that looks like an optional supply/regulator

13:36 <LiquidAcid> and maybe the changes to the dts haven't landed yet, or are just not meant for upstream

13:37 <LiquidAcid> i'm not sure how you have deduced that this vbus-boost is your problem

13:45 <LiquidAcid> also, i think you're mixing up drivers here, the compatible string of usbdrd3_1 is samsung,exynos5250-dwusb3, your vbus-boost property is only used in the phy driver

14:04 <aalm> very much likely