On Wed, Feb 12, 2020 at 02:12:54PM +0100, Oliver Neukum wrote:
> Am Dienstag, den 11.02.2020, 16:44 +0200 schrieb Heikki Krogerus:
> > On Tue, Feb 11, 2020 at 03:34:37PM +0100, Oliver Neukum wrote:
>
> > > >
> > >
> > > yes I got that one. Thanks for the tip.
> >
> > OK, cool! Let me know if the tps6598x.c driver works with that.
> >
> > thanks,
>
> Sorry for my earlier rather short report. It turns out that even
> i2c_multi_instantiate does not load. A bit of debugging points
> to rather inexplicable ACPI code:
>
> Device (UCM1)
> {
> Name (_HID, "INT3515") // _HID: Hardware ID
> Name (_UID, Zero) // _UID: Unique ID
> Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings
> {
> Name (SBFB, ResourceTemplate ()
> {
> I2cSerialBusV2 (0x0038, ControllerInitiated, 0x00061A80,
> AddressingMode7Bit, "\\_SB.PCI0.I2C0",
> 0x00, ResourceConsumer, , Exclusive,
> )
> })
> Name (SBFI, ResourceTemplate ()
> {
> Interrupt (ResourceConsumer, Level, ActiveLow, Exclusive, ,, _Y28)
> {
> 0x00000000,
> }
> })
> CreateDWordField (SBFI, \_SB.PCI0.I2C0.UCM1._CRS._Y28._INT, GINT) // _INT: Interrupts
> GINT = INUM (UCG1)
> Return (ConcatenateResTemplate (SBFB, SBFI))
> }
>
> Method (_STA, 0, NotSerialized) // _STA: Status
> {
> If ((UCSI == One))
> {
> Return (0x0F)
> }
> Else
> {
> Return (Zero)
> }
> }
> }
>
> And indeed 'status' is 0 in sysfs. I am puzzled. I can see no sense in that unless
> I am supposed to use ucsi_acpi but there is no node for that.
The "UCSI" in that condition is just a variable name. It does not
actually have anything to do with the actual UCSI interface.
It looks to me like the operating system is not even made aware of the
connectors on that laptop. That is fairly common unfortunately.
The connectors will work, the firmware takes care of everything, but
they are simply not visible to the operating system. There is of
course also no way to for example swap the roles, or do anything else.
thanks,
--
heikki
