From: Roger Quadros <rogerq@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: sameo@linux.intel.com, balbi@ti.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-omap@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] mfd: omap-usb-tll: Don't hold lock during pm_runtime_get/put_sync()
Date: Wed, 8 Jan 2014 11:58:55 +0530 [thread overview]
Message-ID: <52CCF027.6040607@ti.com> (raw)
In-Reply-To: <20131218103641.GD14274@lee--X1>
Hi,
On 12/18/2013 04:06 PM, Lee Jones wrote:
>> pm_runtime_get/put_sync() can sleep so don't hold spinlock while
>> calling them.
>>
>> This patch prevents a BUG() when CONFIG_DEBUG_ATOMIC_SLEEP is enabled.
>> Bug is present in Kernel versions v3.9 onwards.
>>
>> Reported-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>> Tested-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>> Cc: <stable@vger.kernel.org> # 3.9+
>> ---
>> drivers/mfd/omap-usb-tll.c | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/mfd/omap-usb-tll.c b/drivers/mfd/omap-usb-tll.c
>> index 0d946ae1..248004c 100644
>> --- a/drivers/mfd/omap-usb-tll.c
>> +++ b/drivers/mfd/omap-usb-tll.c
>> @@ -346,7 +346,9 @@ int omap_tll_init(struct usbhs_omap_platform_data *pdata)
>> for (i = 0; i < tll->nch; i++)
>> needs_tll |= omap_usb_mode_needs_tll(pdata->port_mode[i]);
>>
>> + spin_unlock(&tll_lock);
>> pm_runtime_get_sync(tll_dev);
>> + spin_lock(&tll_lock);
>
> This is pretty ugly. Can't you move it above the spin_lock() instead?
OK. I'll also remove NULL check for tll_dev outside the spin_lock().
>
> <snip>
>
>> tll = dev_get_drvdata(tll_dev);
>>
>> + spin_unlock(&tll_lock);
>> pm_runtime_get_sync(tll_dev);
>> + spin_lock(&tll_lock);
>
> Same here?
Yes.
>
>> for (i = 0; i < tll->nch; i++) {
>> if (omap_usb_mode_needs_tll(pdata->port_mode[i])) {
>> @@ -438,7 +441,6 @@ int omap_tll_enable(struct usbhs_omap_platform_data *pdata)
>> }
>>
>> spin_unlock(&tll_lock);
>> -
>
> This doesn't belong in this patch and is now inconsistent with the
> other functions in the driver.
OK.
>
>> return 0;
>> }
>> EXPORT_SYMBOL_GPL(omap_tll_enable);
>> @@ -464,9 +466,8 @@ int omap_tll_disable(struct usbhs_omap_platform_data *pdata)
>> }
>> }
>>
>> - pm_runtime_put_sync(tll_dev);
>> -
>> spin_unlock(&tll_lock);
>> + pm_runtime_put_sync(tll_dev);
>>
>> return 0;
>> }
>
cheers,
-roger
WARNING: multiple messages have this Message-ID (diff)
From: Roger Quadros <rogerq@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: <sameo@linux.intel.com>, <balbi@ti.com>,
<linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH] mfd: omap-usb-tll: Don't hold lock during pm_runtime_get/put_sync()
Date: Wed, 8 Jan 2014 11:58:55 +0530 [thread overview]
Message-ID: <52CCF027.6040607@ti.com> (raw)
In-Reply-To: <20131218103641.GD14274@lee--X1>
Hi,
On 12/18/2013 04:06 PM, Lee Jones wrote:
>> pm_runtime_get/put_sync() can sleep so don't hold spinlock while
>> calling them.
>>
>> This patch prevents a BUG() when CONFIG_DEBUG_ATOMIC_SLEEP is enabled.
>> Bug is present in Kernel versions v3.9 onwards.
>>
>> Reported-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>> Tested-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>> Cc: <stable@vger.kernel.org> # 3.9+
>> ---
>> drivers/mfd/omap-usb-tll.c | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/mfd/omap-usb-tll.c b/drivers/mfd/omap-usb-tll.c
>> index 0d946ae1..248004c 100644
>> --- a/drivers/mfd/omap-usb-tll.c
>> +++ b/drivers/mfd/omap-usb-tll.c
>> @@ -346,7 +346,9 @@ int omap_tll_init(struct usbhs_omap_platform_data *pdata)
>> for (i = 0; i < tll->nch; i++)
>> needs_tll |= omap_usb_mode_needs_tll(pdata->port_mode[i]);
>>
>> + spin_unlock(&tll_lock);
>> pm_runtime_get_sync(tll_dev);
>> + spin_lock(&tll_lock);
>
> This is pretty ugly. Can't you move it above the spin_lock() instead?
OK. I'll also remove NULL check for tll_dev outside the spin_lock().
>
> <snip>
>
>> tll = dev_get_drvdata(tll_dev);
>>
>> + spin_unlock(&tll_lock);
>> pm_runtime_get_sync(tll_dev);
>> + spin_lock(&tll_lock);
>
> Same here?
Yes.
>
>> for (i = 0; i < tll->nch; i++) {
>> if (omap_usb_mode_needs_tll(pdata->port_mode[i])) {
>> @@ -438,7 +441,6 @@ int omap_tll_enable(struct usbhs_omap_platform_data *pdata)
>> }
>>
>> spin_unlock(&tll_lock);
>> -
>
> This doesn't belong in this patch and is now inconsistent with the
> other functions in the driver.
OK.
>
>> return 0;
>> }
>> EXPORT_SYMBOL_GPL(omap_tll_enable);
>> @@ -464,9 +466,8 @@ int omap_tll_disable(struct usbhs_omap_platform_data *pdata)
>> }
>> }
>>
>> - pm_runtime_put_sync(tll_dev);
>> -
>> spin_unlock(&tll_lock);
>> + pm_runtime_put_sync(tll_dev);
>>
>> return 0;
>> }
>
cheers,
-roger
next prev parent reply other threads:[~2014-01-08 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 10:01 [PATCH] mfd: omap-usb-tll: Don't hold lock during pm_runtime_get/put_sync() Roger Quadros
2013-12-18 10:01 ` Roger Quadros
2013-12-18 10:36 ` Lee Jones
2013-12-18 10:36 ` Lee Jones
2014-01-08 6:28 ` Roger Quadros [this message]
2014-01-08 6:28 ` Roger Quadros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52CCF027.6040607@ti.com \
--to=rogerq@ti.com \
--cc=balbi@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.