Contribute
Register

<< Solved >> voodooi2c issues SYNA3602

Status
Not open for further replies.
@tmbt

Hello, no need to apologize, I knew you were in a hurry and I also was going to sleep

anyways it's as you said that I checked someone else's DSDT not yours lol

so yeah it's not the normal voodooi2c patch unfortunately, tbh I don't think I came a cross something like that but kinda got some crazy idea (probably not gonna work but give it a try)

so I edited the _CRS method to kinda match the standard SBFB,SBFG

Code:
            Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
            {
                Name (SBFB, ResourceTemplate ()
                {
                    I2cSerialBusV2 (0x002C, ControllerInitiated, 0x000186A0,
                        AddressingMode7Bit, "\\_SB.PCI0.I2C1",
                        0x00, ResourceConsumer, , Exclusive,
                        )

                })
             
                Name (SBFG, ResourceTemplate ()
                {
                     GpioInt (Level, ActiveLow, Exclusive, PullDefault, 0x0000,
                        "\\_SB.PCI0.GPI0", 0x00, ResourceConsumer, ,
                        )
                        {   // Pin list
                            0x0000
                        }
                })


                CreateWordField (SBFB, 0x38, INTH)
                INTH = GNUM (0x0202000E)
             
                Return (ConcatenateResTemplate (SBFB, SBFG))
            }

If you feel that this is not a stupid idea then give it a try :)

Edit: uploaded TPD1.zip
copy SSDT-I2C to your acpi and copy the renaming patches to your config
Note that this SSDT has Windows 10 Patch, and GPIO Controller Enable patch so if you got those patches disable them!
Hello,
i've tried but that didn't work sadly.

I think there is a problem using SBFB and INTH (different size or something similar) ...

These are the last lines of the code before KP :
ACPI Error : Field INTH at 464 excceeds Buffer SBFB size 280 (bits)
After that i got a ACPI Error parsing the _CRS method AE_AW_BUFFER
and finally a VoodooI2C error saying Could not initilize nub for SYNA3602

:(
 
@moh.96 .. I m going to try to add some method I saw in another user dsdt from 2019 in gitter voodooi2c support chat ..
Do you have any idea why I can override the pin configuration with a value of my choice?
 
Solved !


You've to use Windows 10 (using a live on USB is ok too) and check under the device manager the Hardware ID name for the touchpad HID :
It should be something like HID/SYNA3602&Col02 (not just SYNA3602).


After that you have to edit VoodooI2CHID.kext info.plist under IOKitPersonalities and change it from SYNA3602 to the one you've read in Windows 10.
After that you've to go under the personality and mod also the IOClass name to match the one you've just saw in Windows 10 and after reboot the touchpad will work !

For my example (SYNA3602&Col02) the personality name is : VoodooI2CHIDSYNA3602&Col2Device and the IOClass name is the same VoodooI2CHIDSYNA3602&Col2Device.

I hope to have helped all the people with the same problem

Mattia
 
Hi @tmbt
Tell me what I'm doing wrong? I have SYNA3602 and nothing can make it work. Thanks
 

Attachments

  • DSDT.aml
    163.3 KB · Views: 77
  • 1.png
    1.png
    11.3 KB · Views: 227
  • 11.png
    11.png
    74.7 KB · Views: 225
  • MacBook Pro — Blaise.ioreg
    20 MB · Views: 124
Status
Not open for further replies.
Back
Top