On Tue, 11 Mar 2025 15:03:59 +0100, Genes Lists <lists@xxxxxxxxxxxx> said:On Sat, 2025-03-08 at 15:45 -0500, Genes Lists wrote:......
There are two problems here. The issue you're seeing is fixed in next butnot in mainline due to my omission. I will send a patch for that.On the other hand, the pinctrl driver in question should be fixed too.Can you try the following change:diff --git a/drivers/pinctrl/intel/pinctrl-intel.cb/drivers/pinctrl/intel/pinctrl-intel.cindex d889c7c878e2..0c6925b53d9f 100644--- a/drivers/pinctrl/intel/pinctrl-intel.c+++ b/drivers/pinctrl/intel/pinctrl-intel.c@@ -1068,7 +1068,11 @@ static int intel_gpio_get_direction(structgpio_chip *chip, unsigned int offset)pin = intel_gpio_to_pin(pctrl, offset, NULL, NULL);if (pin < 0)- return -EINVAL;+ /*+ * For pins configured to functions other than GPIO, default+ * to the safe INPUT value.+ */+ return GPIO_LINE_DIRECTION_IN;reg = intel_get_padcfg(pctrl, pin, PADCFG0);if (!reg)?FYI: This was uncovered by commit 9d846b1aebbe ("gpiolib: check thereturn value of gpio_chip::get_direction()").Bart
--
Attachment:
signature.asc
Description: This is a digitally signed message part