Summarises the measured cost as roughly 3 s blank per PD state change,
with keep-awake in the app handling sleep, and notes that a marginal
charger renegotiating PD repeatedly would cut the link each time.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No USB-C detach, one gadget reconnect and a fresh DHCP exchange. With
sleep ruled out, the hub's PD edges cost ~3.5 s (unplug) and ~2.2 s
(plug-in).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Idle on battery, the tablet suspends ~60 s after screen-off and only
answers at its DHCP-renewal wakeups while the USB link stays up. Kept
awake with a video, a PD unplug costs 3.1 s and then nothing. The
earlier replug silences were the tablet waking from sleep.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Unplug causes the full USB-C detach (~3.5 s total). Replug causes no
detach but ~10 s of disruption: the tablet goes silent while the Orin's
link stays up, then reconnects its gadget once. Only an app-level
heartbeat would see the replug outage.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Three PD unplug/replug cycles each caused one full USB-C detach; the
link flapped ~3 times and settled within 5-12 s with no intervention.
Treated as a service-level requirement (yukart decision 24), not a
host fix.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tablet as USB host, Orin's stock L4T gadget as the network side: the
tablet chose NCM and got 192.168.55.100. Android only routes app traffic
over it once it is the default network, so the app has to bind to the
Ethernet network explicitly.
Mass storage is off (enable_ums=0); the config isn't a conffile, so an
nvidia-l4t-init upgrade restores it and the report says how to check.
The Orin's USB-C port (FUSB301, no PD) can't charge the tablet; the PD
hub on hand is the practical fix.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mikkeli
mikkeli