From: Peter Rosin <peda@lysator.liu.se>
To: linux-gpio@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Peter Rosin <peda@lysator.liu.se>, Peter Rosin <peda@axentia.se>
Subject: [RESEND RFC PATCH 0/2] Expose the PIO_ISR register on SAMA5D3
Date: Tue, 8 Dec 2015 04:20:06 +0100 [thread overview]
Message-ID: <1449544808-3163-1-git-send-email-peda@lysator.liu.se> (raw)
From: Peter Rosin <peda@axentia.se>
Hi!
I have a signal connected to a gpio pin which is the output of
a comparator. By changing the level of one of the inputs to the
comparator, I can detect the envelope of the other input to
the comparator by using a series of measurements much in the
same maner a manual ADC works, but watching for changes on the
comparator over a period of time instead of only the immediate
output.
Now, the input signal to the comparator might have a high frequency,
which will cause the output from the comparator (and thus the GPIO
input) to change rapidly.
A common(?) idiom for this is to use the interrupt status register
to catch the glitches, but then not have any interrupt tied to
the pin as that could possibly generate pointless bursts of
(expensive) interrupts.
So, these two patches expose an interface to the PIO_ISR register
of the pio controllers on the platform I'm targetting. The first
patch adds some infrastructure to the gpio core and the second
patch hooks up "my" pin controller.
But hey, this seems like an old problem and I was surprised that
I had to touch the source to do it. Which makes me wonder what I'm
missing and what others needing to see short pulses on a pin but not
needing/wanting interrupts are doing?
Yes, there needs to be a way to select the interrupt edge w/o
actually arming the interrupt, that is missing. And probably
other things too, but I didn't want to do more work in case this
is a dead end for some reason...
Cheers,
Peter
Peter Rosin (2):
gpio: Add isr property of gpio pins
pinctrl: at91: expose the isr bit
Documentation/gpio/sysfs.txt | 12 ++++++++++
drivers/gpio/gpiolib-sysfs.c | 30 ++++++++++++++++++++++++
drivers/gpio/gpiolib.c | 15 ++++++++++++
drivers/pinctrl/pinctrl-at91.c | 50 ++++++++++++++++++++++++++++++++++++----
include/linux/gpio/consumer.h | 1 +
include/linux/gpio/driver.h | 2 ++
6 files changed, 106 insertions(+), 4 deletions(-)
--
1.7.10.4
next reply other threads:[~2015-12-08 3:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 3:20 Peter Rosin [this message]
2015-12-08 3:20 ` [RESEND RFC PATCH 1/2] gpio: Add isr property of gpio pins Peter Rosin
2015-12-11 12:43 ` Linus Walleij
2015-12-08 3:20 ` [RESEND RFC PATCH 2/2] pinctrl: at91: expose the isr bit Peter Rosin
2015-12-09 8:01 ` [RESEND RFC PATCH 0/2] Expose the PIO_ISR register on SAMA5D3 Ludovic Desroches
2015-12-09 8:56 ` Peter Rosin
2015-12-11 12:53 ` Linus Walleij
2015-12-12 18:02 ` Jonathan Cameron
2015-12-12 18:06 ` Jonathan Cameron
2015-12-14 10:38 ` Peter Rosin
2015-12-15 14:20 ` Linus Walleij
2015-12-17 23:19 ` Peter Rosin
2015-12-19 16:06 ` Jonathan Cameron
2015-12-22 8:44 ` Linus Walleij
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=1449544808-3163-1-git-send-email-peda@lysator.liu.se \
--to=peda@lysator.liu.se \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=plagnioj@jcrosoft.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;
as well as URLs for NNTP newsgroup(s).