From: Shawn Guo <shawn.guo@freescale.com>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
Thierry Reding <thierry.reding@gmail.com>,
Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
Sascha Hauer <kernel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org, linux-pwm@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: MX28: leds/pwm: Using pwm driven led as heartbeat leads to kernel warning
Date: Fri, 4 Apr 2014 22:26:58 +0800 [thread overview]
Message-ID: <20140404142656.GA16383@dragon> (raw)
In-Reply-To: <533EB9AC.6040708@i2se.com>
On Fri, Apr 04, 2014 at 03:54:52PM +0200, Stefan Wahren wrote:
> the problem is still reproducable in Mainline 3.14.0 and gives the same
> warning message.
> Also i add linux-leds in CC.
>
> Are there any advices to narrow down the problem?
>
> Is this problem specific to i.MX28 PWM (i don't have other kind of
> hardware)?
I don't think it's specific to i.MX28 PWM. Since the .config hook of
pwm_ops will be called from interrupt context in this case, any pwm
drivers that do sleeping calls in the hook will have this problem, e.g.
the clk APIs that hold mutex like clk_prepare() and clk_get_rate() etc.
Shawn
next prev parent reply other threads:[~2014-04-04 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53345C93.9040005@i2se.com>
2014-04-04 13:54 ` MX28: leds/pwm: Using pwm driven led as heartbeat leads to kernel warning Stefan Wahren
2014-04-04 14:26 ` Shawn Guo [this message]
2014-04-04 15:25 ` Stefan Wahren
2014-04-04 16:44 ` Alexandre Belloni
2014-04-08 7:34 ` Shawn Guo
2014-04-08 7:59 ` Alexandre Belloni
2014-04-08 8:18 ` Shawn Guo
2014-04-08 8:41 ` Alexandre Belloni
2014-04-08 8:49 ` Shawn Guo
2014-04-08 9:04 ` Alexandre Belloni
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=20140404142656.GA16383@dragon \
--to=shawn.guo@freescale.com \
--cc=cooloney@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=stefan.wahren@i2se.com \
--cc=thierry.reding@gmail.com \
/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).