On Thu, Nov 22, 2012 at 6:06 PM, Eliad Peller <eliad@xxxxxxxxxx> wrote: > From: Victor Goldenshtein <victorg@xxxxxx> > > In 18xx the calibration process of the PHY Cortex domain > requires to perform an active calibration of the channel > before it can be used for transmission. To fulfill world > wide regulatory restrictions, fw should be always > synchronized/updated with current CRDA configuration. > Add a new "CMD_DFS_CHANNEL_CONFIG" command to update the > fw with current reg-domain, this command passes a bit map > of channels that are allowed to be used for transmission. > > The driver shall update the fw during initialization and > after each change in the current reg-domain > configuration. The driver will save the channel number of > incoming beacons during the scan process, as they might > be a result of the passive scan on > "IEEE80211_CHAN_PASSIVE_SCAN" channel and will update the > fw accordingly once the scan is finished, the purpose of > this is to be ready in case of the authentication request > on one of these disabled (uncalibrated) channels. > > The new command requires to wait for the fw completion > event "DFS_CHANNELS_CONFIG_COMPLETE_EVENT". > > No scan commands (including the sched scan) can be > executed concurrently with the "CMD_DFS_CHANNEL_CONFIG", > wl->mutex ensures that. [...] > /* The mbox event mask */ > u32 event_mask; > + /* Specific chip family mbox event mask */ > + u32 chip_family_event_mask; This chip_family_event_mask is no longer necessary, since we have a different event mask for each chip family now. I'll post a v3 of this patch before continuing with the next series. Arik -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
