From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "Miao, Jun" <jun.miao@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] pinctrl: intel: use new GPIO line value setter callbacks
Date: Tue, 10 Jun 2025 23:33:22 +0300 [thread overview]
Message-ID: <aEiWkmT9HPlR8u72@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=MepPni55s9mpCkZ_XrWtT3hOhSTN_QTzpNr_Qzk-YKP7Q@mail.gmail.com>
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@intel.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
next prev parent reply other threads:[~2025-06-10 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 12:58 Bartosz Golaszewski
2025-06-10 12:58 ` [PATCH 1/4] pinctrl: baytrail: " Bartosz Golaszewski
2025-06-10 12:58 ` [PATCH 2/4] pinctrl: cherryview: " Bartosz Golaszewski
2025-06-10 12:58 ` [PATCH 3/4] pinctrl: intel: " Bartosz Golaszewski
2025-06-10 12:58 ` [PATCH 4/4] pinctrl: lynxpoint: " Bartosz Golaszewski
[not found] ` <PH7PR11MB845555F9AA0823B53EFD48BF9A6AA@PH7PR11MB8455.namprd11.prod.outlook.com>
2025-06-10 15:32 ` [PATCH 0/4] pinctrl: intel: " Bartosz Golaszewski
2025-06-10 20:33 ` Andy Shevchenko [this message]
2025-06-10 20:29 ` Andy Shevchenko
2025-06-11 4:36 ` Mika Westerberg
2025-06-11 8:28 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aEiWkmT9HPlR8u72@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=jun.miao@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®