From: Arend van Spriel <arend@broadcom.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Bernd Wagener <Bernd.Wagener@Uni-Oldenburg.DE>,
Linux Wireless <linux-wireless@vger.kernel.org>,
brcm80211-dev-list <brcm80211-dev-list@broadcom.com>
Subject: Re: brcmfmac NVRAM files
Date: Fri, 7 Mar 2014 09:26:29 +0100 [thread overview]
Message-ID: <531982B5.9040607@broadcom.com> (raw)
In-Reply-To: <20140305165049.GE14401@zurbaran>
On 03/05/2014 05:50 PM, Samuel Ortiz wrote:
> On Wed, Mar 05, 2014 at 05:15:27PM +0100, Arend van Spriel wrote:
>> On 03/05/14 11:24, Samuel Ortiz wrote:
>>> I'm attaching the log corresponding to a modprobe brcmfmac debug=0x31416
>>> && ifconfig wlan0 up sequence.
>>> I have modified this in the driver, to make it less aggressive about
>>> SDIO sleeps:
>>>
>>> sdio_host.h:
>>> #define BRCMF_WD_POLL_MS 200
>>>
>>> dhd_sdio.c:
>>> #define BRCMF_IDLE_INTERVAL 20
>>
>> So this log looks fine, because due to the changes above it never
>> goes to sleep. The log actually show it is a backport, right?
> That's correct, yes.
>
>
>>>>> I also have 2 question for you;-)
>>> Sorry if I sounded a bit rude, I didn't mean it :-/
>>
>> I did not take it as rude so no worries.
>>
>>>>> - what mmc host controller is used?
>>> So this is sdhci-acpi.
>>>
>>>>> - do you have CONFIG_RUNTIME_PM enabled?
>>> CONFIG_PM_RUNTIME is enabled, yes. Do you want me to test with it
>>> disabled ?
>>>
>>
>> I am asking because Russell King recently discovered that SDHCI
>> based host controller drivers disable the SDIO interrupt.
> You mean they do so from their runtime_suspend hook ?
> I see the thread now:
>
> http://www.spinics.net/lists/arm-kernel/msg308757.html
>
> It seems those patches have not been reviewed nor merged...
> I'll watch that thread closely ;)
>
>> This would
>> explain the timeout on the scan as the scan results are events from
>> the device that require this interrupt. Even with your patches this
>> may still happen. You can probably disable it for the host
>> controller through sysfs.
> I did so, and things seem to be more stable. The throughput is a lot
> better. Better is expected but 20x better is something else.
> I still get fairly weak signal, typically -75 dBm for APs that are a few
> meters away. Does that sound like reasonable values to you ?
Depending on the definition of a few meters and whether there is a
concrete wall in between, I tend to say -75 dBm is crap. Up to 10 meters
(without aforementioned wall) I would expect something around -40 dBm.
Regards,
Arend
prev parent reply other threads:[~2014-03-07 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 15:06 brcmfmac NVRAM files Samuel Ortiz
2014-02-17 16:33 ` Samuel Ortiz
2014-02-17 16:52 ` Bernd Wagener
2014-02-17 17:37 ` Arend van Spriel
2014-02-17 17:38 ` Arend van Spriel
2014-02-17 18:00 ` Samuel Ortiz
2014-02-17 18:27 ` Bernd Wagener
2014-02-18 9:58 ` Arend van Spriel
2014-03-05 2:31 ` Samuel Ortiz
2014-03-05 9:04 ` Arend van Spriel
2014-03-05 10:24 ` Samuel Ortiz
2014-03-05 16:15 ` Arend van Spriel
2014-03-05 16:50 ` Samuel Ortiz
2014-03-07 8:26 ` 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=531982B5.9040607@broadcom.com \
--to=arend@broadcom.com \
--cc=Bernd.Wagener@Uni-Oldenburg.DE \
--cc=brcm80211-dev-list@broadcom.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).