b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: John W. Linville <linville@tuxdriver.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: zajec5@gmail.com, b43-dev@lists.infradead.org,
	linux-wireless@vger.kernel.org, arend@broadcom.com
Subject: [PATCH 0/4] bcma: add PCI functions from brcmsmac
Date: Tue, 15 May 2012 17:15:26 -0400	[thread overview]
Message-ID: <20120515211526.GG24572@tuxdriver.com> (raw)
In-Reply-To: <4FAAED03.4090008@hauke-m.de>

On Thu, May 10, 2012 at 12:17:39AM +0200, Hauke Mehrtens wrote:
> 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.
> > 
> > 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.
> > 
> > Hauke Mehrtens (4):
> >   bcma: implement setting core clock mode to dynamic
> >   bcma: add bcma_core_pci_extend_L1timer
> >   bcma: add bcma_core_pci_fixcfg()
> >   bcma: add bcma_core_pci_config_fixup()
> > 
> >  drivers/bcma/core.c                  |    2 +-
> >  drivers/bcma/driver_pci.c            |   53 ++++++++++++++++++++++++++++++++--
> >  include/linux/bcma/bcma_driver_pci.h |   11 +++++++
> >  3 files changed, 63 insertions(+), 3 deletions(-)
> > 
> 
> Hi Rafa?,
> 
> could you give me an ack or a nack about this patch series and the other
> (ssb/bcma/bcm47xx: extend boardinfo and sprom).
> 
> I have tested them with b43 and brcmsmac on bcma and ssb based SoCs
> (bcm4718 + bcm43224, bcm4705 + 2x bcm4322, bcm4704 + bcm4318)  and have
> not found any problems.
> 
> Hauke

Rafa?, ping?

-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2012-05-15 21:15 UTC|newest]

Thread overview: 8+ 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 ` [PATCH 0/4] bcma: add PCI functions from brcmsmac Arend van Spriel
2012-05-09 22:17 ` Hauke Mehrtens
2012-05-15 21:15   ` John W. Linville [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=20120515211526.GG24572@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=arend@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --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 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).