On 20.03.2024 22:26, Heiner Kallweit wrote:
> On 20.03.2024 22:07, Andy Shevchenko wrote:
>> On Wed, Mar 20, 2024 at 09:21:34PM +0100, Heiner Kallweit wrote:
>>> On 20.03.2024 16:59, Andy Shevchenko wrote:
>>>> On Wed, Mar 20, 2024 at 03:56:29PM +0100, Heiner Kallweit wrote:
>>
>> ...
>>
>>>> grep 0000001b /sys/kernel/debug/pinctrl/*/pins
>>>
>>> pin 3 (GPPC_B_3) 3:INTC1057:00 GPIO 0x80100102 0x0000001b 0x00000000 [LOCKED tx]
>>> pin 82 (GPP_F_7_EMMC_CMD) 135:INTC1057:00 GPIO 0x44000300 0x0000001b 0x00000000 [LOCKED full, ACPI]
>>> pin 182 (GPPC_C_13) 269:INTC1057:00 GPIO 0x44000300 0x0000001b 0x00000000 [LOCKED full, ACPI]
>>
>> I was not correct, the value to grep is '0000[0-3][0-9a-f]1b' as there pull
>> up/down can be enabled.
>>
> Result is the same
>
>> Nevertheless from the above the pin 3 is one that is enabled as GPIO input with
>> RTE 27 and direct IRQ. If it's a culprit, try to add in the pinctrl-intel.c at
>> the end of .probe:
>>
>> {
>> void __iomem *padcfg0;
>> u32 value;
>>
>> padcfg0 = intel_get_padcfg(pctrl, 3, PADCFG0);
>>
>> value = readl(padcfg0);
>> value |= PADCFG0_GPIOTXDIS;
>> value |= PADCFG0_GPIORXDIS;
>> writel(value, padcfg0);
>> }
>>
>> If it helps, it will show the BIOS bug (likely).
>>
> Wow, this indeed fixes the issue for me. Thanks a lot!
> For my understanding: Shall we (kernel driver) rely on the BIOS to configure
> GPIO's properly? Or better assume that GPIO's are in an unknown state on
> driver load and configure them for our needs?
> IOW: If we assume that other systems may have similar issues, should "some driver"
> use e.g. the pinctrl API to configure relevant pins?
>
By the way: Great support! I wish I could get the same support level everywhere.
