Hi, Joseph Kogut <joseph.kogut@xxxxxxxxx> writes: > Hi Felipe, > > That's some great information, thanks! > > At first glance, the DSDT table has two interesting bits. (I would > paste the decompiled source, but I think it may be copyrighted? > Correct me if I'm wrong.) The first is the USB mux, an SMSC USB3750 > connected to I2C1. According to the datasheet, this IC supports > switching the USB data lanes between functions. This looks promising. > > The second interesting bit is a device named "OTG1". The _STA method > of OTG1 checks the value of OTGM--defined earlier as an 8-bit field in > GNVS (NVRAM?)--and returns 0xF if it's not equal to zero, otherwise it > returns zero. I'm guessing this is the host controller, based on the > device name, "Baytrail XHCI controller (Synopsys core/OTG)". this is the peripheral IP :-) Synopsys core/OTG tells me it's dwc3 :-) > There's a field called OTGD in the power management capability > registers opregion, but it's not referenced anywhere else. > > There doesn't appear to be anything else related to the device > controller. The only OS interface string check appears to be in the > configuration of the PCI bus, and it only checks against various > versions of Windows. > > I'm thinking my next step is to boot into Android and dump the DSDT > table, and see if it's the same. I'm betting it's not. It might be the same, yes. But I'm guessing _STA will return a different value for that OTG1 device :-) And maybe this mux has something to do with it too. You can fiddle with the mux by finding its doc, and using i2c-tools (specially i2cset and i2cget) to write/read registers. -- balbi
Attachment:
signature.asc
Description: PGP signature
