-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Paul Walmsley
Sent: Thursday, June 24, 2010 10:39 AM
To: Kevin Hilman
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 06/13] OMAP: hwmod: add non-locking versions
Paul Walmsley p...@pwsan.com writes:
Hi Kevin
On Wed, 23 Jun 2010, Kevin Hilman wrote:
Some hwmods may need to be idled/enabled in atomic context, so
non-locking versions of these functions are required.
Most users should not need these and usage of theses should be
controlled to
Basak, Partha p-bas...@ti.com writes:
[...]
/**
* omap_hwmod_idle - idle an omap_hwmod
* @oh: struct omap_hwmod *
@@ -1319,9 +1345,7 @@ int omap_hwmod_idle(struct omap_hwmod *oh)
if (!oh)
return -EINVAL;
- mutex_lock(omap_hwmod_mutex);
- _idle(oh);
-
Some hwmods may need to be idled/enabled in atomic context, so
non-locking versions of these functions are required.
Most users should not need these and usage of theses should be
controlled to understand why access is being done in atomic context.
For this reason, the non-locking functions are
Hi Kevin
On Wed, 23 Jun 2010, Kevin Hilman wrote:
Some hwmods may need to be idled/enabled in atomic context, so
non-locking versions of these functions are required.
Most users should not need these and usage of theses should be
controlled to understand why access is being done in atomic
