https://bugzilla.kernel.org/show_bug.cgi?id=213579 --- Comment #24 from wse@xxxxxxxxxxxxxxxxxxx --- (In reply to wse from comment #21) > (In reply to Riccardo Mori from comment #20) > > (In reply to Andy Shevchenko from comment #19) > > > What I'm wondering is if the pin list is broken and actual pin 57 is > > > something else (+- few pins according to the current driver). May be > > someone > > > can install libgpiod tools (such as `gpiomon`) and run with pins that are > > > already in GPIO mode without [ACPI] bit set. Something like `gpiomon > > > gpiochip0 43` (for pin #56) and `gpiomon gpiochip0 47` (for pin #60). > Then > > > if touchpad (when being touched I presume) generates the interrupts this > > > will show them. But it's unlikely as > > > per success story described in the bug #211957 where pin under question > has > > > much higher number and any pin list disturbance will be noticed > > immediately. > > > > > > Thank you for helping us Andy. > > I tried `gpiomon gpiochip0 $PIN` with the non-ACPI pins numbered from 15 up > > to 100 but unfortunately I didn't get any output. > > Maybe it's a typo in the firmware and it actually should be 157 or 257 > > Other interrupt related bug reports found with other touchpads, always had > interrupt pins in the 2xx range I tested available pins between 200 and 300 with no avail .. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
