[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CCDE4EB.7060001@arndnet.de>
Date: Sun, 31 Oct 2010 22:51:39 +0100
From: Arnd Hannemann <arnd@...dnet.de>
To: Ohad Ben-Cohen <ohad@...ery.com>
CC: "linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
linux-kernel@...r.kernel.org
Subject: Re: regression: b43-sdio: probe of mmc0:0001:1 failed with error
-16
Hi Ohad,
Am 31.10.2010 20:14, schrieb Ohad Ben-Cohen:
> On Sun, Oct 31, 2010 at 7:16 PM, Arnd Hannemann <arnd@...dnet.de> wrote:
>> b43-sdio: probe of mmc0:0001:1 failed with error -16
>
> It's exactly what Daniel is experiencing with the XO-1.5.
>
> In Daniel's scenario, mmc_sdio_init_card() fails because
> mmc_send_relative_addr() returns -110.
>
> Can you please check out if that's the same thing you have too ?
No, it seems to be the pm_runtime_get_sync in sdio_bus.c::sdio_bus_probe().
If I test with CONFIG_PM_RUNTIME=y and the attached modifications,
then I get this as output:
root@...evb:~# modprobe b43
[ 29.859375] cfg80211: Calling CRDA to update world regulatory domain
[ 30.226562] pm_runtime_get_sync: -16
[ 30.234375] b43-sdio: probe of mmc0:0001:1 failed with error -16
[ 30.242187] Broadcom 43xx driver loaded [ Features: LS, Firmware-ID: FW13 ]
If CONFIG_PM_RUNTIME is not set in .config, the problem goes away.
Regards,
Arnd
View attachment "diff" of type "text/plain" (997 bytes)
Powered by blists - more mailing lists