hi Luca,
On Sun, Mar 9, 2014 at 4:40 PM, Luciano Coelho <luciano.coelho@xxxxxxxxx> wrote:
> In order to support channel switch with multiple vifs and multiple
> contexts, we implement a concept of channel context reservation. This
> allows us to reserve a channel context to be used later.
>
> The reservation functionality is not tied directly to channel switch
> and may be used in other situations (eg. reserving a channel context
> during IBSS join).
>
> We first check if an existing compatible context exists and if it
> does, we reserve it. If there is no compatible context we create a
> new one and reserve it.
>
> Signed-off-by: Luciano Coelho <luciano.coelho@xxxxxxxxx>
> ---
[...]
> +int ieee80211_vif_use_reserved_context(struct ieee80211_sub_if_data *sdata,
> + u32 *changed)
> +{
[...]
> +
> + *changed = local_changed;
> +
> + ieee80211_recalc_chanctx_chantype(local, ctx);
> + ieee80211_recalc_smps_chanctx(local, ctx);
> + ieee80211_recalc_radar_chanctx(local, ctx);
any reason for not calling ieee80211_recalc_chanctx_min_def() as well?
Eliad.
--
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
