A multi-port USB-C charger can briefly disconnect or reconnect a device when another load is attached because the charger may need to redistribute its finite power budget and advertise new USB Power Delivery capabilities. The connected devices then select from the updated offers. A short, repeatable transition can be normal for a documented power-sharing design; repeated cycling, heat or instability is not something to ignore.
The number printed on the charger is usually the system ceiling, not a promise that every port can deliver that number at the same time. The useful question is therefore not “Is this a 100W charger?” but “What does this exact port combination offer to these exact devices?”
Start with the total power budget
A charger converts one input into several outputs. Its controller must keep the sum of those outputs, conversion losses and thermal conditions inside the product design. If one laptop can use most of the available budget when connected alone, adding a tablet or phone forces the charger to choose a new allocation.
Texas Instruments describes USB-C power sharing as a system-level decision across multiple ports. The controller can divide the available power according to fixed limits, port priority or the requirements reported by attached devices. That architecture explains why a per-port maximum and a simultaneous-output maximum are different specifications.
| Allocation pattern | What the label may show | What can happen when a new device connects | What to verify |
|---|---|---|---|
| Fixed split | A defined maximum for each port combination | Existing devices may keep their contracts or be limited by the fixed map | The exact C1/C2/A combination table |
| Priority port | One USB-C port receives the largest share first | A lower-priority port receives the remaining budget | Which physical port has priority and whether order matters |
| Dynamic sharing | A total wattage plus per-port ceilings | The charger may advertise new capabilities and devices may renegotiate | Behavior with the intended devices connected together |
| Independent converters | High per-port ratings that may operate concurrently | Less visible reallocation, but the total input and thermal limits still apply | Simultaneous sustained output in the actual product documentation |
USB-PD contracts belong to one connection at a time
In USB Power Delivery, a source advertises power data objects, or PDOs, that describe available voltage and current combinations. A sink chooses an acceptable option with a request data object, or RDO. The result is an explicit contract for that source-sink pair; it is not a permanent property of the cable or port.
When the source budget changes, the charger may publish a different set of capabilities and ask one or more devices to negotiate again. TI’s power-negotiation application note shows that multi-port systems can update their offers according to the power available. During that transition, a device may briefly show charging stopped, a dock may reset, or a laptop icon may change before a new contract settles.
Why plugging in a cable can affect another port
Some chargers react when a powered device attaches; others also detect a cable or accessory before the final load is active. The controller does not know every future demand in advance. It responds to attachment state, cable identity where applicable, the device request and its programmed allocation rules.
A port label is a ceiling, while an active contract is a negotiated result inside the current shared budget. That distinction is why the same laptop can receive a different offer when it is alone, when a phone shares the charger, or when it is moved from a priority port to a secondary port.
Fixed and dynamic sharing feel different to the user
A fixed map is easier to predict: for example, the manual may state one allocation for C1 alone and another for C1+C2. A dynamic design can use more of the available budget when a connected device needs it and reassign capacity as loads appear, finish charging or disconnect.
Dynamic does not mean limitless. Each port still has an electrical ceiling, every cable has defined capabilities, and the total charger has a power and thermal envelope. The implementation may also prioritize the first port, the first device, the device with the largest request or a vendor-defined sequence. Only the product’s port table and an actual combination test reveal that policy.
Do not blame the cable before checking the allocation
A cable can constrain a USB-PD result, but it does not decide the charger’s total budget. If the device charges correctly alone and changes only when another port becomes active, inspect the sharing table first. Then verify that the cable is rated for the desired power and that the device supports the offered voltage profile.
The USB-C PD vs PPS guide explains the difference between fixed and programmable offers. That protocol distinction matters, but it is separate from multi-port allocation: a charger can support PPS and still reduce the power available to a port when several loads share one converter.
Run a one-variable port-combination test
- Record the charger model, total rating and the published C1, C2 and USB-A combination table.
- Use the intended devices and known-good cables. Test each device alone on its intended port.
- Connect the primary device first, wait for stable charging, then add one secondary load.
- Repeat with the reverse connection order because some allocation policies are order-sensitive.
- Record whether charging pauses, which device reconnects and whether the final state remains stable.
- If a suitable analyzer is available, record the negotiated voltage and current without treating one reading as certification.
A repeatable acceptance test needs the same devices, cables, battery states and port order. A phone near full charge may request less power than one at a low state, so comparison runs should begin under similar conditions.
Interpret a brief interruption separately from instability
| Symptom | First controlled check | More likely expected behavior when | More likely a fault when |
|---|---|---|---|
| Laptop charging icon blinks once | Repeat the same connection order with the same cables | The event occurs only as a second load is attached and charging stabilizes afterward | It repeats with no load change or never recovers |
| Phone drops from fast charging | Disconnect other devices, then add them one at a time | The published port map assigns a lower combined-output ceiling | The single-port baseline also fails with a known-good cable |
| USB drive or dock resets | Separate charging from data by testing the dock with its recommended power path | The dock loses bus power during a contract change | Resets continue on a stable dedicated supply |
| One port will not charge | Swap only the cable, then swap only the physical port | That port is disabled in the documented combination | The same port fails alone with multiple known-good devices |
| Charger cycles repeatedly | Remove all loads and rebuild the setup one device at a time | No published behavior supports the cycle | Any connector is loose, damaged, unusually hot or unstable |
A single, predictable renegotiation tied to a documented load change is different from random dropout. Stop testing if a plug is damaged, the charger or connector becomes unusually hot, power cycles continue, or the setup only works when a cable is held at an angle. Do not repeatedly reconnect a suspect high-power path to force a result.
Choose a charger from the simultaneous workload backward
Add the realistic device requirements, then look for a published allocation that preserves the most important load. A laptop-plus-phone setup may need a priority USB-C port. A desk with a dock, storage and a tablet may need independent supplies if even a short bus-power interruption is unacceptable.
Use the USB-C charger guide to screen wattage, PD profiles and port sharing, then verify the exact SKU. Product families often share an enclosure while using different allocation maps, so a photo or headline wattage is not sufficient purchasing evidence.
Build an acceptance record for sourcing
An approval record should bind the charger model to a port map, device set, cable set, connection order and stable final contracts; otherwise a “100W passed” note cannot be reproduced. Include single-port baselines, all required simultaneous combinations, reconnect behavior, sustained charging and the rejection conditions for cycling or abnormal heat.
If firmware, controller, converter design or port labeling changes, repeat the shared-load test. A supplier substitution can preserve the total number on the case while changing which port receives priority or whether devices briefly reset.
Bottom line
Multi-port charger power is negotiated and shared, not multiplied by the number of sockets. A brief transition can occur when the charger reallocates its budget and devices establish new contracts. Read the port-combination table, test the exact workload in both connection orders, and distinguish one documented renegotiation from repeated instability.
Sources
- Texas Instruments — Power Sharing in USB Type-C Applications — a technical explanation of allocating a limited system power budget across USB-C ports.
- Texas Instruments — USB PD Power Negotiations — application guidance on PDO offers, RDO selection and renegotiating power contracts in shared multi-port systems.