1 /******************************************************************************
3 * This file is provided under a dual BSD/GPLv2 license. When using or
4 * redistributing this file, you may do so under either license.
8 * Copyright(c) 2005 - 2009 Intel Corporation. All rights reserved.
10 * This program is free software; you can redistribute it and/or modify
11 * it under the terms of version 2 of the GNU General Public License as
12 * published by the Free Software Foundation.
14 * This program is distributed in the hope that it will be useful, but
15 * WITHOUT ANY WARRANTY; without even the implied warranty of
16 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
17 * General Public License for more details.
19 * You should have received a copy of the GNU General Public License
20 * along with this program; if not, write to the Free Software
21 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110,
24 * The full GNU General Public License is included in this distribution
25 * in the file called LICENSE.GPL.
27 * Contact Information:
28 * Intel Linux Wireless <ilw@linux.intel.com>
29 * Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497
33 * Copyright(c) 2005 - 2009 Intel Corporation. All rights reserved.
34 * All rights reserved.
36 * Redistribution and use in source and binary forms, with or without
37 * modification, are permitted provided that the following conditions
40 * * Redistributions of source code must retain the above copyright
41 * notice, this list of conditions and the following disclaimer.
42 * * Redistributions in binary form must reproduce the above copyright
43 * notice, this list of conditions and the following disclaimer in
44 * the documentation and/or other materials provided with the
46 * * Neither the name Intel Corporation nor the names of its
47 * contributors may be used to endorse or promote products derived
48 * from this software without specific prior written permission.
50 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
51 * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
52 * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
53 * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
54 * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
55 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
56 * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
57 * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
58 * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
59 * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
60 * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
62 *****************************************************************************/
64 * Please use this file (iwl-4965-hw.h) only for hardware-related definitions.
65 * Use iwl-commands.h for uCode API definitions.
66 * Use iwl-dev.h for driver implementation definitions.
69 #ifndef __iwl_4965_hw_h__
70 #define __iwl_4965_hw_h__
75 #define IWL4965_EEPROM_IMG_SIZE 1024
78 * uCode queue management definitions ...
79 * Queue #4 is the command queue for 3945 and 4965; map it to Tx FIFO chnl 4.
80 * The first queue used for block-ack aggregation is #7 (4965 only).
81 * All block-ack aggregation queues should map to Tx DMA/FIFO channel 7.
83 #define IWL_CMD_QUEUE_NUM 4
84 #define IWL_CMD_FIFO_NUM 4
85 #define IWL49_FIRST_AMPDU_QUEUE 7
88 #define SHORT_SLOT_TIME 9
89 #define LONG_SLOT_TIME 20
92 #define IWL49_RSSI_OFFSET 44
97 #define PCI_CFG_RETRY_TIMEOUT 0x041
98 #define PCI_CFG_POWER_SOURCE 0x0C8
99 #define PCI_REG_WUM8 0x0E8
100 #define PCI_CFG_LINK_CTRL 0x0F0
102 /* PCI register values */
103 #define PCI_CFG_LINK_CTRL_VAL_L0S_EN 0x01
104 #define PCI_CFG_LINK_CTRL_VAL_L1_EN 0x02
105 #define PCI_CFG_CMD_REG_INT_DIS_MSK 0x04
106 #define PCI_CFG_PMC_PME_FROM_D3COLD_SUPPORT (0x80000000)
109 #define IWL_NUM_SCAN_RATES (2)
111 #define IWL_DEFAULT_TX_RETRY 15
114 /* Sizes and addresses for instruction and data memory (SRAM) in
115 * 4965's embedded processor. Driver access is via HBUS_TARG_MEM_* regs. */
116 #define IWL49_RTC_INST_LOWER_BOUND (0x000000)
117 #define IWL49_RTC_INST_UPPER_BOUND (0x018000)
119 #define IWL49_RTC_DATA_LOWER_BOUND (0x800000)
120 #define IWL49_RTC_DATA_UPPER_BOUND (0x80A000)
122 #define IWL49_RTC_INST_SIZE (IWL49_RTC_INST_UPPER_BOUND - \
123 IWL49_RTC_INST_LOWER_BOUND)
124 #define IWL49_RTC_DATA_SIZE (IWL49_RTC_DATA_UPPER_BOUND - \
125 IWL49_RTC_DATA_LOWER_BOUND)
127 #define IWL49_MAX_INST_SIZE IWL49_RTC_INST_SIZE
128 #define IWL49_MAX_DATA_SIZE IWL49_RTC_DATA_SIZE
130 /* Size of uCode instruction memory in bootstrap state machine */
131 #define IWL49_MAX_BSM_SIZE BSM_SRAM_SIZE
133 static inline int iwl4965_hw_valid_rtc_data_addr(u32 addr
)
135 return (addr
>= IWL49_RTC_DATA_LOWER_BOUND
) &&
136 (addr
< IWL49_RTC_DATA_UPPER_BOUND
);
139 /********************* START TEMPERATURE *************************************/
142 * 4965 temperature calculation.
144 * The driver must calculate the device temperature before calculating
145 * a txpower setting (amplifier gain is temperature dependent). The
146 * calculation uses 4 measurements, 3 of which (R1, R2, R3) are calibration
147 * values used for the life of the driver, and one of which (R4) is the
148 * real-time temperature indicator.
150 * uCode provides all 4 values to the driver via the "initialize alive"
151 * notification (see struct iwl4965_init_alive_resp). After the runtime uCode
152 * image loads, uCode updates the R4 value via statistics notifications
153 * (see STATISTICS_NOTIFICATION), which occur after each received beacon
154 * when associated, or can be requested via REPLY_STATISTICS_CMD.
156 * NOTE: uCode provides the R4 value as a 23-bit signed value. Driver
157 * must sign-extend to 32 bits before applying formula below.
161 * degrees Kelvin = ((97 * 259 * (R4 - R2) / (R3 - R1)) / 100) + 8
163 * NOTE: The basic formula is 259 * (R4-R2) / (R3-R1). The 97/100 is
164 * an additional correction, which should be centered around 0 degrees
165 * Celsius (273 degrees Kelvin). The 8 (3 percent of 273) compensates for
166 * centering the 97/100 correction around 0 degrees K.
168 * Add 273 to Kelvin value to find degrees Celsius, for comparing current
169 * temperature with factory-measured temperatures when calculating txpower
172 #define TEMPERATURE_CALIB_KELVIN_OFFSET 8
173 #define TEMPERATURE_CALIB_A_VAL 259
175 /* Limit range of calculated temperature to be between these Kelvin values */
176 #define IWL_TX_POWER_TEMPERATURE_MIN (263)
177 #define IWL_TX_POWER_TEMPERATURE_MAX (410)
179 #define IWL_TX_POWER_TEMPERATURE_OUT_OF_RANGE(t) \
180 (((t) < IWL_TX_POWER_TEMPERATURE_MIN) || \
181 ((t) > IWL_TX_POWER_TEMPERATURE_MAX))
183 /********************* END TEMPERATURE ***************************************/
185 /********************* START TXPOWER *****************************************/
188 * 4965 txpower calculations rely on information from three sources:
191 * 2) "initialize" alive notification
192 * 3) statistics notifications
194 * EEPROM data consists of:
196 * 1) Regulatory information (max txpower and channel usage flags) is provided
197 * separately for each channel that can possibly supported by 4965.
198 * 40 MHz wide (.11n fat) channels are listed separately from 20 MHz
201 * See struct iwl4965_eeprom_channel for format, and struct iwl4965_eeprom
202 * for locations in EEPROM.
204 * 2) Factory txpower calibration information is provided separately for
205 * sub-bands of contiguous channels. 2.4GHz has just one sub-band,
206 * but 5 GHz has several sub-bands.
208 * In addition, per-band (2.4 and 5 Ghz) saturation txpowers are provided.
210 * See struct iwl4965_eeprom_calib_info (and the tree of structures
211 * contained within it) for format, and struct iwl4965_eeprom for
212 * locations in EEPROM.
214 * "Initialization alive" notification (see struct iwl4965_init_alive_resp)
217 * 1) Temperature calculation parameters.
219 * 2) Power supply voltage measurement.
221 * 3) Tx gain compensation to balance 2 transmitters for MIMO use.
223 * Statistics notifications deliver:
225 * 1) Current values for temperature param R4.
229 * To calculate a txpower setting for a given desired target txpower, channel,
230 * modulation bit rate, and transmitter chain (4965 has 2 transmitters to
231 * support MIMO and transmit diversity), driver must do the following:
233 * 1) Compare desired txpower vs. (EEPROM) regulatory limit for this channel.
234 * Do not exceed regulatory limit; reduce target txpower if necessary.
236 * If setting up txpowers for MIMO rates (rate indexes 8-15, 24-31),
237 * 2 transmitters will be used simultaneously; driver must reduce the
238 * regulatory limit by 3 dB (half-power) for each transmitter, so the
239 * combined total output of the 2 transmitters is within regulatory limits.
242 * 2) Compare target txpower vs. (EEPROM) saturation txpower *reduced by
243 * backoff for this bit rate*. Do not exceed (saturation - backoff[rate]);
244 * reduce target txpower if necessary.
246 * Backoff values below are in 1/2 dB units (equivalent to steps in
247 * txpower gain tables):
249 * OFDM 6 - 36 MBit: 10 steps (5 dB)
250 * OFDM 48 MBit: 15 steps (7.5 dB)
251 * OFDM 54 MBit: 17 steps (8.5 dB)
252 * OFDM 60 MBit: 20 steps (10 dB)
253 * CCK all rates: 10 steps (5 dB)
255 * Backoff values apply to saturation txpower on a per-transmitter basis;
256 * when using MIMO (2 transmitters), each transmitter uses the same
257 * saturation level provided in EEPROM, and the same backoff values;
258 * no reduction (such as with regulatory txpower limits) is required.
260 * Saturation and Backoff values apply equally to 20 Mhz (legacy) channel
261 * widths and 40 Mhz (.11n fat) channel widths; there is no separate
262 * factory measurement for fat channels.
264 * The result of this step is the final target txpower. The rest of
265 * the steps figure out the proper settings for the device to achieve
266 * that target txpower.
269 * 3) Determine (EEPROM) calibration sub band for the target channel, by
270 * comparing against first and last channels in each sub band
271 * (see struct iwl4965_eeprom_calib_subband_info).
274 * 4) Linearly interpolate (EEPROM) factory calibration measurement sets,
275 * referencing the 2 factory-measured (sample) channels within the sub band.
277 * Interpolation is based on difference between target channel's frequency
278 * and the sample channels' frequencies. Since channel numbers are based
279 * on frequency (5 MHz between each channel number), this is equivalent
280 * to interpolating based on channel number differences.
282 * Note that the sample channels may or may not be the channels at the
283 * edges of the sub band. The target channel may be "outside" of the
284 * span of the sampled channels.
286 * Driver may choose the pair (for 2 Tx chains) of measurements (see
287 * struct iwl4965_eeprom_calib_ch_info) for which the actual measured
288 * txpower comes closest to the desired txpower. Usually, though,
289 * the middle set of measurements is closest to the regulatory limits,
290 * and is therefore a good choice for all txpower calculations (this
291 * assumes that high accuracy is needed for maximizing legal txpower,
292 * while lower txpower configurations do not need as much accuracy).
294 * Driver should interpolate both members of the chosen measurement pair,
295 * i.e. for both Tx chains (radio transmitters), unless the driver knows
296 * that only one of the chains will be used (e.g. only one tx antenna
297 * connected, but this should be unusual). The rate scaling algorithm
298 * switches antennas to find best performance, so both Tx chains will
299 * be used (although only one at a time) even for non-MIMO transmissions.
301 * Driver should interpolate factory values for temperature, gain table
302 * index, and actual power. The power amplifier detector values are
303 * not used by the driver.
305 * Sanity check: If the target channel happens to be one of the sample
306 * channels, the results should agree with the sample channel's
310 * 5) Find difference between desired txpower and (interpolated)
311 * factory-measured txpower. Using (interpolated) factory gain table index
312 * (shown elsewhere) as a starting point, adjust this index lower to
313 * increase txpower, or higher to decrease txpower, until the target
314 * txpower is reached. Each step in the gain table is 1/2 dB.
316 * For example, if factory measured txpower is 16 dBm, and target txpower
317 * is 13 dBm, add 6 steps to the factory gain index to reduce txpower
321 * 6) Find difference between current device temperature and (interpolated)
322 * factory-measured temperature for sub-band. Factory values are in
323 * degrees Celsius. To calculate current temperature, see comments for
324 * "4965 temperature calculation".
326 * If current temperature is higher than factory temperature, driver must
327 * increase gain (lower gain table index), and vice verse.
329 * Temperature affects gain differently for different channels:
331 * 2.4 GHz all channels: 3.5 degrees per half-dB step
332 * 5 GHz channels 34-43: 4.5 degrees per half-dB step
333 * 5 GHz channels >= 44: 4.0 degrees per half-dB step
335 * NOTE: Temperature can increase rapidly when transmitting, especially
336 * with heavy traffic at high txpowers. Driver should update
337 * temperature calculations often under these conditions to
338 * maintain strong txpower in the face of rising temperature.
341 * 7) Find difference between current power supply voltage indicator
342 * (from "initialize alive") and factory-measured power supply voltage
343 * indicator (EEPROM).
345 * If the current voltage is higher (indicator is lower) than factory
346 * voltage, gain should be reduced (gain table index increased) by:
348 * (eeprom - current) / 7
350 * If the current voltage is lower (indicator is higher) than factory
351 * voltage, gain should be increased (gain table index decreased) by:
353 * 2 * (current - eeprom) / 7
355 * If number of index steps in either direction turns out to be > 2,
356 * something is wrong ... just use 0.
358 * NOTE: Voltage compensation is independent of band/channel.
360 * NOTE: "Initialize" uCode measures current voltage, which is assumed
361 * to be constant after this initial measurement. Voltage
362 * compensation for txpower (number of steps in gain table)
363 * may be calculated once and used until the next uCode bootload.
366 * 8) If setting up txpowers for MIMO rates (rate indexes 8-15, 24-31),
367 * adjust txpower for each transmitter chain, so txpower is balanced
368 * between the two chains. There are 5 pairs of tx_atten[group][chain]
369 * values in "initialize alive", one pair for each of 5 channel ranges:
371 * Group 0: 5 GHz channel 34-43
372 * Group 1: 5 GHz channel 44-70
373 * Group 2: 5 GHz channel 71-124
374 * Group 3: 5 GHz channel 125-200
375 * Group 4: 2.4 GHz all channels
377 * Add the tx_atten[group][chain] value to the index for the target chain.
378 * The values are signed, but are in pairs of 0 and a non-negative number,
379 * so as to reduce gain (if necessary) of the "hotter" channel. This
380 * avoids any need to double-check for regulatory compliance after
384 * 9) If setting up for a CCK rate, lower the gain by adding a CCK compensation
385 * value to the index:
387 * Hardware rev B: 9 steps (4.5 dB)
388 * Hardware rev C: 5 steps (2.5 dB)
390 * Hardware rev for 4965 can be determined by reading CSR_HW_REV_WA_REG,
391 * bits [3:2], 1 = B, 2 = C.
393 * NOTE: This compensation is in addition to any saturation backoff that
394 * might have been applied in an earlier step.
397 * 10) Select the gain table, based on band (2.4 vs 5 GHz).
399 * Limit the adjusted index to stay within the table!
402 * 11) Read gain table entries for DSP and radio gain, place into appropriate
403 * location(s) in command (struct iwl4965_txpowertable_cmd).
406 /* Limit range of txpower output target to be between these values */
407 #define IWL_TX_POWER_TARGET_POWER_MIN (0) /* 0 dBm = 1 milliwatt */
408 #define IWL_TX_POWER_TARGET_POWER_MAX (16) /* 16 dBm */
411 * When MIMO is used (2 transmitters operating simultaneously), driver should
412 * limit each transmitter to deliver a max of 3 dB below the regulatory limit
413 * for the device. That is, use half power for each transmitter, so total
414 * txpower is within regulatory limits.
416 * The value "6" represents number of steps in gain table to reduce power 3 dB.
417 * Each step is 1/2 dB.
419 #define IWL_TX_POWER_MIMO_REGULATORY_COMPENSATION (6)
422 * CCK gain compensation.
424 * When calculating txpowers for CCK, after making sure that the target power
425 * is within regulatory and saturation limits, driver must additionally
426 * back off gain by adding these values to the gain table index.
428 * Hardware rev for 4965 can be determined by reading CSR_HW_REV_WA_REG,
429 * bits [3:2], 1 = B, 2 = C.
431 #define IWL_TX_POWER_CCK_COMPENSATION_B_STEP (9)
432 #define IWL_TX_POWER_CCK_COMPENSATION_C_STEP (5)
435 * 4965 power supply voltage compensation for txpower
437 #define TX_POWER_IWL_VOLTAGE_CODES_PER_03V (7)
442 * The following tables contain pair of values for setting txpower, i.e.
443 * gain settings for the output of the device's digital signal processor (DSP),
444 * and for the analog gain structure of the transmitter.
446 * Each entry in the gain tables represents a step of 1/2 dB. Note that these
447 * are *relative* steps, not indications of absolute output power. Output
448 * power varies with temperature, voltage, and channel frequency, and also
449 * requires consideration of average power (to satisfy regulatory constraints),
450 * and peak power (to avoid distortion of the output signal).
452 * Each entry contains two values:
453 * 1) DSP gain (or sometimes called DSP attenuation). This is a fine-grained
454 * linear value that multiplies the output of the digital signal processor,
455 * before being sent to the analog radio.
456 * 2) Radio gain. This sets the analog gain of the radio Tx path.
457 * It is a coarser setting, and behaves in a logarithmic (dB) fashion.
459 * EEPROM contains factory calibration data for txpower. This maps actual
460 * measured txpower levels to gain settings in the "well known" tables
461 * below ("well-known" means here that both factory calibration *and* the
462 * driver work with the same table).
464 * There are separate tables for 2.4 GHz and 5 GHz bands. The 5 GHz table
465 * has an extension (into negative indexes), in case the driver needs to
466 * boost power setting for high device temperatures (higher than would be
467 * present during factory calibration). A 5 Ghz EEPROM index of "40"
468 * corresponds to the 49th entry in the table used by the driver.
470 #define MIN_TX_GAIN_INDEX (0) /* highest gain, lowest idx, 2.4 */
471 #define MIN_TX_GAIN_INDEX_52GHZ_EXT (-9) /* highest gain, lowest idx, 5 */
476 * Index Dsp gain Radio gain
477 * 0 110 0x3f (highest gain)
581 * Index Dsp gain Radio gain
582 * -9 123 0x3F (highest gain)
694 * Sanity checks and default values for EEPROM regulatory levels.
695 * If EEPROM values fall outside MIN/MAX range, use default values.
697 * Regulatory limits refer to the maximum average txpower allowed by
698 * regulatory agencies in the geographies in which the device is meant
699 * to be operated. These limits are SKU-specific (i.e. geography-specific),
700 * and channel-specific; each channel has an individual regulatory limit
701 * listed in the EEPROM.
703 * Units are in half-dBm (i.e. "34" means 17 dBm).
705 #define IWL_TX_POWER_DEFAULT_REGULATORY_24 (34)
706 #define IWL_TX_POWER_DEFAULT_REGULATORY_52 (34)
707 #define IWL_TX_POWER_REGULATORY_MIN (0)
708 #define IWL_TX_POWER_REGULATORY_MAX (34)
711 * Sanity checks and default values for EEPROM saturation levels.
712 * If EEPROM values fall outside MIN/MAX range, use default values.
714 * Saturation is the highest level that the output power amplifier can produce
715 * without significant clipping distortion. This is a "peak" power level.
716 * Different types of modulation (i.e. various "rates", and OFDM vs. CCK)
717 * require differing amounts of backoff, relative to their average power output,
718 * in order to avoid clipping distortion.
720 * Driver must make sure that it is violating neither the saturation limit,
721 * nor the regulatory limit, when calculating Tx power settings for various
724 * Units are in half-dBm (i.e. "38" means 19 dBm).
726 #define IWL_TX_POWER_DEFAULT_SATURATION_24 (38)
727 #define IWL_TX_POWER_DEFAULT_SATURATION_52 (38)
728 #define IWL_TX_POWER_SATURATION_MIN (20)
729 #define IWL_TX_POWER_SATURATION_MAX (50)
732 * Channel groups used for Tx Attenuation calibration (MIMO tx channel balance)
733 * and thermal Txpower calibration.
735 * When calculating txpower, driver must compensate for current device
736 * temperature; higher temperature requires higher gain. Driver must calculate
737 * current temperature (see "4965 temperature calculation"), then compare vs.
738 * factory calibration temperature in EEPROM; if current temperature is higher
739 * than factory temperature, driver must *increase* gain by proportions shown
740 * in table below. If current temperature is lower than factory, driver must
743 * Different frequency ranges require different compensation, as shown below.
745 /* Group 0, 5.2 GHz ch 34-43: 4.5 degrees per 1/2 dB. */
746 #define CALIB_IWL_TX_ATTEN_GR1_FCH 34
747 #define CALIB_IWL_TX_ATTEN_GR1_LCH 43
749 /* Group 1, 5.3 GHz ch 44-70: 4.0 degrees per 1/2 dB. */
750 #define CALIB_IWL_TX_ATTEN_GR2_FCH 44
751 #define CALIB_IWL_TX_ATTEN_GR2_LCH 70
753 /* Group 2, 5.5 GHz ch 71-124: 4.0 degrees per 1/2 dB. */
754 #define CALIB_IWL_TX_ATTEN_GR3_FCH 71
755 #define CALIB_IWL_TX_ATTEN_GR3_LCH 124
757 /* Group 3, 5.7 GHz ch 125-200: 4.0 degrees per 1/2 dB. */
758 #define CALIB_IWL_TX_ATTEN_GR4_FCH 125
759 #define CALIB_IWL_TX_ATTEN_GR4_LCH 200
761 /* Group 4, 2.4 GHz all channels: 3.5 degrees per 1/2 dB. */
762 #define CALIB_IWL_TX_ATTEN_GR5_FCH 1
763 #define CALIB_IWL_TX_ATTEN_GR5_LCH 20
766 CALIB_CH_GROUP_1
= 0,
767 CALIB_CH_GROUP_2
= 1,
768 CALIB_CH_GROUP_3
= 2,
769 CALIB_CH_GROUP_4
= 3,
770 CALIB_CH_GROUP_5
= 4,
774 /********************* END TXPOWER *****************************************/
780 * Most communication between driver and 4965 is via queues of data buffers.
781 * For example, all commands that the driver issues to device's embedded
782 * controller (uCode) are via the command queue (one of the Tx queues). All
783 * uCode command responses/replies/notifications, including Rx frames, are
784 * conveyed from uCode to driver via the Rx queue.
786 * Most support for these queues, including handshake support, resides in
787 * structures in host DRAM, shared between the driver and the device. When
788 * allocating this memory, the driver must make sure that data written by
789 * the host CPU updates DRAM immediately (and does not get "stuck" in CPU's
790 * cache memory), so DRAM and cache are consistent, and the device can
791 * immediately see changes made by the driver.
793 * 4965 supports up to 16 DRAM-based Tx queues, and services these queues via
794 * up to 7 DMA channels (FIFOs). Each Tx queue is supported by a circular array
795 * in DRAM containing 256 Transmit Frame Descriptors (TFDs).
797 #define IWL49_NUM_FIFOS 7
798 #define IWL49_CMD_FIFO_NUM 4
799 #define IWL49_NUM_QUEUES 16
800 #define IWL49_NUM_AMPDU_QUEUES 8
804 * struct iwl4965_schedq_bc_tbl
808 * Each Tx queue uses a byte-count table containing 320 entries:
809 * one 16-bit entry for each of 256 TFDs, plus an additional 64 entries that
810 * duplicate the first 64 entries (to avoid wrap-around within a Tx window;
811 * max Tx window is 64 TFDs).
813 * When driver sets up a new TFD, it must also enter the total byte count
814 * of the frame to be transmitted into the corresponding entry in the byte
815 * count table for the chosen Tx queue. If the TFD index is 0-63, the driver
816 * must duplicate the byte count entry in corresponding index 256-319.
818 * padding puts each byte count table on a 1024-byte boundary;
819 * 4965 assumes tables are separated by 1024 bytes.
821 struct iwl4965_scd_bc_tbl
{
822 __le16 tfd_offset
[TFD_QUEUE_BC_SIZE
];
823 u8 pad
[1024 - (TFD_QUEUE_BC_SIZE
) * sizeof(__le16
)];
824 } __attribute__ ((packed
));
826 #endif /* !__iwl_4965_hw_h__ */