[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CCDA8D6.7030905@arndnet.de>
Date: Sun, 31 Oct 2010 18:35:18 +0100
From: Arnd Hannemann <arnd@...dnet.de>
To: Ohad Ben-Cohen <ohad@...ery.com>,
"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
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@...ery.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists