From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>,
Antonio Quartulli <ordex@autistici.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
<linux-wireless@vger.kernel.org>,
Rodriguez Luis <rodrigue@qca.qualcomm.com>,
<ath9k-devel@lists.ath9k.org>
Subject: Re: [RFC 1/2] ath9k_htc: Advertize allowed vif combinations
Date: Thu, 27 Sep 2012 21:23:35 +0530 [thread overview]
Message-ID: <5064767F.8050701@qca.qualcomm.com> (raw)
In-Reply-To: <1348761132-8344-1-git-send-email-mohammed@qca.qualcomm.com>
On Thursday 27 September 2012 09:22 PM, Mohammed Shafi Shajakhan wrote:
> From: Antonio Quartulli <ordex@autistici.org>
>
> Advertize allowed VIFs combinations to the cfg80211 sublayer.
> Other than that, practical tests shown that ath9k_htc devices allow an
> IBSS VIF to coexist with VIF set up on other modes, so advertize
> that to. We can also further add p2p/mesh mode to be advertized
> in the combinations allowed.
Antonio tomorrow evening i will just do a sanity test and send these
stuff as patch. thank you so much for your patience!
>
> Signed-off-by: Antonio Quartulli <ordex@autistici.org>
> Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
> ---
> drivers/net/wireless/ath/ath9k/htc_drv_init.c | 35 +++++++++++++++++++++++++
> 1 files changed, 35 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/htc_drv_init.c b/drivers/net/wireless/ath/ath9k/htc_drv_init.c
> index d98255e..4d65af1 100644
> --- a/drivers/net/wireless/ath/ath9k/htc_drv_init.c
> +++ b/drivers/net/wireless/ath/ath9k/htc_drv_init.c
> @@ -694,6 +694,38 @@ err_hw:
> return ret;
> }
>
> +/*
> + * It is possible to have atmost ATH9K_HTC_MAX_BCN_VIF beaconing interfaces
> + * therefore either we have 1 IBSS + ATH9K_HTC_MAX_BCN_VIF - 1 AP's, or we
> + * have only ATH9K_HTC_MAX_BCN_VIF AP's
> + */
> +
> +static const struct ieee80211_iface_limit if_limits_ibss[] = {
> + {.max = ATH9K_HTC_MAX_VIF, .types = BIT(NL80211_IFTYPE_STATION)},
> + {.max = ATH9K_HTC_MAX_VIF - 1, .types = BIT(NL80211_IFTYPE_AP)},
> + {.max = 1, .types = BIT(NL80211_IFTYPE_ADHOC)},
> +};
> +
> +static const struct ieee80211_iface_limit if_limits_no_ibss[] = {
> + {.max = ATH9K_HTC_MAX_VIF, .types = BIT(NL80211_IFTYPE_STATION)},
> + {.max = ATH9K_HTC_MAX_VIF, .types = BIT(NL80211_IFTYPE_AP)},
> +};
> +
> +static const struct ieee80211_iface_combination if_comb[] = {
> + {.limits = if_limits_ibss,
> + .n_limits = ARRAY_SIZE(if_limits_ibss),
> + .max_interfaces = ATH9K_HTC_MAX_VIF,
> + .num_different_channels = 1,
> + .beacon_int_infra_match = true,
> + },
> + {.limits = if_limits_no_ibss,
> + .n_limits = ARRAY_SIZE(if_limits_no_ibss),
> + .max_interfaces = ATH9K_HTC_MAX_VIF,
> + .num_different_channels = 1,
> + .beacon_int_infra_match = true,
> + },
> +};
> +
> static void ath9k_set_hw_capab(struct ath9k_htc_priv *priv,
> struct ieee80211_hw *hw)
> {
> @@ -716,6 +748,9 @@ static void ath9k_set_hw_capab(struct ath9k_htc_priv *priv,
> BIT(NL80211_IFTYPE_P2P_GO) |
> BIT(NL80211_IFTYPE_P2P_CLIENT);
>
> + hw->wiphy->iface_combinations = if_comb;
> + hw->wiphy->n_iface_combinations = ARRAY_SIZE(if_comb);
> +
> hw->wiphy->flags &= ~WIPHY_FLAG_PS_ON_BY_DEFAULT;
>
> hw->wiphy->flags |= WIPHY_FLAG_IBSS_RSN |
>
--
thanks,
shafi
next prev parent reply other threads:[~2012-09-27 15:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 15:52 [RFC 1/2] ath9k_htc: Advertize allowed vif combinations Mohammed Shafi Shajakhan
2012-09-27 15:52 ` [RFC 2/2] ath9k_htc: Remove interface combination specific checks Mohammed Shafi Shajakhan
2012-09-27 15:53 ` Mohammed Shafi Shajakhan [this message]
2012-09-27 16:02 ` [RFC 1/2] ath9k_htc: Advertize allowed vif combinations Antonio Quartulli
2012-09-28 2:23 ` Sujith Manoharan
2012-09-28 4:57 ` Mohammed Shafi Shajakhan
2012-09-28 10:42 ` Sujith Manoharan
2012-09-29 9:31 ` Antonio Quartulli
2012-09-29 14:22 ` Adrian Chadd
2012-10-08 15:50 ` Mohammed Shafi
2012-10-10 0:10 ` Antonio Quartulli
2012-10-10 15:19 ` Mohammed Shafi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5064767F.8050701@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ordex@autistici.org \
--cc=rodrigue@qca.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).