96 lines
3.4 KiB
C
96 lines
3.4 KiB
C
/* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
|
|
/*
|
|
* Copyright (C) 2005-2014, 2020-2021 Intel Corporation
|
|
* Copyright (C) 2013-2014 Intel Mobile Communications GmbH
|
|
*/
|
|
#ifndef __iwl_drv_h__
|
|
#define __iwl_drv_h__
|
|
#include <linux/export.h>
|
|
|
|
/* for all modules */
|
|
#define DRV_NAME "iwlwifi"
|
|
|
|
/* radio config bits (actual values from NVM definition) */
|
|
#define NVM_RF_CFG_DASH_MSK(x) (x & 0x3) /* bits 0-1 */
|
|
#define NVM_RF_CFG_STEP_MSK(x) ((x >> 2) & 0x3) /* bits 2-3 */
|
|
#define NVM_RF_CFG_TYPE_MSK(x) ((x >> 4) & 0x3) /* bits 4-5 */
|
|
#define NVM_RF_CFG_PNUM_MSK(x) ((x >> 6) & 0x3) /* bits 6-7 */
|
|
#define NVM_RF_CFG_TX_ANT_MSK(x) ((x >> 8) & 0xF) /* bits 8-11 */
|
|
#define NVM_RF_CFG_RX_ANT_MSK(x) ((x >> 12) & 0xF) /* bits 12-15 */
|
|
|
|
#define EXT_NVM_RF_CFG_FLAVOR_MSK(x) ((x) & 0xF)
|
|
#define EXT_NVM_RF_CFG_DASH_MSK(x) (((x) >> 4) & 0xF)
|
|
#define EXT_NVM_RF_CFG_STEP_MSK(x) (((x) >> 8) & 0xF)
|
|
#define EXT_NVM_RF_CFG_TYPE_MSK(x) (((x) >> 12) & 0xFFF)
|
|
#define EXT_NVM_RF_CFG_TX_ANT_MSK(x) (((x) >> 24) & 0xF)
|
|
#define EXT_NVM_RF_CFG_RX_ANT_MSK(x) (((x) >> 28) & 0xF)
|
|
|
|
/**
|
|
* DOC: Driver system flows - drv component
|
|
*
|
|
* This component implements the system flows such as bus enumeration, bus
|
|
* removal. Bus dependent parts of system flows (such as iwl_pci_probe) are in
|
|
* bus specific files (transport files). This is the code that is common among
|
|
* different buses.
|
|
*
|
|
* This component is also in charge of managing the several implementations of
|
|
* the wifi flows: it will allow to have several fw API implementation. These
|
|
* different implementations will differ in the way they implement mac80211's
|
|
* handlers too.
|
|
|
|
* The init flow wrt to the drv component looks like this:
|
|
* 1) The bus specific component is called from module_init
|
|
* 2) The bus specific component registers the bus driver
|
|
* 3) The bus driver calls the probe function
|
|
* 4) The bus specific component configures the bus
|
|
* 5) The bus specific component calls to the drv bus agnostic part
|
|
* (iwl_drv_start)
|
|
* 6) iwl_drv_start fetches the fw ASYNC, iwl_req_fw_callback
|
|
* 7) iwl_req_fw_callback parses the fw file
|
|
* 8) iwl_req_fw_callback starts the wifi implementation to matches the fw
|
|
*/
|
|
|
|
struct iwl_drv;
|
|
struct iwl_trans;
|
|
struct iwl_cfg;
|
|
/**
|
|
* iwl_drv_start - start the drv
|
|
*
|
|
* @trans_ops: the ops of the transport
|
|
*
|
|
* starts the driver: fetches the firmware. This should be called by bus
|
|
* specific system flows implementations. For example, the bus specific probe
|
|
* function should do bus related operations only, and then call to this
|
|
* function. It returns the driver object or %NULL if an error occurred.
|
|
*/
|
|
struct iwl_drv *iwl_drv_start(struct iwl_trans *trans);
|
|
|
|
/**
|
|
* iwl_drv_stop - stop the drv
|
|
*
|
|
* @drv:
|
|
*
|
|
* Stop the driver. This should be called by bus specific system flows
|
|
* implementations. For example, the bus specific remove function should first
|
|
* call this function and then do the bus related operations only.
|
|
*/
|
|
void iwl_drv_stop(struct iwl_drv *drv);
|
|
|
|
/*
|
|
* exported symbol management
|
|
*
|
|
* The driver can be split into multiple modules, in which case some symbols
|
|
* must be exported for the sub-modules. However, if it's not split and
|
|
* everything is built-in, then we can avoid that.
|
|
*/
|
|
#ifdef CONFIG_IWLWIFI_OPMODE_MODULAR
|
|
#define IWL_EXPORT_SYMBOL(sym) EXPORT_SYMBOL_NS_GPL(sym, IWLWIFI)
|
|
#else
|
|
#define IWL_EXPORT_SYMBOL(sym)
|
|
#endif
|
|
|
|
/* max retry for init flow */
|
|
#define IWL_MAX_INIT_RETRY 2
|
|
|
|
#endif /* __iwl_drv_h__ */
|