From: Arend van Spriel <arend@broadcom.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-wireless Mailing List <linux-wireless@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
"brcm80211-dev-list@broadcom.com"
<brcm80211-dev-list@broadcom.com>
Subject: Re: brcmfmac not working on ECS LIVA
Date: Thu, 13 Nov 2014 11:47:44 +0100 [thread overview]
Message-ID: <54648C50.6000702@broadcom.com> (raw)
In-Reply-To: <CAMP44s1DOA31ob24=qzz83MnVFmm60EpgaPYvLbwUv-AP5FRbw@mail.gmail.com>
On 12-11-14 16:23, Felipe Contreras wrote:
> On Wed, Nov 12, 2014 at 4:40 AM, Arend van Spriel <arend@broadcom.com> wrote:
>> On 11-11-14 23:32, Felipe Contreras wrote:
>>> On Sun, Nov 9, 2014 at 4:46 AM, Arend van Spriel <arend@broadcom.com> wrote:
>>>
>>>> Could you share the nvram obtained from EFI? Also please create a kernel log
>>>> with debug=0xd416.
>>>
>>> There you go:
>>> http://people.freedesktop.org/~felipec/dmesg-brcm.txt
>>>
>>
>> It is using the sdhci-acpi driver for the sdio host controller. If I am
>> not mistaken that one does runtime-pm. This has caused issues with our
>> device. This is what happens:
>>
>> 1. driver sends control message and waits for firmware response.
>> 2. runtime pm kicks in and suspends host controller.
>> 3. host controller suspend disable sdio clock.
>> 4. host controller does not detect firmware interrupt for response.
>> 5. control message times out.
>>
>> You can disable it through sysfs, but the patch below may do it.
>
> I tried this patch, and although it seems to make a difference, it
> still doesn't work.
>
> http://people.freedesktop.org/~felipec/dmesg-brcm-2.txt
Hi Felipe,
All the messages to the firmware seem ok. If connection would succeed I
normally see a LINK event followed by SET_SSID event. In your log I only
see the SET_SSID event with failed status, hence the connect is
unsuccessful. Do you have any control over the AP? Could you try without
WPA security to quickly confirm connection works? May help in root
causing the issue.
Regards,
Arend
next prev parent reply other threads:[~2014-11-13 10:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 20:39 brcmfmac not working on ECS LIVA Felipe Contreras
2014-11-09 10:46 ` Arend van Spriel
2014-11-10 20:48 ` Felipe Contreras
2014-11-11 11:08 ` Arend van Spriel
2014-11-11 18:32 ` Felipe Contreras
2014-11-11 18:35 ` Arend van Spriel
2014-11-11 18:49 ` Felipe Contreras
2014-11-11 19:10 ` Arend van Spriel
2014-11-11 19:13 ` Felipe Contreras
2014-11-11 22:32 ` Felipe Contreras
2014-11-12 10:40 ` Arend van Spriel
2014-11-12 15:23 ` Felipe Contreras
2014-11-13 10:47 ` Arend van Spriel [this message]
2014-11-14 17:03 ` Felipe Contreras
2014-11-14 19:30 ` Arend van Spriel
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=54648C50.6000702@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=felipe.contreras@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@linux.intel.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).