From: Arnd Hannemann <arnd@arndnet.de>
To: Ohad Ben-Cohen <ohad@wizery.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: regression: b43-sdio: probe of mmc0:0001:1 failed with error -16
Date: Sun, 31 Oct 2010 18:35:18 +0100 [thread overview]
Message-ID: <4CCDA8D6.7030905@arndnet.de> (raw)
In-Reply-To: <4CCDA454.708@arndnet.de>
Am 31.10.2010 18:16, schrieb Arnd Hannemann:
> on todays Linus' git (v2.6.36-9871-g3985c7c) b43 sdio stopped working.
> It was working on (v2.6.36-6794-g12ba8d1).
>
> b43-sdio: probe of mmc0:0001:1 failed with error -16
>
> The error seems to originate from the following code in drivers/mmc/core/sdio_bus.c:sdio_bus_probe()
>
> 135 ret = pm_runtime_get_sync(dev);
> 136 if (ret < 0)
> 137 goto out;
>
> so I suspect this has something to do with the following commit:
>
> commit 40bba0c1ca83a370f749c8bc9afda71cf79ebd91
> Author: Ohad Ben-Cohen <ohad@wizery.com>
> Date: Sat Oct 2 13:54:11 2010 +0200
>
> mmc: sdio: enable runtime PM for SDIO functions
>
> However, simply reverting 40bba0c1ca83a370f749c8bc9afda71cf79ebd91 does not work because then
> modprobe hangs.
>
> Tested on AP4EVB (arm) with tmio_mmc. Any ideas?
FYI:
disabling CONFIG_PM_RUNTIME in my config seems to fix the issue for me.
Best regards,
Arnd
next prev parent reply other threads:[~2010-10-31 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 17:16 regression: b43-sdio: probe of mmc0:0001:1 failed with error -16 Arnd Hannemann
2010-10-31 17:25 ` Chris Ball
2010-10-31 17:35 ` Arnd Hannemann [this message]
2010-10-31 19:14 ` Ohad Ben-Cohen
2010-10-31 21:51 ` Arnd Hannemann
2010-11-01 4:50 ` Ohad Ben-Cohen
2010-11-01 8:05 ` Arnd Hannemann
2010-11-01 9:02 ` Ohad Ben-Cohen
2010-11-01 14:22 ` Arnd Hannemann
2010-11-01 14:33 ` Ohad Ben-Cohen
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=4CCDA8D6.7030905@arndnet.de \
--to=arnd@arndnet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ohad@wizery.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).