From: chris@printf•net (Chris Ball)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH V2 2/2] mmc: sdhci-esdhc-imx: fix warning during module remove function
Date: Mon, 13 Jan 2014 18:40:09 +0000 [thread overview]
Message-ID: <8638krbu9i.fsf@void.printf.net> (raw)
In-Reply-To: <1388042634-17281-2-git-send-email-b29396@freescale.com> (Dong Aisheng's message of "Thu, 26 Dec 2013 15:23:54 +0800")
Hi,
On Thu, Dec 26 2013, Dong Aisheng wrote:
> Since the clock is managed by runtime pm currently, we do not need
> disable it again during driver remove function, or it will cause
> clock disable count mismatch issue since the clocks have already been disabled.
>
> The issue can be simply reproduced by unbind the devices via sysfs.
> mx6slevk:/sys/bus/platform/drivers/sdhci-esdhc-imx# echo 2194000.usdhc > unbind
> mmc1: card aaaa removed
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 657 at drivers/clk/clk.c:842 __clk_disable+0x68/0x88()
Thanks, pushed to mmc-next.
- Chris.
--
Chris Ball <chris@printf•net> <http://printf.net/>
next prev parent reply other threads:[~2014-01-13 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 7:23 [PATCH V2 1/2] mmc: sdhci-esdhc-imx: fix access hardirq-unsafe lock in atomic context Dong Aisheng
2013-12-26 7:23 ` [PATCH V2 2/2] mmc: sdhci-esdhc-imx: fix warning during module remove function Dong Aisheng
2014-01-13 18:40 ` Chris Ball [this message]
2013-12-31 5:24 ` [PATCH V2 1/2] mmc: sdhci-esdhc-imx: fix access hardirq-unsafe lock in atomic context Shawn Guo
2014-01-13 10:52 ` Dong Aisheng
2014-01-13 18:41 ` Chris Ball
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=8638krbu9i.fsf@void.printf.net \
--to=chris@printf$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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