Hi Steve,
On Sun, Dec 30, 2012 at 10:13:08PM +0800, steve.zhan wrote:
> Hi,
> Acked-by: Steve zhan zhanzhe...@gmail.com
>
> "I'd rather not test the spinlocks after they are registering as they
> might already be in use by then."
>
> Why? I think user must use it after hwspin_lock_reg
Hi Steve,
On Sat, Dec 29, 2012 at 05:19:08PM +0800, steve.zhan wrote:
> Hi,
>
> It is good idea add this feature.
>
> 1: Can we let the "ret = hwspin_lock_tests(ops, hwlock);" add after
> hwspin_lock_register_single have return
> succeed, that can avoid test duplicated Or error lockid. Of co
n , linux-kernel@vger.kernel.org,
> linux-arm-ker...@lists.infradead.org, linux-o...@vger.kernel.org
> Cc: Ido Yariv
> Subject: [PATCH] hwspinlock/core: Add testing capabilities
> Message-ID: <1355344026-17222-1-git-send-email-...@wizery.com>
>
> Add testing capabilities for
Add testing capabilities for verifying correctness of the underlying
hwspinlock layers. This can be handy especially during development.
These tests are performed only once as part of the hwspinlock
registration.
Signed-off-by: Ido Yariv
---
drivers/hwspinlock/Kconfig |9 +
dri
4 matches
Mail list logo