03:39 <harigs_> hi all, where can i find document about rk3399's ISP usage?

03:40 <harigs_> i can find ISP details of rk3288 but not rk3399

12:56 <ShapeShifter499> Hi

13:28 <kbingham> Looks like my issues are due to the extcon frameworks ... the fusb doesn't register with the extcon framework, but the phy-rockchip-typec usesextcon_get_edev_by_phandle() to get a reference to the fusb0 (but fails, because the fusb hasnt' registered in the appropriate extcon_dev_list)

13:50 <mmind00> kbingham: can you check if your sources have https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/phy/rockchip/phy-rockchip-typec.c?id=ec1fcd7b7e6f50dd6e259ca76c6e41e2346b3afe

13:52 <kbingham> mmind00, Yup

13:53 <kbingham> I definitely have taht patch in.

13:53 <mmind00> very strange, because then it shouldn't defer type type-c phy probe

13:54 <mmind00> the very goal of that patch is to make the type-c phy probe even if the extcon is missing ...

13:55 <kbingham> mmind00, Aha ... but I have provided an extcon ...

14:03 <kbingham> mmind00, Ok - so removing the extcon means that the fe800000.dwc3 has probed ... but if that's in host mode - I don't think it lets me run it as a gadget?

14:04 <kbingham> Or is that where you had suggested I can force it to run peripheral mode ?

14:04 <mmind00> kbingham: yep that was my idea

14:04 <kbingham> Ok - I'll give that a go ...

14:04 <mmind00> kbingham: in theory you might even just need to set dr_mode in the dwc3 dt node to device?

14:04 <kbingham> Presumably by adapting the return that's added in the patch you referenced

14:05 <mmind00> kbingham: yep

14:23 <kbingham> mmind00, no probe failures, but no udc in /sys/class/udc :( so not useful ... I'll keep digging.

14:31 <kbingham> aha - setting dr_mode = "peripheral", has given me a udc at /sys/class/udc/fe800000.dwc3 :D

15:05 <eballetbo> yeah, setting dr_mode = "peripheral" should work, I did some work this week trying to make usb work as gadget

15:06 <eballetbo> kbingham: ooi: has your platform the otg_id pin connected?

15:08 <kbingham> eballetbo, Not sure ... Not even sure how to find out currently :)

15:08 <kbingham> eballetbo, Were you successful in getting gadget working?

15:09 <kbingham> I've just tried configuring a mass storage gadget and it didn't enumerate on the host. I got host-usb errors though ... so 'something' happened .. but no the right thing yet :D

15:09 <eballetbo> yes, but my platform need some hacks to make it work properly (mainly due the otg_id pin is not hooked). Still investigating

15:10 <kbingham> eballetbo, I see no reference to otg_id in the vendor tree for this board, so I suspect it's similar.

15:10 <kbingham> I'd be interested in seeing your hacks to try out here :)

15:10 <kbingham> eballetbo, Which platform are you working on ?

15:10 <eballetbo> let me share my wip tree. I'm under kevin

15:11 <kbingham> eballetbo, thanks.

15:11 <kbingham> Ohhh - I've just found the board schematics - :D

15:14 <kbingham> eballetbo, Is otg_id related to vbus detect ?

15:14 <kbingham> TYPEC0_U3VBUSDET ..

15:20 <eballetbo> kbingham: Try if works applying the latest 3 patches from https://gitlab.collabora.com/eballetbo/linux/commits/topic/chromeos/usb-otg-support

15:22 <eballetbo> sorry I did not have time to cleanup/fixup the patches

15:22 <kbingham> eballetbo, don't worry :)

15:22 <kbingham> WIP is WIP :D

15:24 <eballetbo> That's the script I am using to test https://hastebin.com/vudewuhale.bash

15:24 <eballetbo> I am using a ethernet gadget instead but a mass storage should be similar

15:37 <kbingham> eballetbo, Thankyou - that is certainly useful too

15:41 <mmind00> That type-c stuff is confusing :-D ... I'm currently reading in a pending series adding support for things like the dp altmode to the general typec framework

15:41 <eballetbo> kbingham: fyi, pushed a new patch, so there are 4 wip patches that you need to apply

15:42 <kbingham> eballetbo, Your changes appear to be in he phy-rockchip-inno-usb2 ?

15:43 <eballetbo> yes

15:43 <kbingham> Are you using type C?

15:47 <eballetbo> Yes, not sure in your platform, but at least on kevin the usb is complex, we have the usb2-phy + usb3-phy + dwc3 controller + cros-ec-extcon as actors

15:48 <eballetbo> Just to be clear, what I have is a PC (USB-A) connected to the Kevin (Type C) and I configure a cdc ethernet gadget

15:50 <eballetbo> I suppose you have the same, but instead cros-ec-extcon you have a fusb chip?

15:50 <eballetbo> ooi, are your schematics public?

15:55 <kbingham> http://wiki.friendlyarm.com/wiki/images/f/f4/NanoPC-T4-1802-Schematic.pdf

15:56 <kbingham> http://wiki.friendlyarm.com/wiki/index.php/NanoPC-T4

15:56 <kbingham> It's a cheap(ish) board I ordered online. My goal is to test UVC gadget video performance on DWC3 TypeC

15:57 <kbingham> I'm actually trying to work on a qualcomm platform, which uses the DWC3 - I had hoped to be able to test mainline drivers with the RK3399 - (qualcomm vendor tree is v4.9) - but alas I'm hitting sooo many troubles :(

15:58 <kbingham> Still ... now I have a new device for a media-centre role :D

16:12 <kbingham> eballetbo, Thank you for your help! - I have managed to bring up the nanopc board with a USB ethernet bridge across the type-c :D

16:12 <kbingham> So ... it's workign :D

16:12 <eballetbo> \o/

16:12 <kbingham> Next step ... UVC video :)

16:12 <kbingham> (next week now though)

16:13 <eballetbo> I'll also work on these patches next week, to make it less hacky :)

16:16 <kbingham> eballetbo, Great - please CC me on any submissions you make :)

16:16 <kbingham> (kieran.bingham@ideasonboard.com)

18:49 <ShapeShifter499> hi

18:50 <ShapeShifter499> mmind00: The guys over at #archlinux-arm suggested I talk to you for help with rockchip and possibly rock64

18:51 <ShapeShifter499> ayufan: hey are you the same from Rock64?

18:53 <ShapeShifter499> I believe some of the fixes and patches for USB in the rockchip-linux sources needs to be incorporated into mainline

18:56 <ayufan> yeap

19:23 <ayufan> I checked, I didn't see any interesting commits

20:16 <mmind00> ShapeShifter499: the rk3328 has this nasty usb3 bug where the phy becomes unresponsive after unplugging a device

20:17 <ShapeShifter499> hmm

20:28 <ShapeShifter499> mmind00: I saw a crash with the USB plugged in at boot with the mainline

20:31 <ShapeShifter499> mmind00: ayufan https://github.com/ayufan-rock64/linux-build/issues/259 wouldn't be related to any odd crashes?

20:32 <ShapeShifter499> Since my issue was solved with a USB hub that has more power. Maybe this might cause an issue?

21:24 <amstan> ShapeShifter499: so are there any patches that need reviewing?

21:34 <ShapeShifter499> amstan: hi

21:35 <ShapeShifter499> amstan: I don't know yet, I just got to the realization that the kernel I found was working was compiled from the rockchip-linux source which has the USB patches