linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 14 Nov 2014 20:30:24 +0100	[thread overview]
Message-ID: <54665850.9070007@broadcom.com> (raw)
In-Reply-To: <CAMP44s0j+i3zADu=Y3fUWqNEgDFeESs2_aFYmxQt9kZRcXkCjA@mail.gmail.com>

On 11/14/14 18:03, Felipe Contreras wrote:
> On Thu, Nov 13, 2014 at 4:47 AM, Arend van Spriel<arend@broadcom.com>  wrote:
>> 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:
>
>>> 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.
>
> I tried disabled WPA security, it's still not working.

Thanks, Felipe

Could you check the runtime-pm for mmc1 controller. You need to find 
sdhci-acpi driver in sysfs. I think it is under 
/sys/bus/platform/drivers. One of the bound devices is mmc1 (although 
probably will have different nameing there) and there is subfolder power 
with file named control. Can you cat that file and do 'echo on > 
control' if it says auto.

Regards,
Arend


      reply	other threads:[~2014-11-14 19:30 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
2014-11-14 17:03           ` Felipe Contreras
2014-11-14 19:30             ` Arend van Spriel [this message]

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=54665850.9070007@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).