From: "Arend van Spriel" <arend@broadcom.com>
To: "Hauke Mehrtens" <hauke@hauke-m.de>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 00/19] brcmsmac: use sprom and PCIe code from bcma
Date: Thu, 3 May 2012 08:13:20 +0200 [thread overview]
Message-ID: <4FA22200.6000108@broadcom.com> (raw)
In-Reply-To: <4FA1B66A.4060901@hauke-m.de>
On 05/03/2012 12:34 AM, Hauke Mehrtens wrote:
> On 05/02/2012 08:06 AM, Arend van Spriel wrote:
>> On 04/29/2012 10:13 AM, Arend van Spriel wrote:
>>> On 04/29/2012 02:50 AM, Hauke Mehrtens wrote:
>>>> I have not completely runtime tested these patches as I do not have a
>>>> PCI(e) devices currently supported by brcmsmac. My SoC (BCM4718) and
>>>> the PCI devices connected to my SoC (BCM43224) are currently not
>>>> working with brcmsmac, but they are failing much later that without
>>>> these patches.
>>>
>>> I will test this patch series as well on PCI(e) devices. So you do have
>>> a bcm43224 card, but no laptop to fit it in? Just wondering. I will send
>>> the results.
>>>
>>> Gr. AvS
>>>
>>
>> Hi Hauke,
>>
>> I have tested this patch series including the other two series as I
>> suspect there is a dependancy so:
>>
>> [PATCH 0/8] ssb/bcma/bcm47xx: extend boardinfo and sprom
>> [PATCH 0/4] bcma: add PCI functions from brcmsmac
>
> Yes these patch series are mostly providing some stuff needed by brcmsmac.
>
>> I only did some basic testing, but wanted to let you know the results so
>> far:
>>
>> BCM43224/OTP/64-bit/2.4G: 63 Mbps
>> BCM43224/OTP/64-bit/5G: 57 Mbps
>> BCM43224/SPROM/32-bit/2.4G: 65 Mbps
>> BCM43224/SPROM/32-bit/5G: 63 Mbps
>>
>> These are pretty normal numbers. I will add the test branch to my
>> nightly regression testing for the next couple of days.
>>
>> First impression: Great job!
>
> Hi Arend,
>
> thanks for testing.
>
> Have you tried suspend/resume and hibernate/resume? I think some of the
> workaround in drivers/bcma/driver_pci.c should be called in the resume
> path and not only in the initialization path.
>
> Hauke
>
Not yet. I also want to cover the bcm4313 pcie card. I will add the
suspend resume testing to my list.
Gr. AvS
next prev parent reply other threads:[~2012-05-03 6:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 0:50 [PATCH 00/19] brcmsmac: use sprom and PCIe code from bcma Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 01/19] brcmsmac: use sprom " Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 02/19] brcmsmac: remove brcmsmac own sprom parsing Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 03/19] brcmsmac: get board and chip info from bcma Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 04/19] brcmsmac: remove support for cc rev < 20 Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 05/19] brcmsmac: remove references to PCI Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 06/19] brcmsmac: remove PCIe functions needed for PCIe core rev <= 10 Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 07/19] brcmsmac: remove pcicore_hwup() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 08/19] brcmsmac: remove ai_pci_setup() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 09/19] brcmsmac: remove ai_chipcontrl_epa4331 Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 10/19] brcmsmac: remove ai_gpiocontrol() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 11/19] brcmsmac: remove _ai_clkctl_cc() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 12/19] brcmsmac: remove pcicore_attach() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 13/19] brcmsmac: remove pcicore_find_pci_capability() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 14/19] brcmsmac: remove pcie_extendL1timer() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 15/19] brcmsmac: remove pcicore_fixcfg() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 16/19] brcmsmac: remove nicpci.c Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 17/19] brcmsmac: do not access host_pci Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 18/19] brcmsmac: read PCI vendor and device id only for PCI devices Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 19/19] brcmsmac: handle non pci in ai_deviceremoved() Hauke Mehrtens
2012-04-29 8:13 ` [PATCH 00/19] brcmsmac: use sprom and PCIe code from bcma Arend van Spriel
2012-04-29 13:21 ` Hauke Mehrtens
2012-04-29 16:45 ` Arend van Spriel
2012-04-29 22:45 ` Hauke Mehrtens
2012-05-01 9:35 ` Arend van Spriel
2012-05-01 18:21 ` Hauke Mehrtens
2012-06-02 14:21 ` Hauke Mehrtens
2012-05-02 6:06 ` Arend van Spriel
2012-05-02 22:34 ` Hauke Mehrtens
2012-05-03 6:13 ` Arend van Spriel [this message]
2012-05-03 6:18 ` Arend van Spriel
2012-05-03 11:46 ` Hauke Mehrtens
2012-05-08 12:39 ` Arend van Spriel
2012-05-09 9:00 ` Hauke Mehrtens
2012-05-09 9:26 ` Arend van Spriel
2012-05-09 22:27 ` Hauke Mehrtens
2012-05-10 12:14 ` 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=4FA22200.6000108@broadcom.com \
--to=arend@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).