From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: OMAP: dmtimer: fix sleeping function called from invalid context
Date: Fri, 9 Dec 2011 13:34:47 -0800 [thread overview]
Message-ID: <20111209213447.GB31337@atomide.com> (raw)
In-Reply-To: <1322194370-8073-2-git-send-email-omar.ramirez@ti.com>
* Omar Ramirez Luna <omar.ramirez@ti.com> [111124 19:37]:
> omap_dm_timer_request* holds a spin_lock_irqsave while inner routines call
> clk_get_sys which holds a mutex_lock, given that mutex can be put to sleep
> a BUG message is triggered. This occurs in 2 ocassions.
>
> 1. When the fck is gotten at the beginning of omap_dm_timer_prepare by using
> clk_get (which will call clk_get_sys), this was fixed by getting the clock
> handles on probe.
>
> 2. When omap_dm_timer_set_source tries to get the clock handles (with clk_get)
> for the fck and source clock, this was moved to be made after
> spin_unlock_irqsave when the context is not atomic anymore.
>
> @@ -168,19 +159,26 @@ struct omap_dm_timer *omap_dm_timer_request(void)
> break;
> }
>
> - if (timer) {
> - ret = omap_dm_timer_prepare(timer);
> - if (ret) {
> - timer->reserved = 0;
> - timer = NULL;
> - }
> + if (!timer) {
> + spin_unlock_irqrestore(&dm_timer_lock, flags);
> + goto err_no_timer;
> }
> +
> + omap_dm_timer_prepare(timer);
> +
> spin_unlock_irqrestore(&dm_timer_lock, flags);
>
> - if (!timer)
> - pr_debug("%s: timer request failed!\n", __func__);
> + ret = omap_dm_timer_set_source(timer, OMAP_TIMER_SRC_32_KHZ);
> + if (ret) {
> + timer->reserved = 0;
> + goto err_no_timer;
> + }
>
> return timer;
> +
> +err_no_timer:
> + pr_debug("%s: timer request failed!\n", __func__);
> + return NULL;
> }
> EXPORT_SYMBOL_GPL(omap_dm_timer_request);
This does not seem right.. It seems that you're hardcoding the source
clock to 32 KiHz clock while other sources are available too?
> @@ -199,19 +197,26 @@ struct omap_dm_timer *omap_dm_timer_request_specific(int id)
> }
> }
>
> - if (timer) {
> - ret = omap_dm_timer_prepare(timer);
> - if (ret) {
> - timer->reserved = 0;
> - timer = NULL;
> - }
> + if (!timer) {
> + spin_unlock_irqrestore(&dm_timer_lock, flags);
> + goto err_no_timer;
> }
> +
> + omap_dm_timer_prepare(timer);
> +
> spin_unlock_irqrestore(&dm_timer_lock, flags);
>
> - if (!timer)
> - pr_debug("%s: timer%d request failed!\n", __func__, id);
> + ret = omap_dm_timer_set_source(timer, OMAP_TIMER_SRC_32_KHZ);
> + if (ret) {
> + timer->reserved = 0;
> + goto err_no_timer;
> + }
And here too?
Regards,
Tony
next prev parent reply other threads:[~2011-12-09 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 4:12 [PATCH 0/2] ARM: OMAP: dmtimer: scheduling while atomic fixes Omar Ramirez Luna
2011-11-25 4:12 ` [PATCH 1/2] ARM: OMAP: dmtimer: fix sleeping function called from invalid context Omar Ramirez Luna
2011-12-09 21:34 ` Tony Lindgren [this message]
2011-12-09 22:10 ` Ramirez Luna, Omar
2011-12-12 23:08 ` Tony Lindgren
2011-12-13 1:49 ` Ramirez Luna, Omar
2011-11-25 4:12 ` [PATCH 2/2] ARM: OMAP: dmtimer: reorganize omap_dm_timer_request_* Omar Ramirez Luna
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=20111209213447.GB31337@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).