From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH v4 0/2] gpio: sch: Interrupt support
Date: Tue, 16 Mar 2021 18:26:11 +0200 [thread overview]
Message-ID: <20210316162613.87710-1-andriy.shevchenko@linux.intel.com> (raw)
I'm now struggling to test this on Intel Minnowboard (v1), but it seems not
working and it's only one possible pin to test, so I have to take soldering
iron in my hands and do some hardware hacks to test. Meanwhile I sent this in
order to Jan to test on his side that everything is working on their platform.
Changes in v4:
- turned to GPIO core infrastructure of IRQ chip instantiation (Linus)
- converted IRQ callbacks to use better APIs
- use handle_bad_irq() as default handler and now I know why, see
eb441337c714 ("gpio: pca953x: Set IRQ type when handle Intel Galileo Gen 2")
for the real example what happens if it's preset to something meaningful
- fixed remove stage (we have to remove SCI handler, which wasn't done in v3)
Changes in v3 (https://lore.kernel.org/linux-gpio/cover.1574277614.git.jan.kiszka@siemens.com/T/#u):
- split-up of the irq enabling patch as requested by Andy
Jan Kiszka (2):
gpio: sch: Add edge event support
gpio: sch: Hook into ACPI SCI handler to catch GPIO edge events
drivers/gpio/gpio-sch.c | 146 ++++++++++++++++++++++++++++++++++++++--
1 file changed, 140 insertions(+), 6 deletions(-)
--
2.30.2
next reply other threads:[~2021-03-16 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 16:26 Andy Shevchenko [this message]
2021-03-16 16:26 ` [PATCH v4 1/2] gpio: sch: Add edge event support Andy Shevchenko
2021-03-16 16:26 ` [PATCH v4 2/2] gpio: sch: Hook into ACPI SCI handler to catch GPIO edge events Andy Shevchenko
2021-03-16 17:05 ` Andy Shevchenko
2021-03-16 20:49 ` Andy Shevchenko
2021-03-17 6:57 ` Jan Kiszka
2021-03-17 9:52 ` Andy Shevchenko
2021-03-17 9:57 ` Jan Kiszka
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=20210316162613.87710-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=jan.kiszka@siemens.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).