linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [V4,1/3] brcmfmac: add support multi-scheduled scan
Date: Wed, 07 Jun 2017 17:53:13 +0300	[thread overview]
Message-ID: <87y3t34zom.fsf@codeaurora.org> (raw)
In-Reply-To: <621288e8-e950-5aea-7d27-c5cb802dd416@broadcom.com> (Arend van Spriel's message of "Wed, 7 Jun 2017 10:15:15 +0200")

Arend van Spriel <arend.vanspriel@broadcom.com> writes:

> On 5/22/2017 5:16 PM, Kalle Valo wrote:
>> Arend Van Spriel <arend.vanspriel@broadcom.com> wrote:
>>> From: Arend Van Spriel <arend.vanspriel@broadcom.com>
>>>
>>> This change adds support for multi-scheduled scan in the driver. It
>>> currently relies on g-scan support in firmware and will set struct
>>> wiphy::max_sched_scan_reqs accordingly. This is limited to 16 concurrent
>>> requests.
>>>
>>> The firmware currently has a limit of 64 channels that can be configured
>>> for all requests in total regardless whether there are duplicates. So if
>>> a request uses 35 channels there are 29 channels left for another reque=
st.
>>> When user-space does not specify any channels cfg80211 will add all
>>> channels defined by the wiphy instance to the request, which makes
>>> reaching the limit rather easy for dual-band devices.
>>>
>>> Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com>
>>> Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
>>> Reviewed-by: Franky Lin <franky.lin@broadcom.com>
>>> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
>>
>> I see new warnings:
>>
>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/pno.c: In function =E2=
=80=98brcmf_pno_config_sched_scans=E2=80=99:
>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/pno.c:166:6: warning: =
=E2=80=98mac_mask=E2=80=99 may be used uninitialized in this function [-Wma=
ybe-uninitialized]
>>    u8 *mac_mask;
>>        ^
>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/pno.c:183:2: warning: =
=E2=80=98mac_addr=E2=80=99 may be used uninitialized in this function [-Wma=
ybe-uninitialized]
>>    memcpy(pfn_mac.mac, mac_addr, ETH_ALEN);
>>    ^
>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/pno.c:165:6: note: =E2=
=80=98mac_addr=E2=80=99 was declared here
>>    u8 *mac_addr;
>>        ^
>>
>> 3 patches set to Changes Requested.
>>
>> 9736151 [V4,1/3] brcmfmac: add support multi-scheduled scan
>> 9736147 [V4,2/3] brcmfmac: add mutex to protect pno requests
>> 9736149 [V4,3/3] brcmfmac: add scheduled scan support for specified BSSI=
Ds
>
> Not seeing it here using gcc version 4.8.4 (Ubuntu
> 4.8.4-2ubuntu1~14.04.3).

My version is:

gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609

I don't think that's really exocit version of the compiler, or is it?

> Also tried using W=3D1 on the make command
> line. Getting a bunck of other warnings, but not the ones above.

This was without W=3D1, just a default compilation with all wireless
drivers enabled.

> Do you want me to fix it?

Yes, please. I try to keep the patches warning free, even if they are
false warnings.

--=20
Kalle Valo

  reply	other threads:[~2017-06-07 14:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19  7:57 [PATCH V4 1/3] brcmfmac: add support multi-scheduled scan Arend van Spriel
2017-05-19  7:57 ` [PATCH V4 2/3] brcmfmac: add mutex to protect pno requests Arend van Spriel
2017-05-19  7:57 ` [PATCH V4 3/3] brcmfmac: add scheduled scan support for specified BSSIDs Arend van Spriel
2017-05-22 15:16 ` [V4,1/3] brcmfmac: add support multi-scheduled scan Kalle Valo
2017-06-07  8:15   ` Arend van Spriel
2017-06-07 14:53     ` Kalle Valo [this message]
2017-06-07 16:46       ` Arend van Spriel

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=87y3t34zom.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).