Comment 75 for bug 1949394

Hello,
I have been randomly browsing Your DSDT table and I spotted this:

            Device (TPD0)
            {
                Name (_ADR, One) // _ADR: Address
                Name (_HID, "ELAN1000") // _HID: Hardware ID
                Name (_CID, "PNP0C50") // _CID: Compatible ID
                Name (_UID, One) // _UID: Unique ID
                Name (_S0W, 0x04) // _S0W: S0 Device Wake State
                Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method
                {
                    If (LEqual (Arg0, Buffer (0x10)

What this reminds You of?

And then I searched for PNP0C50 and found
http://msdn.microsoft.com/en-us/library/windows/hardware/jj131711%28v=vs.85%29.aspx
"This section describes plug and play support for devices that support HID over the I2C transport."

And in the initiaization sequence on this page:

"The following list gives the enumeration sequence. Note that the order of this list may change in future versions of Windows.

 1. Retrieve ACPI ASL code for HID I2C DEVICE from System BIOS.
 2. Retrieve HID Descriptor from the Device.
        Write HID Descriptor Address
        Read HID Descriptor
 3. Issue a SET_POWER to the Device.
        Write SET_POWER Command
"