From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/3] ARM: Introduce atomic MMIO modify
Date: Thu, 2 Jan 2014 11:58:36 -0300 [thread overview]
Message-ID: <20140102145835.GA6883@localhost> (raw)
In-Reply-To: <20140102144724.GF19878@titan.lakedaemon.net>
On Thu, Jan 02, 2014 at 09:47:24AM -0500, Jason Cooper wrote:
> On Thu, Jan 02, 2014 at 11:30:57AM +0000, Russell King - ARM Linux wrote:
> > On Tue, Dec 10, 2013 at 11:41:35AM -0300, Ezequiel Garcia wrote:
> > > Some SoC have MMIO regions that are shared across orthogonal
> > > subsystems. This commit implements a possible solution for the
> > > thread-safe access of such regions through a spinlock-protected API.
> > >
> > > Concurrent access is protected with a single spinlock for the
> > > entire MMIO address space. While this protects shared-registers,
> > > it also serializes access to unrelated/unshared registers.
> > >
> > > We add relaxed and non-relaxed variants, by using writel_relaxed and writel,
> > > respectively. The rationale for this is that some users may not require
> > > register write completion but only thread-safe access to a register.
> > >
> > > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> >
> > Okay, so this patch has been submitted to the patch system, but it
> > contains no other tags other than Ezequiel's sign-off. Clearly
> > other people *have* reviewed it.
> >
> > Can we please have some acks etc for it please?
>
> Acked-by: Jason Cooper <jason@lakedaemon.net>
>
Thanks!
Will: Can you ack this patch as well?
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-02 14:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 14:41 [PATCH v5 0/3] Introduce atomic MMIO register modify Ezequiel Garcia
2013-12-10 14:41 ` [PATCH v5 1/3] ARM: Introduce atomic MMIO modify Ezequiel Garcia
2013-12-10 16:49 ` Mark Brown
2013-12-10 17:00 ` Russell King - ARM Linux
2013-12-10 17:09 ` Mark Brown
2013-12-11 20:49 ` Ezequiel Garcia
2013-12-12 13:58 ` Will Deacon
2013-12-12 14:02 ` Jason Cooper
2013-12-12 14:07 ` Will Deacon
2013-12-12 14:36 ` Jason Cooper
2013-12-12 15:05 ` Ezequiel Garcia
2014-01-02 11:30 ` Russell King - ARM Linux
2014-01-02 14:47 ` Jason Cooper
2014-01-02 14:58 ` Ezequiel Garcia [this message]
2014-01-12 14:52 ` Ezequiel Garcia
2014-01-13 13:58 ` Catalin Marinas
2014-01-13 14:02 ` Russell King - ARM Linux
2014-01-13 15:28 ` Will Deacon
2014-01-15 17:15 ` Jason Cooper
2013-12-10 14:41 ` [PATCH v5 2/3] clocksource: orion: Use atomic access for shared registers Ezequiel Garcia
2013-12-12 13:53 ` Jason Cooper
2013-12-10 14:41 ` [PATCH v5 3/3] watchdog: " Ezequiel Garcia
2013-12-12 13:53 ` Jason Cooper
2013-12-12 13:52 ` [PATCH v5 0/3] Introduce atomic MMIO register modify Jason Cooper
2013-12-12 15:07 ` Ezequiel Garcia
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=20140102145835.GA6883@localhost \
--to=ezequiel.garcia@free-electrons.com \
--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).