From: Neil Armstrong <narmstrong@baylibre.com>
To: linux-amlogic@lists.infradead.org
Subject: Re: GPIO Interrupts
Date: Fri, 24 Jul 2020 10:05:52 +0200 [thread overview]
Message-ID: <a212ea3d-dc08-73e6-0706-79c01d0be377@baylibre.com> (raw)
In-Reply-To: <1356858918.38098893.1595529644632.JavaMail.zimbra@mailid.telus.net>
Hi,
On 23/07/2020 20:40, honsch@telus.net wrote:
> Hi there,
> I've been working on a ODroid C2 project for a while, (meson, gxbb) and I cannot get gpio interrupts working from the devicetree.
>
> I'm trying to hook up the PPS gpio driver as well as some gpio IIO triggers. I had it all working on a 4.x kernel a couple of years ago but on the 5.7 it's a no-go.
>
> The pinctrl-meson driver is missing the hook for gpiod_to_irq(), and the irq-meson-gpio driver is missing the activate function for platform_get_irq() to function.
>
> Has either of these paths ever been implemented or tested? Am I missing something simple?
The only available driver for GPIO interrupts is irq-meson-gpio and should be enough for most of your use-cases
if you pass the GPIO interrupt as `interrupt = ` and `interrupt-parent =` as we do for the Ethernet PHY on some
boards.
For historical & HW architecture reasons, it's not possible to implement upstream support for the gpiod_to_irq() in the pinctrl driver.
Neil
> Thanks.
>
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2020-07-24 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 18:40 GPIO Interrupts honsch@telus.net
2020-07-24 8:03 ` Jerome Brunet
2020-07-24 8:05 ` Neil Armstrong [this message]
2020-07-25 6:00 ` E Honsch
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=a212ea3d-dc08-73e6-0706-79c01d0be377@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).