ec: Consider removing physical USB2 switch |
|||
Issue descriptionFor most boards supporting BC 1.2, we have a USB2 switch on the board or in the charger chip (e.g. bd9995x). We turn off the switch when we want to avoid a possible conflict on D+/D- line between charging port detection (from the charger) and USB2 enumeration (from USB2 PHY on AP). Theoretically, the physical USB2 switch can be replaced with a 'virtual' one (i.e. better sync mechanism between EC and AP). To be more specific, we can always tell AP to power off USB2 PHY, which is equivalent to turning off the physical USB2 switch.
,
Mar 15 2018
,
Mar 15 2018
My understanding follows Vincent's. For example, the TI BQ24392 will perform BC 1.2 detection and then connect the data lines to the system if necessary / depending upon the result. I think the pericom one behaves similarly, but also has the option for manually controlling the switches.
,
Mar 15 2018
Sorry, I though we have a physical switch for some projects. It looks like this switch is always incorporated into the chips in charge of BC 1.2 detection. Among all the chips we use so far, rt946x is the only one doing BC 1.2 detection but not coming with a 'free', built-in switch. Scarlet is the only board using rt946x so far, and we're trying to enable BC 1.2: https://chromium-review.googlesource.com/#/c/chromiumos/platform/ec/+/905934/ So maybe this concern is only valid for Scarlet for now.
,
Mar 15 2018
Yeah, we generally only go with solutions that have built-in switches. There usually isn't much benefit to the non-switch solutions (especially since the behavior of the host port may be undefined depending on the SoC), except for the RT9467 case where it was significantly cheaper and RK explicitly acknowledged it would work. So I don't think there's anything to do here...
,
Mar 15 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by vpalatin@google.com
, Mar 15 2018