https://bugzilla.kernel.org/show_bug.cgi?id=213579 --- Comment #39 from Riccardo Mori (patacca@xxxxxxxxxxxxx) --- (In reply to Rod Thomas from comment #37) > a) Where 44 comes from - is this the GPIO pin that corresponds to acpi pin > 57? You can find the mappings with `cat /sys/kernel/debug/pincntrl/INT346\:00/pins` For example let's analyze the row for pin 57: `pin 57 (SLP_S0B) 44:INT34C6:00 mode 1 0x44000700 0x00000051 0x00000000 [LOCKED full, ACPI]` You can see that it is referring to line SLP_S0B, it is mapped to GPIO 44 and is not in GPIO mode (mode 1) and is fully locked and has ACPI ownership. In contrast pin 37: `pin 37 (CLKOUT_48) 140:INT34C6:00 GPIO 0x40800102 0x0000003d 0x00000000 [LOCKED tx]` it is referring to line CLKOUT_48, it is mapped to GPIO 140, it is in GPIO mode and ACPI has no ownership of it > Sorry to be a noob but just want to understand this before I embark on my > first > kernel build. I see you are using an archlinux based distro so you might find useful this repo I just created to build linux with this hack: https://github.com/patacca/linux-tigerlake-hack -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
