From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: exynos_defconfig: Enable WiFi-Ex as a module instead built-in
Date: Wed, 30 Sep 2015 16:37:41 +0900 [thread overview]
Message-ID: <560B9145.6070606@samsung.com> (raw)
In-Reply-To: <560B8DA3.6060507@osg.samsung.com>
On 30.09.2015 16:22, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 09/30/2015 02:36 AM, Krzysztof Kozlowski wrote:
>> On 29.09.2015 21:42, Javier Martinez Canillas wrote:
>>> The Marvell WiFi-Ex driver tries to load a firmware on probe. So if the
>>> driver is built-in and probed before a firmware is available, this is
>>> not loaded and the chip does not work.
>>>
>>> This happens for example if an initramfs isn't used since the driver is
>>> probed before the root filesystem is mounted.
>>>
>>> Change the default config since the driver isn't needed for machines to
>>> boot and is more convenient to have it enabled as a module to avoid
>>> requiring an initramfs or to have the firmware built into the kernel.
>>>
>>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>>>
>>> ---
>>>
>>> arch/arm/configs/exynos_defconfig | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> The user-space can always initiate re-probing of device - just re-bind
>
> It is true that you can force a re-probing from user-space by doing:
>
> $ echo "mmc2:0001:1" > /sys/bus/sdio/drivers/mwifiex_sdio/unbind
> $ echo "mmc2:0001:1" > /sys/bus/sdio/drivers/mwifiex_sdio/bind
I suppose the unbind won't be needed, because device aborted the
probe... so only one another bind.
>
> but:
>
> a) This is not obvious. In fact, I didn't think that possibility
> before you mentioned and I've been using Linux for many years :)
Eh, questionable. Obvious for me :)
>
> b) This is not something that isn't done automatically by init systems.
Right.
>
> So what users will see is that the driver was probed successfully but
> the firmware fails to load later (since the driver users the async
> request_firmware_nowait function to request the firmware).
Okay.
>
>> it. However I assume that driver cannot work without firmware?
>>
>
> Yes, it doesn't. I explained this in the commit message. Do you
> think it should be made more clear?
No, its OK, I agree.
Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-09-30 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 12:42 [PATCH] ARM: exynos_defconfig: Enable WiFi-Ex as a module instead built-in Javier Martinez Canillas
2015-09-29 13:20 ` Andreas Färber
2015-09-29 13:57 ` Javier Martinez Canillas
2015-09-30 0:36 ` Krzysztof Kozlowski
2015-09-30 7:22 ` Javier Martinez Canillas
2015-09-30 7:37 ` Krzysztof Kozlowski [this message]
2015-09-30 7:54 ` Javier Martinez Canillas
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=560B9145.6070606@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).