diff options
author | 2022-02-13 14:05:19 +0100 | |
---|---|---|
committer | 2022-02-17 16:30:18 +0100 | |
commit | 582ab24e096fd591026de6f1bbae104e45fecf0f (patch) | |
tree | d1bb6f66f18422a561df88eeac4da7e83b26bf29 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | usb: dwc3: pci: Set the swnode from inside dwc3_pci_quirks() (diff) | |
download | wireguard-linux-582ab24e096fd591026de6f1bbae104e45fecf0f.tar.xz wireguard-linux-582ab24e096fd591026de6f1bbae104e45fecf0f.zip |
usb: dwc3: pci: Set "linux,phy_charger_detect" property on some Bay Trail boards
Some Android x86 tablets with a Bay Trail (BYT) SoC and a Crystal Cove
PMIC, which does not support charger-detection, rely on the TUSB1211 phy
for charger-detection.
Windows tablets with the same SoC + PMIC often use an extra chip for
charger-detection like the FSA831A. But since on Android tablets
the designers already need to add a TUSB1211 phy to support device/gadget
mode the phy is used to do charger-detection instead.
These Android x86 tablets can be identified by the unique combination of
a Bay Trail SoC (already checked for by PCI-ids) + a Crystal Cove PMIC +
not using the standard ACPI battery and ac drivers. Where as on Windows
tablets the standard ACPI battery and ac drivers will be used on BYT
boards with a Crystal Cove PMIC.
Set a special kernel-internal (so not part of the dt-bindings)
"linux,phy_charger_detect" property on these boards, which tells the
tusb1210 driver to enable charger-detection.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Link: https://lore.kernel.org/r/20220213130524.18748-5-hdegoede@redhat.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions