ballerbu1g9005 has quit [Ping timeout: 258 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 265 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 252 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 258 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 272 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 265 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 265 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 272 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 258 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 244 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 272 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 265 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
ballerburg9005 has joined #linux-amlogic
hipboi has quit [Ping timeout: 272 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 252 seconds]
sputnik_ has quit [Ping timeout: 250 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 272 seconds]
GNUtoo has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 258 seconds]
ballerburg9005 has quit [Ping timeout: 272 seconds]
hipboi has joined #linux-amlogic
camus has joined #linux-amlogic
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 272 seconds]
camus1 is now known as camus
hipboi has quit [Ping timeout: 265 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
hipboi has quit [Ping timeout: 258 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 265 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 258 seconds]
hipboi has joined #linux-amlogic
ballerburg9005 has joined #linux-amlogic
cmeerw has joined #linux-amlogic
hipboi has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 272 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 258 seconds]
hipboi has joined #linux-amlogic
camus has quit [Remote host closed the connection]
hipboi has quit [Ping timeout: 268 seconds]
ballerburg9005 has quit [Ping timeout: 268 seconds]
ballerburg9005 has joined #linux-amlogic
hipboi has joined #linux-amlogic
ballerbu1g9005 has joined #linux-amlogic
ballerburg9005 has quit [Ping timeout: 272 seconds]
hipboi has quit [Ping timeout: 252 seconds]
cmeerw has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 252 seconds]
sputnik_ has joined #linux-amlogic
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-amlogic
warpme_ has quit [Quit: Connection closed for inactivity]
hipboi has quit [Ping timeout: 265 seconds]
alyssa has quit [Quit: leaving]
hipboi has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
hipboi has quit [Ping timeout: 258 seconds]
<BlueMatt>
how does the dwc2 bus maxpower selection work? for devices which report even moderate power like 400mA, upstream linux on odroidc2 appears to reject it, vs hardkernel's ancient branch will happily run it.
ballerbu1g9005 has quit [Ping timeout: 268 seconds]
<xdarklight>
BlueMatt: I haven't come across something like that in the dwc2 code yet. so either it's me missing the relevant code, "dwc2 doesn't care" or "handled by generic code"
<BlueMatt>
from my (rather poor) grep skills it seems like its "read from device"
<BlueMatt>
rpi-related discussions seem to indicate you can set a gpio (presumably connected back to the usb controller) which changes maxpower
<BlueMatt>
so I guess the question is....how does hardkernel do it/do they have a similar flag?
<xdarklight>
BlueMatt: page 21 of the Odroid-C2 schematics mention a RICHTEK RT9715EGB which according to it's datasheet has a 1.5A current limit. if software is not involved here (which I was referring to in my last comment) then I'd expect that any device which draws less than 1.5A should work
<BlueMatt>
may be some other issue, but I cant seem to get anything that reports more than 200mA to even show up
<BlueMatt>
(reports more than 200mA according to my laptop's lsusb)
<xdarklight>
let me check on my Odroid-C1 with this USB drive which has: MaxPower 500mA
<BlueMatt>
oh, maybe its 100, I dont have a (100, 200) device, and lsusb on the odroid says "MaxPower 100mA"
<BlueMatt>
on the bus
<BlueMatt>
and bHubContrCurrent 100 milli Ampere
hipboi has joined #linux-amlogic
<BlueMatt>
maybe I'm just missing some config for devices
<xdarklight>
it should always show up on the bus, regardless of whether there's a driver or not
<BlueMatt>
right, it does not. unless I'm missing some config for "plugged a usb3 device into a usb2 port"?
<xdarklight>
the device I'm testing is a USB 3.0 storage device
<xdarklight>
BlueMatt: one note in general: USB hotplug seems to be hit and miss (on Odroid-C1 it's mostly miss unfortunately). lsusb -vvv seems to work around this
<BlueMatt>
yea, its mostly miss on my c2 as well, i normally test by rebooting :/
<xdarklight>
BlueMatt: my USB 3.0 flash drive is not being detected at all. however, my USB 3.0 card reader is: https://pastebin.com/jEfx2k3s
<BlueMatt>
huh. right, so I only have usb 3.0 flash drives and an old usb 2.0 one. only the 2.0 one is detected.
<BlueMatt>
maybe I incorrectly assumed power-restriction, but it looks like your device there is reporting that it pulls no power?
<BlueMatt>
oh, no, 500ma
<BlueMatt>
huh.
ballerburg9005 has joined #linux-amlogic
<BlueMatt>
i guess not a lot of room to work around it, then?
<xdarklight>
my suggestion is to ask on the linux-usb (and Cc'ing the linux-amlogic) mailing list while including the dwc2 driver maintainers. there's CONFIG_USB_DWC2_DEBUG which gives a lot of debug info. unfortunately it's too much debug info and I don't know which part to focus on
<BlueMatt>
right, so its just the random ones I have.
<BlueMatt>
xdarklight: whats your wMaxPacketSize for the ones that work/dont?
<BlueMatt>
oh, nvm, found a usb 3.0 one that works here
<BlueMatt>
huh. ugh
hipboi has quit [Ping timeout: 265 seconds]
ballerburg9005 has quit [Ping timeout: 252 seconds]