Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1380457 > unrolled thread

Re: [PATCH 1/2] clk: imx: do not sleep if IRQ's are still disabled

Started byStephen Boyd <sboyd@codeaurora.org>
First post2016-04-16 03:10 +0200
Last post2016-04-18 04:00 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 1/2] clk: imx: do not sleep if IRQ's are still disabled Stephen Boyd <sboyd@codeaurora.org> - 2016-04-16 03:10 +0200
    Re: [PATCH 1/2] clk: imx: do not sleep if IRQ's are still disabled Shawn Guo <shawnguo@kernel.org> - 2016-04-18 04:00 +0200

#1380457 — Re: [PATCH 1/2] clk: imx: do not sleep if IRQ's are still disabled

FromStephen Boyd <sboyd@codeaurora.org>
Date2016-04-16 03:10 +0200
SubjectRe: [PATCH 1/2] clk: imx: do not sleep if IRQ's are still disabled
Message-ID<romUi-3Jk-1@gated-at.bofh.it>
On 01/29, Stefan Agner wrote:
> If a clock gets enabled early during boot time, it can lead to a PLL
> startup. The wait_lock function makes sure that the PLL is really
> stareted up before it gets used. However, the function sleeps which
> leads to scheduling and an error:
> bad: scheduling from the idle thread!
> ...
> 
> Use udelay in case IRQ's are still disabled.
> 
> Signed-off-by: Stefan Agner <stefan@agner.ch>

This is really old. Shawn, are you picking these up? I'm removing
these from my queue for now.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

[toc] | [next] | [standalone]


#1380891

FromShawn Guo <shawnguo@kernel.org>
Date2016-04-18 04:00 +0200
Message-ID<rp6DM-5xU-3@gated-at.bofh.it>
In reply to#1380457
On Fri, Apr 15, 2016 at 06:00:53PM -0700, Stephen Boyd wrote:
> On 01/29, Stefan Agner wrote:
> > If a clock gets enabled early during boot time, it can lead to a PLL
> > startup. The wait_lock function makes sure that the PLL is really
> > stareted up before it gets used. However, the function sleeps which
> > leads to scheduling and an error:
> > bad: scheduling from the idle thread!
> > ...
> > 
> > Use udelay in case IRQ's are still disabled.
> > 
> > Signed-off-by: Stefan Agner <stefan@agner.ch>
> 
> This is really old. Shawn, are you picking these up? I'm removing
> these from my queue for now.

Yes, I'm picking them up.

Shawn

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web