Re: [PATCH 3/5] omap:hwspinlock-added hwspinlock driver

[Nishanth Menon <nm@ti.com>]

Kanigeri, Hari had written, on 07/19/2010 11:50 AM, the following:
> From: Simon Que <sque@ti.com>
> 
> Created driver for OMAP hardware spinlock.  This driver supports:
> - Reserved spinlocks for internal use
> - Dynamic allocation of unreserved locks
> - Lock, unlock, and trylock functions, with or without disabling irqs/preempt
> - Registered as a platform device driver
> 
> The device initialization uses hwmod to configure the devices.
> One device will be created for each IP.  It will pass spinlock register offset
> info to the driver.  The device initialization file is:
>                 arch/arm/mach-omap2/hwspinlocks.c
> 
> The driver takes in register offset info passed in device initialization.
> It uses hwmod to obtain the base address of the hardware spinlock module.
> Then it reads info from the registers.  The function hwspinlock_probe()
> initializes the array of spinlock structures, each containing a spinlock
> register address calculated from the base address and lock offsets.
> The device driver file is:
>                 arch/arm/plat-omap/hwspinlock.c

just a curious question:

Is there no h/w spinlock implementation for other architectures in 
linux? I mean the concept does not seem unique for a heterogenous 
processor environments now a days.. if it does exist, maybe we have two 
options:
* extend standard spinlock architecture to handle h/w spinlocks as well
* establish a new framework for h/w spinlocks..

[...]

-- 
Regards,
Nishanth Menon