[PATCH 3/3] omap: add hwspinlock device

Ohad Ben-Cohen ohad at wizery.com
Thu Oct 21 05:06:39 EDT 2010

On Thu, Oct 21, 2010 at 10:36 AM, Kamoolkar, Mugdha <mugdha at ti.com> wrote:
>> <khilman at deeprootsystems.com> wrote:
>> > Yes, that would indeed simplify things.
>> Balaji, Nishant, are you OK with this ?
> The problem with this approach is that the i2c driver would have to
> sync up on the shared memory location that it uses to share the
> information of the spinlock ID.

I agree.

But we seem to have this sort of problem anyway:

Since we are forbidden to take a hwspinlock over a lengthy period of
time, i2c-omap can't really use it directly to achieve mutual
exclusion over the entire i2c transfer (which is long and involved

It was suggested that i2c-omap would only use the hwspinlock to
protect a shared memory entry which would indicate the owner of the
i2c bus. Either that, or use something like Peterson's mutual
exclusion algorithm which is entirely implemented in software.

Both of the latter approaches involves sync'ing up on a shared memory
location..  so it seems like i2c-omap anyway has to deal with this
kind of pain, and having a predefined hwspinlock id number doesn't
relieve it.

What do you think ?


More information about the linux-arm-kernel mailing list