All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janusz Dziedzic <janusz.dziedzic@tieto.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
	Felix Fietkau <nbd@openwrt.org>
Subject: Re: [RFC] ath9k: advertise p2p dev support when chanctx
Date: Mon, 15 Jun 2015 13:38:14 +0200	[thread overview]
Message-ID: <CALhHN=pUKuXAEb3JEEVTHATEHhvoLe52QDh-pixiS9oUo=6j6Q@mail.gmail.com> (raw)
In-Reply-To: <21886.43539.833126.629494@gargle.gargle.HOWL>

On 15 June 2015 at 12:33, Sujith Manoharan <sujith@msujith.org> wrote:
> Janusz Dziedzic wrote:
>> Add p2p dev support when ath9k loaded with
>> use_chanctx=1. This will fix problem, when first
>> interface is an AP and next we would like to run
>> p2p_find. Before p2p scan failed.
>>
>> Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
>> ---
>> @Felix, Sujith please review. I am not sure if didn't miss some
>> case for NL80211_IFTYPE_P2P_DEVICE (special handling required?).
>
> At least the callbacks for adding/removing interfaces need
> to be handled ?
>
Strange, but I didn't hit any problem yet with my simple patch.

> But, can you describe the sequence of commands used that
> resulted in this issue ?
>
1. load ath9k with use_chanctx=1
2. run wpa_supplicant using wlan0
3. connect wlan0 to AP
4. when we are connected, run p2p_find form wpa_cli
5. scan will failed with Operation not supported (even I will
force-ap-scan, while chanctx version using hw_scan callback ...)
6. p2p_find will fail

BR
Janusz

WARNING: multiple messages have this Message-ID (diff)
From: Janusz Dziedzic <janusz.dziedzic@tieto.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC] ath9k: advertise p2p dev support when chanctx
Date: Mon, 15 Jun 2015 13:38:14 +0200	[thread overview]
Message-ID: <CALhHN=pUKuXAEb3JEEVTHATEHhvoLe52QDh-pixiS9oUo=6j6Q@mail.gmail.com> (raw)
In-Reply-To: <21886.43539.833126.629494@gargle.gargle.HOWL>

On 15 June 2015 at 12:33, Sujith Manoharan <sujith@msujith.org> wrote:
> Janusz Dziedzic wrote:
>> Add p2p dev support when ath9k loaded with
>> use_chanctx=1. This will fix problem, when first
>> interface is an AP and next we would like to run
>> p2p_find. Before p2p scan failed.
>>
>> Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
>> ---
>> @Felix, Sujith please review. I am not sure if didn't miss some
>> case for NL80211_IFTYPE_P2P_DEVICE (special handling required?).
>
> At least the callbacks for adding/removing interfaces need
> to be handled ?
>
Strange, but I didn't hit any problem yet with my simple patch.

> But, can you describe the sequence of commands used that
> resulted in this issue ?
>
1. load ath9k with use_chanctx=1
2. run wpa_supplicant using wlan0
3. connect wlan0 to AP
4. when we are connected, run p2p_find form wpa_cli
5. scan will failed with Operation not supported (even I will
force-ap-scan, while chanctx version using hw_scan callback ...)
6. p2p_find will fail

BR
Janusz

  reply	other threads:[~2015-06-15 11:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  5:10 [RFC] ath9k: advertise p2p dev support when chanctx Janusz Dziedzic
2015-06-10  5:10 ` [ath9k-devel] " Janusz Dziedzic
2015-06-15 10:33 ` Sujith Manoharan
2015-06-15 10:33   ` [ath9k-devel] " Sujith Manoharan
2015-06-15 11:38   ` Janusz Dziedzic [this message]
2015-06-15 11:38     ` Janusz Dziedzic
2015-06-15 11:46     ` Janusz Dziedzic
2015-06-15 11:46       ` [ath9k-devel] " Janusz Dziedzic
2015-06-15 15:47     ` Sujith Manoharan
2015-06-15 15:47       ` [ath9k-devel] " Sujith Manoharan
2015-06-15 18:19       ` Arend van Spriel
2015-06-15 18:19         ` [ath9k-devel] " Arend van Spriel
2015-06-16  1:25         ` Sujith Manoharan
2015-06-16  1:25           ` [ath9k-devel] " Sujith Manoharan
2015-06-16  6:30           ` Janusz Dziedzic
2015-06-16  6:30             ` [ath9k-devel] " Janusz Dziedzic
2015-06-16  7:08             ` Johannes Berg
2015-06-16  7:08               ` [ath9k-devel] " Johannes Berg
2015-06-16  7:53             ` Sujith

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='CALhHN=pUKuXAEb3JEEVTHATEHhvoLe52QDh-pixiS9oUo=6j6Q@mail.gmail.com' \
    --to=janusz.dziedzic@tieto.com \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.org \
    --cc=sujith@msujith.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.