> The real issue is the chipsets; because of cost they spend essentially nothing on firmware. You can add your own controller to manage the issue but that adds

> The real issue is the chipsets; because of cost they spend essentially nothing on firmware. You can add your own controller to manage the issue but that adds to the BOM and requires finding a programmer who can handle embedded AND is willing to write a very policy, but that adds cost too. Thanks, that sounds plausible to me, although it's a shame, because it'd make such chargers so much better. > I agree it’s not that hard, though figuring out a policy that won’t annoy people is hard (I’d implement of sorting devices by what they ask for, then go from high to low doing your best to satisfy them, with nobody getting less than the USB 2.1 baseline, though I know that would piss some people off). I mean right now there is already such a policy: Each device can only get as much as the port is rated for depending on how many and which ports are occupied. They could just leave the numbers as they are and label them as "minimum power provided by the port". If a device requires less power they can provide this surplus power to devices which request more, if the port is capable to handle that.