Firmware reporting `POWER_MISMATCH` on several beefy hub models

Discussion moved here from !36 (comment 251138).

Context

From the Hubs section in the dp-alt-mode-adapters.org file:

Name	Prd Id	Function	USB ID	Notes	URL
Anker 563 (2021 model with 5 Gbps)	A8385	USB-C Hub (11-in-1)	291a:8385	Won’t charge, POWER_MISMATCH per tps6598x trace	https://www.anker.com/eu-de/products/a8385
Anker 565 (2023 model with 10 Gbps)	A8388	USB-C Hub (11-in-1)	291a:8388	Won’t charge, POWER_MISMATCH per tps6598x trace	https://www.anker.com/eu-de/products/a8388

Discussion thread

I’ve been trying to figure out why, of all hubs, all the relatively expensive Anker models are failing to charge the phone, while at the same time, the trace consistently emits the POWER_MISMATCH flag.

Anker products, especially the expensive ones, have a track record of being able to charge all the things six ways to Sunday with so many jiggerwatts.
Can you point me to a resource that might help me investigate what’s really happening, i.e. whether it’s a fault in the hub, just a plain incompatibility with the TPS/TPS firmware, or even something that might be fixable?

@guido.gunther replied:

The common source is often that the hub doesn't offer us a contract we can deal with (e.g. 5V/3A) as most hubs target laptops that then e.g. want a higher voltage.

@angus.ainslie replied:

@claudia do you have dmesg logs when using the Anker hubs ?

We had a report recently where an HP hub was offering 5V/5A and the battery charger driver was limiting the current to 500mA because that was more than 3A allowed by the spec. We need to make a 1 line change to the battery driver to fix that by accepting the 5A but limiting the charge current to 3A but it might something similar for the Anker hubs.