| commit | c27bdc84d6310914cfdd59280c2e663588392d01 | |
| author | Johannes Berg <johannes.berg@intel.com> | |
| Fri, 25 Nov 2011 19:11:43 +0000 (25 11:11 -0800) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Mon, 28 Nov 2011 19:44:25 +0000 (28 14:44 -0500) | ||
| tree | 4a78bf8e3709c1596f413f8a84f6fa8c126e7bea | treesnapshot (tar.gz zip) |
| parent | aed666e5e88a27f600187f960d306a028f4883ea | commitdiff |
iwlagn: remove calibration knowledge
The init microcode knows very well which calibrations
are required and sends us results for those that are.
Consequently, we can just send all of those to the RT
uCode again.
The problem with having the driver know about this is
that it is a uCode feature, not a hardware feature so
the config is completely unsuitable.
The only thing we need to check is whether the device
needs crystal calibration or not, add a new parameter
to the configuration for that.
This makes new uCode work on 6000 series devices.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
The init microcode knows very well which calibrations
are required and sends us results for those that are.
Consequently, we can just send all of those to the RT
uCode again.
The problem with having the driver know about this is
that it is a uCode feature, not a hardware feature so
the config is completely unsuitable.
The only thing we need to check is whether the device
needs crystal calibration or not, add a new parameter
to the configuration for that.
This makes new uCode work on 6000 series devices.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>