diff options
author | Rafał Miłecki <zajec5@gmail.com> | 2015-10-15 07:23:25 +0200 |
---|---|---|
committer | Kalle Valo <kvalo@codeaurora.org> | 2015-10-28 21:04:04 +0200 |
commit | 399500da18f7fe79699c0e4f603f8874cecb3898 (patch) | |
tree | 0c42ef4110c225788c1a5e9b4bbb670f736eca09 /scripts/Makefile.asm-generic | |
parent | 0117e78aec73f1c0869e50d11a255b28aa4db8f0 (diff) | |
download | linux-stable-399500da18f7fe79699c0e4f603f8874cecb3898.tar.gz linux-stable-399500da18f7fe79699c0e4f603f8874cecb3898.tar.bz2 linux-stable-399500da18f7fe79699c0e4f603f8874cecb3898.zip |
ssb: pick PCMCIA host code support from b43 driver
ssb bus can be found on various "host" devices like PCI/PCMCIA/SDIO.
Every ssb bus contains cores AKA devices.
The main idea is to have ssb driver scan/initialize bus and register
ready-to-use cores. This way ssb drivers can operate on a single core
mostly ignoring underlaying details.
For some reason PCMCIA support was split between ssb and b43. We got
PCMCIA host device probing in b43, then bus scanning in ssb and then
wireless core probing back in b43. The truth is it's very unlikely we
will ever see PCMCIA ssb device with no 802.11 core but I still don't
see any advantage of the current architecture.
With proposed change we get the same functionality with a simpler
architecture, less Kconfig symbols, one killed EXPORT and hopefully
cleaner b43. Since b43 supports both: ssb & bcma I prefer to keep ssb
specific code in ssb driver.
This mostly moves code from b43's pcmcia.c to bridge_pcmcia_80211.c. We
already use similar solution with b43_pci_bridge.c. I didn't use "b43"
in name of this new file as in theory any driver can operate on wireless
core.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'scripts/Makefile.asm-generic')
0 files changed, 0 insertions, 0 deletions