[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aEiWkmT9HPlR8u72@smile.fi.intel.com>
Date: Tue, 10 Jun 2025 23:33:22 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: "Miao, Jun" <jun.miao@...el.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Linus Walleij <linus.walleij@...aro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] pinctrl: intel: use new GPIO line value setter
callbacks
On Tue, Jun 10, 2025 at 05:32:53PM +0200, Bartosz Golaszewski wrote:
> On Tue, Jun 10, 2025 at 5:30 PM Miao, Jun <jun.miao@...el.com> wrote:
> > Excuse me,
> > I have a problem
> > echo 631 > /sys/class/gpio/export
> > echo rising > /sys/class/gpio/gpio631/edge
> > [18090.472396] emmitsburg-pinctrl INTC1071:00: pin 119 cannot be used as IRQ
Check the pin configuration in /sys/kernel/debug/pinctrl/INTC1071:00/pins. But
I believe this is the wrong driver used for not yet released HW.
I suggest you not to communicate in public for this type of issues. We have
internal mailing list for that and other channels to discuss.
> > [18090.472408] genirq: Setting trigger mode 1 for irq 245 failed (intel_gpio_irq_type+0x0/0x130)
> >
> > How to set the gpio631 as IRQ mode ?
>
> Is this a regression caused by this series?
I am pretty sure it's irrelevant. IRQ is input mode, the value setters
shouldn't be involved in that at all.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists