Remix.run Logo
mathis 8 days ago

The situation with chargers isn’t ideal. With a single USB-C port, everything works fine.

The problem starts when multiple ports are involved. Plugging in a second device can trigger unpredictable behavior, which is usually acceptable for battery-powered devices. But for devices that need a continuous power supply (e.g., a Raspberry Pi), multi-port chargers aren’t reliable –– connecting another device may briefly interrupt power.

Using a traditional power strip with one dedicated adapter per device avoids this issue.

For now, I’m sticking with individual USB-C adapters for non-battery-powered devices.

avianlyric 8 days ago | parent [-]

It’s a limitation of the early versions of the PD spec. The PD spec now includes features that allow a device to express its needed power draw, and wanted power draw, along with info like the fact they’re a battery pack.

In addition the spec now has messages that allow a charger to renegotiate the PD contract with a device with resetting the entire USB-C connection. So if you have chargers and devices that support these elements, you can connect and disconnect devices with interrupting the power to anything else connected. The charger just does a live renegotiation and redistribution of its available power envelope.

Also means that when a phone and battery pack get plugged in, the charger can pull power allocation from the battery pack to send to the phone so the phone charges first. Then once the phone is charged, reallocate the power budget to the battery packs again.