[lkml]   [2010]   [Oct]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/3] Add OMAP hardware spinlock misc driver
On Tue, Oct 19, 2010 at 04:31:30PM -0700, Daniel Walker wrote:
> On Mon, 2010-10-18 at 09:44 +0200, Ohad Ben-Cohen wrote:
> > OMAP4 introduces a Spinlock hardware module, 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 module 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 a new misc driver for this OMAP hwspinlock module.
> Does this code interface with some hardware unit (other than the other
> processors) to accomplish this locking ?
> The reason I ask is because MSM has similar code, and from what I can
> tell the MSM version has some structures in memory but that's all. It
> just operates on the structures in memory.
> It might be worth looking over the two implementation so we aren't both
> remaking the wheel.

Ohad's message to which you replied had:

Cc: Ohad Ben-Cohen <>, Hari Kanigeri <>,
Benoit Cousson <>, Tony Lindgren <>,
Greg KH <>, Grant Likely <>,, Suman Anna <>

Yours has:

To: Ohad Ben-Cohen <>
Cc: Hari Kanigeri <>, Benoit Cousson <>,
Tony Lindgren <>, Greg KH <>,,
Grant Likely <>,,, Suman Anna <>,

which includes an invalid address "mattw@codeaurora.orgmattw". Is there
a reason why you're excluding the linux-omap list from your message and
subsequent discussion?

 \ /
  Last update: 2010-10-20 11:57    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean