Docs: Type-C shouldn't be referred to as supporting host mode

•zmatt> 
jkridner: it may be better to not call the type-C port "dual role" given that it doesn't actually support host role (as previously discussed) .. and it doesn't really need it anyway since there are two usb 3 type-A ports
10:28 AM 
in de board features list I mean
10:28 AM 
*in the
10:29 AM <jkridner> Jason Kridner 
sure, but it can work with some hubs as a host. Suggesting just calling it a  client port?
10:29 AM <•zmatt> 
those hubs are in violation of the usb s[ec
10:29 AM 
*spec
10:30 AM <jkridner> Jason Kridner 
removed Host from https://beagleboard.org/boards/
10:30 AM <•zmatt> 
but yeah, device port or peripheral port
10:31 AM 
— jkridner wishes lorforlinux logged into IRC so I can pawn off the update to the SRM.
10:31 AM <•zmatt> 
host role requires either being a power source or a type-c controller that supports data role swap
10:31 AM <jkridner> Jason Kridner 
documentation pull requests to git.beagleboard.org/beagleboard/beaglebone-ai-64 are *welcome*!
10:32 AM 
right. we'd need a hub that starts in the wrong data role.
10:33 AM <•zmatt> 
yep, the hub would need to act in peripheral role even though host role was negotiated for it