All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Fu, Zhonghui" <zhonghui.fu@linux.intel.com>,
	brudley@broadcom.com, Franky Lin <frankyl@broadcom.com>,
	meuleman@broadcom.com, linville@tuxdriver.com,
	pieterpg@broadcom.com, dekim@broadcom.com,
	mcgrof@do-not-panic.com, antonio@open-mesh.com,
	johannes.berg@intel.com, linux-wireless@vger.kernel.org,
	brcm80211-dev-list@broadcom.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] brcmfmac: prevent watchdog from interfering with scanning and connecting
Date: Mon, 4 Aug 2014 17:47:58 +0100	[thread overview]
Message-ID: <20140804164758.GF30282@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <53A311E4.301@broadcom.com>

On Thu, Jun 19, 2014 at 06:37:56PM +0200, Arend van Spriel wrote:
> On 19-06-14 18:28, Fu, Zhonghui wrote:
>> I have tried brcmfmac driver with "CONFIG_PM_RUNTIME is not set", and scanning and connecting  always succeeded. This means that CONFIG_PM_RUNTIME should not be set if we use SDIO WiFi device driven by brcmfmac driver, right?
>
> Depends which kernel you are using. In 3.16-rc1 the sdio interrupt issue  
> has been fixed so you should be fine to use CONFIG_PM_RUNTIME. Here is  
> the commit

I have to say that scanning with the 4329 device seems utterly useless,
whereas 4330 works fine.  Apart from the broadcom chip, the rest of the
hardware is identical.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

  parent reply	other threads:[~2014-08-04 16:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16  5:49 [PATCH] brcmfmac: prevent watchdog from interfering with scanning and connecting Fu, Zhonghui
2014-06-16  5:49 ` Fu, Zhonghui
2014-06-16  8:15 ` Arend van Spriel
2014-06-16  8:15   ` Arend van Spriel
2014-06-19 16:28   ` Fu, Zhonghui
2014-06-19 16:37     ` Arend van Spriel
2014-06-19 16:37       ` Arend van Spriel
2014-07-21  7:42       ` Fu, Zhonghui
2014-07-24 15:22         ` Fu, Zhonghui
2014-08-04 16:36           ` Fu, Zhonghui
2014-08-04 16:52             ` Russell King - ARM Linux
2014-08-04 20:12               ` Arend van Spriel
2014-08-04 20:12                 ` Arend van Spriel
2014-08-05  5:42                 ` Fu, Zhonghui
2014-08-05  5:42                   ` Fu, Zhonghui
2014-08-05  5:38               ` Fu, Zhonghui
2014-08-04 17:29             ` Arend van Spriel
2014-08-04 17:29               ` Arend van Spriel
2014-08-04 16:47       ` Russell King - ARM Linux [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-11  3:52 Fu, Zhonghui

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=20140804164758.GF30282@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=antonio@open-mesh.com \
    --cc=arend@broadcom.com \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=dekim@broadcom.com \
    --cc=frankyl@broadcom.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@do-not-panic.com \
    --cc=meuleman@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pieterpg@broadcom.com \
    --cc=zhonghui.fu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.