Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Eugene Krasnikov <k.eugene.e@gmail.com>
Cc: linux-wireless@vger.kernel.org, wcn36xx@lists.infradead.org
Subject: Re: [PATCH v2 01/16] wcn36xx: Add main.c
Date: Fri, 23 Aug 2013 11:22:54 +0200	[thread overview]
Message-ID: <1377249774.14021.15.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1377248299-21007-2-git-send-email-k.eugene.e@gmail.com> (sfid-20130823_105928_264143_4BF93F2F)

On Fri, 2013-08-23 at 10:58 +0200, Eugene Krasnikov wrote:

> +static const struct ieee80211_iface_limit if_limits[] = {
> +	{ .max = 2, .types = BIT(NL80211_IFTYPE_STATION) },
> +	{ .max = 1, .types = BIT(NL80211_IFTYPE_AP) },
> +};
> +
> +static const struct ieee80211_iface_combination if_comb = {
> +	.limits = if_limits,
> +	.n_limits = ARRAY_SIZE(if_limits),
> +	.max_interfaces = 2,
> +	.num_different_channels = 1,
> +};

> +static int wcn36xx_add_interface(struct ieee80211_hw *hw,
> +				 struct ieee80211_vif *vif)
> +{
> +	struct wcn36xx *wcn = hw->priv;
> +
> +	wcn36xx_dbg(WCN36XX_DBG_MAC, "mac add interface vif %p type %d\n",
> +		    vif, vif->type);
> +
> +	wcn->current_vif = (struct wcn36xx_vif *)vif->drv_priv;

If you actually support two interfaces (and that looks more likely now)
I don't think this "current_vif" makes any sense at all, it'll be
randomly pointing to one or the other depending on which one was added
last.

> +static int wcn36xx_sta_add(struct ieee80211_hw *hw, struct ieee80211_vif *vif,
> +			   struct ieee80211_sta *sta)
> +{
> +	struct wcn36xx *wcn = hw->priv;
> +
> +	wcn36xx_dbg(WCN36XX_DBG_MAC, "mac sta add vif %p sta %pM\n",
> +		    vif, sta->addr);
> +
> +	wcn->sta = (struct wcn36xx_sta *)sta->drv_priv;
> +	wcn->aid = sta->aid;

You support more than one interface and AP, but there's no way this code
can then be correct. It seems to me that you're really only supporting a
single client interface correctly right now.

johannes


  reply	other threads:[~2013-08-23  9:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23  8:58 [PATCH v2 00/16] wcn36xx: mac80211 driver for Qualcomm WCN3660/WCN3680 hardware Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 01/16] wcn36xx: Add main.c Eugene Krasnikov
2013-08-23  9:22   ` Johannes Berg [this message]
2013-08-23  9:42     ` Eugene Krasnikov
2013-08-23  9:47       ` Johannes Berg
2013-08-23 10:06         ` Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 02/16] wcn36xx: add debug.c Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 03/16] wcn36xx: add debug.h Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 04/16] wcn36xx: add dxe.c Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 05/16] wcn36xx: add dxe.h Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 06/16] wcn36xx: add hal.h Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 07/16] wcn36xx: add pmc.c Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 08/16] wcn36xx: add pmc.h Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 09/16] wcn36xx: add smd.c Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 10/16] wcn36xx: add smd.h Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 11/16] wcn36xx: add txrx.c Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 12/16] wcn36xx: add txrx.h Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 13/16] wcn36xx: add wcn36xx.h Eugene Krasnikov
2013-08-23 23:02   ` Joe Perches
2013-08-26  7:23     ` Eugene Krasnikov
2013-09-02 14:15     ` Kalle Valo
2013-09-02 17:49       ` Joe Perches
2013-09-03  5:08         ` Kalle Valo
2013-09-03  5:13           ` Joe Perches
2013-09-03  5:25             ` Kalle Valo
2013-09-03  5:27               ` Joe Perches
2013-09-03  5:39                 ` Kalle Valo
2013-09-03  5:41                   ` Joe Perches
2013-09-03  5:48                     ` Kalle Valo
2013-08-23  8:58 ` [PATCH v2 14/16] wcn36xx: add Makefile Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 15/16] wcn36xx: add Kconfig Eugene Krasnikov
2013-08-23  8:58 ` [PATCH v2 16/16] wcn36xx: Add wcn36xx to ath Makefile and Kconfig Eugene Krasnikov

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=1377249774.14021.15.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=k.eugene.e@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wcn36xx@lists.infradead.org \
    /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