[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=4hYRJheBBLJARJr_s5RbMs3APFTKD-pk1VJEy@mail.gmail.com>
Date: Tue, 19 Oct 2010 22:21:10 +0200
From: Ohad Ben-Cohen <ohad@...ery.com>
To: Kevin Hilman <khilman@...prootsystems.com>
Cc: linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, akpm@...ux-foundation.org,
Greg KH <greg@...ah.com>, Tony Lindgren <tony@...mide.com>,
Benoit Cousson <b-cousson@...com>,
Grant Likely <grant.likely@...retlab.ca>,
Hari Kanigeri <h-kanigeri2@...com>, Suman Anna <s-anna@...com>,
Simon Que <sque@...com>,
"Krishnamoorthy, Balaji T" <balajitk@...com>
Subject: Re: [PATCH 1/3] drivers: misc: add omap_hwspinlock driver
On Tue, Oct 19, 2010 at 6:58 PM, Kevin Hilman
<khilman@...prootsystems.com> wrote:
>> + * This spin_trylock_irqsave serves two purposes:
>> +
>> + * 1. Disable local interrupts and preemption, in order to
>> + * minimize the period of time in which the hwspinlock
>> + * is taken (so caller will not preempted). This is
>> + * important in order to minimize the possible polling on
>> + * the hardware interconnect by a remote user of this lock.
>> + *
>> + * 2. Make this hwspinlock primitive SMP-safe (so we can try to
>> + * take it from additional contexts on the local cpu)
>> + */
>
> 3. Ensures that in_atomic/might_sleep checks catch potential problems
> with hwspinlock usage (e.g. scheduler checks like 'scheduling while
> atomic' etc.)
Nice one. Added.
>> +/**
>> + * omap_hwspinlock_unlock() - unlock a specific hwspinlock
>
> minor nit: s/lock_unlock/_unlock/ to match name below
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists