From: Arend van Spriel <arend@broadcom.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linville@tuxdriver.com, zajec5@gmail.com,
b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: [PATCH 0/4] bcma: add PCI functions from brcmsmac
Date: Sun, 29 Apr 2012 10:05:22 +0200 [thread overview]
Message-ID: <4F9CF642.1000705@broadcom.com> (raw)
In-Reply-To: <1335658732-24351-1-git-send-email-hauke@hauke-m.de>
On 04/29/2012 02:18 AM, Hauke Mehrtens wrote:
> This patch series contains the functions regarding the PCIe core from
> brcmsmac for the supported PCIe core revisions.
>
> Some of these functions have to be called on resume after suspend, but
> I do not know which or if all have to be called. I do not have a PCIe
> based device supported by brcmsmac, so I can not test this. Could
> someone which such a device do some tests and create a patch with the
> functions, which have to be called on resume.
I do have some devices and feel it is my/our responsibility to get this
tested. I let you know the results.
> The goal of theses patches is to remove the PCIe code from brcmsmac to
> get one step ahead in making brcmsmac support non pcie based devices.
>
> This is based on wireless-testing/master.
>
Gr. AvS
WARNING: multiple messages have this Message-ID (diff)
From: "Arend van Spriel" <arend@broadcom.com>
To: "Hauke Mehrtens" <hauke@hauke-m.de>
Cc: linville@tuxdriver.com, zajec5@gmail.com,
b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/4] bcma: add PCI functions from brcmsmac
Date: Sun, 29 Apr 2012 10:05:22 +0200 [thread overview]
Message-ID: <4F9CF642.1000705@broadcom.com> (raw)
In-Reply-To: <1335658732-24351-1-git-send-email-hauke@hauke-m.de>
On 04/29/2012 02:18 AM, Hauke Mehrtens wrote:
> This patch series contains the functions regarding the PCIe core from
> brcmsmac for the supported PCIe core revisions.
>
> Some of these functions have to be called on resume after suspend, but
> I do not know which or if all have to be called. I do not have a PCIe
> based device supported by brcmsmac, so I can not test this. Could
> someone which such a device do some tests and create a patch with the
> functions, which have to be called on resume.
I do have some devices and feel it is my/our responsibility to get this
tested. I let you know the results.
> The goal of theses patches is to remove the PCIe code from brcmsmac to
> get one step ahead in making brcmsmac support non pcie based devices.
>
> This is based on wireless-testing/master.
>
Gr. AvS
next prev parent reply other threads:[~2012-04-29 8:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 0:18 [PATCH 0/4] bcma: add PCI functions from brcmsmac Hauke Mehrtens
2012-04-29 0:18 ` [PATCH 1/4] bcma: implement setting core clock mode to dynamic Hauke Mehrtens
2012-04-29 0:18 ` [PATCH 2/4] bcma: add bcma_core_pci_extend_L1timer Hauke Mehrtens
2012-04-29 0:18 ` [PATCH 3/4] bcma: add bcma_core_pci_fixcfg() Hauke Mehrtens
2012-04-29 0:18 ` [PATCH 4/4] bcma: add bcma_core_pci_config_fixup() Hauke Mehrtens
2012-04-29 8:05 ` Arend van Spriel [this message]
2012-04-29 8:05 ` [PATCH 0/4] bcma: add PCI functions from brcmsmac Arend van Spriel
2012-05-09 22:17 ` Hauke Mehrtens
2012-05-09 22:17 ` Hauke Mehrtens
2012-05-15 21:15 ` John W. Linville
2012-05-15 21:15 ` John W. Linville
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=4F9CF642.1000705@broadcom.com \
--to=arend@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=zajec5@gmail.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.