Lines Matching +full:system +full:- +full:bus
1 /* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
3 * Copyright (C) 2005-2014, 2020-2021, 2023 Intel Corporation
4 * Copyright (C) 2013-2014 Intel Mobile Communications GmbH
15 #define NVM_RF_CFG_DASH_MSK(x) (x & 0x3) /* bits 0-1 */
16 #define NVM_RF_CFG_STEP_MSK(x) ((x >> 2) & 0x3) /* bits 2-3 */
17 #define NVM_RF_CFG_TYPE_MSK(x) ((x >> 4) & 0x3) /* bits 4-5 */
18 #define NVM_RF_CFG_PNUM_MSK(x) ((x >> 6) & 0x3) /* bits 6-7 */
19 #define NVM_RF_CFG_TX_ANT_MSK(x) ((x >> 8) & 0xF) /* bits 8-11 */
20 #define NVM_RF_CFG_RX_ANT_MSK(x) ((x >> 12) & 0xF) /* bits 12-15 */
30 * DOC: Driver system flows - drv component
32 * This component implements the system flows such as bus enumeration, bus
33 * removal. Bus dependent parts of system flows (such as iwl_pci_probe) are in
34 * bus specific files (transport files). This is the code that is common among
43 * 1) The bus specific component is called from module_init
44 * 2) The bus specific component registers the bus driver
45 * 3) The bus driver calls the probe function
46 * 4) The bus specific component configures the bus
47 * 5) The bus specific component calls to the drv bus agnostic part
58 * iwl_drv_start - start the drv
62 * starts the driver: fetches the firmware. This should be called by bus
63 * specific system flows implementations. For example, the bus specific probe
64 * function should do bus related operations only, and then call to this
70 * iwl_drv_stop - stop the drv
74 * Stop the driver. This should be called by bus specific system flows
75 * implementations. For example, the bus specific remove function should first
76 * call this function and then do the bus related operations only.
84 * must be exported for the sub-modules. However, if it's not split and
85 * everything is built-in, then we can avoid that.