[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTin1fd=Kei7Fo6G+uR+270HdTkc71fvsA6qjBjcA@mail.gmail.com>
Date: Tue, 14 Dec 2010 16:31:36 +0200
From: Ohad Ben-Cohen <ohad@...ery.com>
To: linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Cc: akpm@...ux-foundation.org, Greg KH <greg@...ah.com>,
Tony Lindgren <tony@...mide.com>,
Benoit Cousson <b-cousson@...com>,
Grant Likely <grant.likely@...retlab.ca>,
Hari Kanigeri <h-kanigeri2@...com>, Suman Anna <s-anna@...com>,
Kevin Hilman <khilman@...prootsystems.com>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v3 0/4] Introduce hardware spinlock framework
Hi Greg, Tony,
On Sat, Dec 4, 2010 at 1:50 AM, Ohad Ben-Cohen <ohad@...ery.com> wrote:
> OMAP4 introduces a Hardware Spinlock device, which provides hardware
> assistance for synchronization and mutual exclusion between heterogeneous
> processors and those not operating under a single, shared operating system
> (e.g. OMAP4 has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP).
>
> The intention of this hardware device is to allow remote processors,
> that have no alternative mechanism to accomplish synchronization and mutual
> exclusion operations, to share resources (such as memory and/or any other
> hardware resource).
>
> This patchset adds hwspinlock framework that makes it possible
> for drivers to use those hwspinlock devices and stay platform-independent.
...
> Documentation/hwspinlock.txt | 299 +++++++++++++++
> arch/arm/mach-omap2/Makefile | 1 +
> arch/arm/mach-omap2/hwspinlock.c | 63 ++++
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 64 ++++
> drivers/Kconfig | 2 +
> drivers/Makefile | 1 +
> drivers/hwspinlock/Kconfig | 22 ++
> drivers/hwspinlock/Makefile | 6 +
> drivers/hwspinlock/hwspinlock.h | 61 +++
> drivers/hwspinlock/hwspinlock_core.c | 557 ++++++++++++++++++++++++++++
> drivers/hwspinlock/omap_hwspinlock.c | 231 ++++++++++++
> include/linux/hwspinlock.h | 298 +++++++++++++++
> 12 files changed, 1605 insertions(+), 0 deletions(-)
Can you please have a look and say if this looks OK ?
If it does, where would you prefer this to go through ?
Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists