Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 160
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 22 9月, 2011 6 次提交
    • O
      hwspinlock/core: remove stubs for register/unregister · c536abfd
      由 Ohad Ben-Cohen 提交于 
      hwspinlock drivers must anyway select CONFIG_HWSPINLOCK,
so there's no point in having register/unregister stubs.

Removing those stubs will only make it easier for developers
to catch CONFIG_HWSPINLOCK mis-.config-urations.
Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
      c536abfd
    • J
      hwspinlock/core: use a mutex to protect the radix tree · 93b465c2
      由 Juan Gutierrez 提交于 
      Since we're using non-atomic radix tree allocations, we
should be protecting the tree using a mutex and not a
spinlock.

Non-atomic allocations and process context locking is good enough,
as the tree is manipulated only when locks are registered/
unregistered/requested/freed.

The locks themselves are still protected by spinlocks of course,
and mutexes are not involved in the locking/unlocking paths.

Cc: <stable@kernel.org>
Signed-off-by: NJuan Gutierrez <jgutierrez@ti.com>
[ohad@wizery.com: rewrite the commit log, #include mutex.h, add minor
commentary]
[ohad@wizery.com: update register/unregister parts in hwspinlock.txt]
Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
      93b465c2
    • O
      hwspinlock/core/omap: fix id issues on multiple hwspinlock devices · c3c1250e
      由 Ohad Ben-Cohen 提交于 
      hwspinlock devices provide system-wide hardware locks that are used
by remote processors that have no other way to achieve synchronization.

To achieve that, each physical lock must have a system-wide id number
that is agreed upon, otherwise remote processors can't possibly assume
they're using the same hardware lock.

Usually boards have a single hwspinlock device, which provides several
hwspinlocks, and in this case, they can be trivially numbered 0 to
(num-of-locks - 1).

In case boards have several hwspinlocks devices, a different base id
should be used for each hwspinlock device (they can't all use 0 as
a starting id!).

While this is certainly not common, it's just plain wrong to just
silently use 0 as a base id whenever the hwspinlock driver is probed.

This patch provides a hwspinlock_pdata structure, that boards can use
to set a different base id for each of the hwspinlock devices they may
have, and demonstrates how to use it with the omap hwspinlock driver.

While we're at it, make sure the hwspinlock core prints an explicit
error message in case an hwspinlock is registered with an id number
that already exists; this will help users catch such base id issues.
Reported-by: NArnd Bergmann <arnd@arndb.de>
Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
Acked-by: NTony Lindgren <tony@atomide.com>
      c3c1250e
    • O
      hwspinlock/omap: simplify allocation scheme · c97f6dd0
      由 Ohad Ben-Cohen 提交于 
      Instead of allocating every hwspinlock separately, allocate
them all in one shot.

This both simplifies the driver and helps achieving better
slab utilization.
Reported-by: NArnd Bergmann <arnd@arndb.de>
Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
      c97f6dd0
    • O
      hwspinlock/core: simplify 'owner' handling · e467b642
      由 Ohad Ben-Cohen 提交于 
      Use struct device_driver's owner member instead of asking drivers to
explicitly pass the owner again.

This simplifies drivers and also save some memory, since there's no
point now in maintaining a separate owner pointer per hwspinlock.
Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
      e467b642
    • O
      hwspinlock/core: simplify Kconfig · 315d8f5c
      由 Ohad Ben-Cohen 提交于 
      Simplify hwspinlock's Kconfig by making the global CONFIG_HWSPINLOCK
entry invisible; users will just select it when needed.

This also prepares the ground for adding hwspinlock support for other
platforms (the 'depends on ARCH_OMAP4' was rather hideous, and while
we're at it, a dedicated menu is added).
Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
      315d8f5c
  3. 13 9月, 2011 8 次提交
  5. 12 9月, 2011 3 次提交
  7. 11 9月, 2011 23 次提交