From: Tony Lindgren <tony@atomide.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
Javier Martinez Canillas <javier@dowhile0.org>,
santosh shilimkar <santosh.shilimkar@oracle.com>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Linux GPIO List <linux-gpio@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>, Sekhar Nori <nsekhar@ti.com>
Subject: Re: [PATCH REPOST] gpio: omap: use raw locks for locking
Date: Wed, 1 Jul 2015 04:29:29 -0700 [thread overview]
Message-ID: <20150701112928.GW4156@atomide.com> (raw)
In-Reply-To: <20150701073205.GT4156@atomide.com>
* Tony Lindgren <tony@atomide.com> [150701 00:34]:
>
> This should be OK for most cases as the GPIO interrupt devices are
> typically on some external bus like I2C or GPMC. The hurting case
> would be bitbanging GPIO devices, like the CBUS I2C driver.
Thinking about it the CBUS I2C driver does not need interrupts
for the bitbanging part either :)
So I think we can just make it threaded IRQ for GPIO.
Tony
next prev parent reply other threads:[~2015-07-01 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 17:06 [PATCH REPOST] gpio: omap: use raw locks for locking Sebastian Andrzej Siewior
2015-06-19 17:42 ` santosh shilimkar
2015-06-19 21:54 ` Javier Martinez Canillas
2015-06-22 7:08 ` Tony Lindgren
2015-06-30 10:55 ` Grygorii Strashko
2015-06-30 16:36 ` Sebastian Andrzej Siewior
2015-07-01 7:32 ` Tony Lindgren
2015-07-01 11:29 ` Tony Lindgren [this message]
2015-07-07 8:58 ` Grygorii Strashko
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=20150701112928.GW4156@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=gnurou@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=javier@dowhile0.org \
--cc=khilman@deeprootsystems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@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).