linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Siva Rebbagondla <siva8118@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>,
	Prameela Rani Garnepudi <prameela.j04cs@gmail.com>,
	rishikesh.basu@redpinesignals.com,
	Siva Rebbagondla <siva.rebbagondla@redpinesignals.com>
Subject: Re: [v4] rsi: add support for hardware scan offload
Date: Wed, 9 Jan 2019 08:15:47 +0530	[thread overview]
Message-ID: <CANGSkXTuHK8uzOOjOTHo_Gkvk8f2ndD=1hEQw4ZUGD0kVSs81g@mail.gmail.com> (raw)
In-Reply-To: <87muobqeco.fsf@kamboji.qca.qualcomm.com>

On Tue, Jan 8, 2019 at 10:24 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> Siva Rebbagondla <siva8118@gmail.com> writes:
>
> > From: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>
> >
> > With the current approach of scanning, roaming delays are observed.
> > Firmware has support for back ground scanning. To get this advantage,
> > mac80211 hardware scan is implemented, which decides type of scan to
> > do based on connected state.
> >
> > When station is in not connected, driver returns with special value 1
> > to trigger software scan in mac80211. In case of connected state,
> > background scan will be triggered.
> >
> > Signed-off-by: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>
> > Signed-off-by: Siva Rebbagondla <siva.rebbagondla@redpinesignals.com>
> > ---
> > changes in v4: renamed return value in hw_scan from "-EPERM" -> "1" [Jberg]
> > changes in v3: replaced rsi_prepare_probe_request() with ieee80211_probereq_get() [Kvalo]
> > changes in v2: none
>
> This depends on:
>
> e9da68ddea60 mac80211: allow hardware scan to fall back to software
>
> But that's in w-d-next now so this is safe to be apply.
>
> --
> Kalle Valo

Yes Kvalo, you can apply this patch to w-d-next.

Brgds,
Siva Rebbagondla

  reply	other threads:[~2019-01-09  2:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-27  9:26 [v4] rsi: add support for hardware scan offload Siva Rebbagondla
2019-01-08 16:54 ` Kalle Valo
2019-01-09  2:45   ` Siva Rebbagondla [this message]
2019-01-10 11:38 ` Kalle Valo

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='CANGSkXTuHK8uzOOjOTHo_Gkvk8f2ndD=1hEQw4ZUGD0kVSs81g@mail.gmail.com' \
    --to=siva8118@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=prameela.j04cs@gmail.com \
    --cc=rishikesh.basu@redpinesignals.com \
    --cc=siva.rebbagondla@redpinesignals.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).