2013-06-13 00:52:10 +07:00
|
|
|
config ATH10K
|
|
|
|
|
tristate "Atheros 802.11ac wireless cards support"
|
2013-07-11 04:03:36 +07:00
|
|
|
depends on MAC80211 && HAS_DMA
|
2013-06-13 00:52:10 +07:00
|
|
|
select ATH_COMMON
|
2015-11-25 20:38:34 +07:00
|
|
|
select CRC32
|
2013-06-13 00:52:10 +07:00
|
|
|
---help---
|
|
|
|
|
This module adds support for wireless adapters based on
|
|
|
|
|
Atheros IEEE 802.11ac family of chipsets.
|
|
|
|
|
|
|
|
|
|
If you choose to build a module, it'll be called ath10k.
|
|
|
|
|
|
|
|
|
|
config ATH10K_PCI
|
|
|
|
|
tristate "Atheros ath10k PCI support"
|
|
|
|
|
depends on ATH10K && PCI
|
|
|
|
|
---help---
|
|
|
|
|
This module adds support for PCIE bus
|
|
|
|
|
|
ath10k: add basic skeleton to support ahb
qca4019 uses ahb instead of pci where it slightly differs in device
enumeration, clock control, reset control, etc. Good thing is that
ahb also uses copy engine for the data transaction. So, the most of
the stuff implemented in pci.c/ce.c are reusable in ahb case too.
Device enumeration in ahb case comes through platform driver/device
model. All resource details like irq, memory map, clocks, etc for
qca4019 can be fetched from of_node of platform device.
Simply flow would look like,
device tree => platform device (kernel) => platform driver (ath10k)
Device tree entry will have all qca4019 resource details and the same
info will be passed to kernel. Kernel will prepare new platform device
for that entry and expose DT info to of_node in platform device.
Later, ath10k would register platform driver with unique compatible name
and then kernels binds to corresponding compatible entry & calls ath10k
ahb probe functions. From there onwards, ath10k will take control of it
and move forward.
New bool flag CONFIG_ATH10K_AHB is added in Kconfig to conditionally
enable ahb support in ath10k. On enabling this flag, ath10k_pci.ko
will have ahb support. This patch adds only basic skeleton and few
macros to support ahb in the context of qca4019.
Signed-off-by: Raja Mani <rmani@qti.qualcomm.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
2016-01-27 16:54:25 +07:00
|
|
|
config ATH10K_AHB
|
|
|
|
|
bool "Atheros ath10k AHB support"
|
2016-01-27 16:54:29 +07:00
|
|
|
depends on ATH10K_PCI && OF && RESET_CONTROLLER
|
ath10k: add basic skeleton to support ahb
qca4019 uses ahb instead of pci where it slightly differs in device
enumeration, clock control, reset control, etc. Good thing is that
ahb also uses copy engine for the data transaction. So, the most of
the stuff implemented in pci.c/ce.c are reusable in ahb case too.
Device enumeration in ahb case comes through platform driver/device
model. All resource details like irq, memory map, clocks, etc for
qca4019 can be fetched from of_node of platform device.
Simply flow would look like,
device tree => platform device (kernel) => platform driver (ath10k)
Device tree entry will have all qca4019 resource details and the same
info will be passed to kernel. Kernel will prepare new platform device
for that entry and expose DT info to of_node in platform device.
Later, ath10k would register platform driver with unique compatible name
and then kernels binds to corresponding compatible entry & calls ath10k
ahb probe functions. From there onwards, ath10k will take control of it
and move forward.
New bool flag CONFIG_ATH10K_AHB is added in Kconfig to conditionally
enable ahb support in ath10k. On enabling this flag, ath10k_pci.ko
will have ahb support. This patch adds only basic skeleton and few
macros to support ahb in the context of qca4019.
Signed-off-by: Raja Mani <rmani@qti.qualcomm.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
2016-01-27 16:54:25 +07:00
|
|
|
---help---
|
|
|
|
|
This module adds support for AHB bus
|
|
|
|
|
|
2013-06-13 00:52:10 +07:00
|
|
|
config ATH10K_DEBUG
|
|
|
|
|
bool "Atheros ath10k debugging"
|
|
|
|
|
depends on ATH10K
|
|
|
|
|
---help---
|
|
|
|
|
Enables debug support
|
|
|
|
|
|
|
|
|
|
If unsure, say Y to make it easier to debug problems.
|
|
|
|
|
|
|
|
|
|
config ATH10K_DEBUGFS
|
|
|
|
|
bool "Atheros ath10k debugfs support"
|
2014-09-04 19:51:09 +07:00
|
|
|
depends on ATH10K && DEBUG_FS
|
2014-08-02 13:12:54 +07:00
|
|
|
select RELAY
|
2013-06-13 00:52:10 +07:00
|
|
|
---help---
|
|
|
|
|
Enabled debugfs support
|
|
|
|
|
|
|
|
|
|
If unsure, say Y to make it easier to debug problems.
|
|
|
|
|
|
|
|
|
|
config ATH10K_TRACING
|
|
|
|
|
bool "Atheros ath10k tracing support"
|
|
|
|
|
depends on ATH10K
|
|
|
|
|
depends on EVENT_TRACING
|
|
|
|
|
---help---
|
|
|
|
|
Select this to ath10k use tracing infrastructure.
|
|
|
|
|
|
2013-12-23 13:38:27 +07:00
|
|
|
config ATH10K_DFS_CERTIFIED
|
|
|
|
|
bool "Atheros DFS support for certified platforms"
|
|
|
|
|
depends on ATH10K && CFG80211_CERTIFICATION_ONUS
|
|
|
|
|
default n
|
|
|
|
|
---help---
|
|
|
|
|
This option enables DFS support for initiating radiation on
|
|
|
|
|
ath10k.
|