LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Jason Cooper" <jason@lakedaemon.net>,
"Hua Jing" <jinghua@marvell.com>, "Ken Ma" <make@marvell.com>,
"Antoine Tenart" <antoine.tenart@free-electrons.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Nadav Haklai" <nadavh@marvell.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"Victor Gu" <xigu@marvell.com>,
"Neta Zur Hershkovits" <neta@marvell.com>,
"Miquèl Raynal" <miquel.raynal@free-electrons.com>,
"Gregory CLEMENT" <gregory.clement@free-electrons.com>,
"Marcin Wojtas" <mw@semihalf.com>,
"Wilson Ding" <dingwei@marvell.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH] pinctrl: armada-37xx: Add edge both type gpio irq support
Date: Tue, 20 Mar 2018 22:56:15 +0100 [thread overview]
Message-ID: <20180320215615.zszlfw5pnecfqhpt@pengutronix.de> (raw)
In-Reply-To: <20171031131617.GA11647@lunn.ch>
On Tue, Oct 31, 2017 at 02:16:17PM +0100, Andrew Lunn wrote:
> > Patch applied.
> >
> > The discussion here is interesting, it is customary for GPIO drivers
> > to implement double-edge detection emulation by swapping the
> > edge detector around like this.
>
> Hi Linus
>
> I was not aware this was customary.
>
> > It might be possible to collect some generic information about
> > this in the Documentation/gpio/driver.txt document.
>
> Yes, i think it should be documented somewhere. Even in the use case
> here, detecting an SD card being inserted/removed, you could get some
> bounce on the microswitch, miss an edge, and be in the wrong state.
Maybe I'm wrong, but I wonder if there could be a set of helper
functions provided by the gpio core that helps implementing this
software simulation of IRQ_TYPE_EDGE_BOTH reliably (i.e. as good as
possible in software) to prevent common mistakes.
First draft:
disable_irq_nosync(...);
level = gpio_get(...);
retry:
if (level)
configure_for_falling_edge();
else
configure_for_raising_edge();
postlevel = gpio_get(...);
if (level != postlevel) {
mark_irq_pending(); /* something like desc->istate |= IRQS_PENDING */
level = postlevel;
goto retry;
}
enable_irq(...); /* this resends the irq */
I think this only looses an event if there is an edge between gpio_get
and the configure_for_${some}_edge and another before postlevel = ...
that make the two events invisible. But I think this is okish, as a
short spike might also be missed by a hw-edge-detector. And compared to
the current code there should be no way to end in a state where we
configured for raising edge and the level is already high.
When the gpio toggles quickly this might keep the cpu busy in an endless
loop, but such a sequence would also block a controller that can trigger
on both edges in hardware. Not sure if breaking the loop at some point
is sensible anyhow. Also calling the irq handlers would be beneficial,
but I don't know if/how this works without (more) racing.
A similar approach would be great to have to "simulate" level sensitive
irqs if the hardware only implements edge logic (which affects
armada-37xx, too, which annoys me).
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2018-03-20 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 13:10 Gregory CLEMENT
2017-10-19 13:38 ` Andrew Lunn
2017-10-27 12:57 ` Gregory CLEMENT
2017-10-27 19:39 ` Andrew Lunn
2017-10-31 12:07 ` Linus Walleij
2017-10-31 13:16 ` Andrew Lunn
2017-10-31 13:27 ` Linus Walleij
2018-03-20 21:56 ` Uwe Kleine-König [this message]
2018-03-21 8:02 ` 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=20180320215615.zszlfw5pnecfqhpt@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@free-electrons.com \
--cc=dingwei@marvell.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jinghua@marvell.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=make@marvell.com \
--cc=miquel.raynal@free-electrons.com \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=neta@marvell.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=xigu@marvell.com \
--subject='Re: [PATCH] pinctrl: armada-37xx: Add edge both type gpio irq support' \
/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
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).