Commit d9df23e9 authored by Johannes Berg's avatar Johannes Berg Committed by John W. Linville
Browse files

iwlwifi: clarify config struct comments

It talks about treating different uCode APIs
as different pieces of hardware which really
isn't how we handle things.
Signed-off-by: default avatarJohannes Berg <>
Signed-off-by: default avatarWey-Yi Guy <>
Signed-off-by: default avatarJohn W. Linville <>
parent 0ca24daf
......@@ -307,13 +307,9 @@ struct iwl_ht_params {
* @iq_invert: I/Q inversion
* @temp_offset_v2: support v2 of temperature offset calibration
* We enable the driver to be backward compatible wrt API version. The
* driver specifies which APIs it supports (with @ucode_api_max being the
* highest and @ucode_api_min the lowest). Firmware will only be loaded if
* it has a supported API version.
* The ideal usage of this infrastructure is to treat a new ucode API
* release as a new hardware revision.
* We enable the driver to be backward compatible wrt. hardware features.
* API differences in uCode shouldn't be handled here but through TLVs
* and/or the uCode API version instead.
struct iwl_cfg {
/* params specific to an individual device within a device family */
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment