From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: concurrent access to gpiolib on mxc.
Date: Tue, 3 Aug 2010 21:36:11 +0200 [thread overview]
Message-ID: <20100803193611.GA18431@pengutronix.de> (raw)
In-Reply-To: <4C58643E.2040105@xenomai.org>
Hi Gilles,
On Tue, Aug 03, 2010 at 08:47:26PM +0200, Gilles Chanteperdrix wrote:
> the gpiolib support on mxc seems to lack protection against concurrent
> access. Is it OK for this SOC family?
http://git.pengutronix.de/?p=imx/linux-2.6.git;a=commitdiff;h=14cb0de
is on it's way into mainline. Note that you need
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=6280/1
on top of it.
Does this answer your question?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-08-03 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 18:47 concurrent access to gpiolib on mxc Gilles Chanteperdrix
2010-08-03 19:36 ` Uwe Kleine-König [this message]
2010-08-04 5:55 ` Gilles Chanteperdrix
2010-08-03 20:19 ` Fabio Estevam
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=20100803193611.GA18431@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@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).