From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Peter Oh <peter.oh@bowerswilkins.com>,
"Harms, Hannes" <hannes.harms@tu-bs.de>,
Ben Greear <greearb@candelatech.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: mesh point and ap mode on same interface
Date: Wed, 15 Nov 2017 11:36:49 +0100 [thread overview]
Message-ID: <5A0C18C1.4000507@broadcom.com> (raw)
In-Reply-To: <87lgj7hm5e.fsf@kamboji.qca.qualcomm.com>
On 11/15/2017 11:27 AM, Kalle Valo wrote:
> Arend van Spriel <arend.vanspriel@broadcom.com> writes:
>
>> On 11/15/2017 11:01 AM, Kalle Valo wrote:
>>> (adding linux-wireless for a cfg80211 question)
>>>
>>> Peter Oh <peter.oh@bowerswilkins.com> writes:
>>>> On 11/08/2017 04:49 AM, Harms, Hannes wrote:
>>>>
>>>>> I found a solution for the problem:
>>>>>
>>>>> When joining the mesh with beacon interval set to 100
>>>>> both mesh and ap interface are coming up.
>>>>>
>>>>>> iw mesh0 mesh join my_mesh beacon-interval 100
>>>>>
>>>>> The default beacon interval is 1000 for mesh interfaces.
>>>>> It seems that QCA9880 is not working
>>>>> with different beacon intervals for ap + mesh.
>>>>
>>>> Good to hear that working. But mesh beacon interval 1000 which is
>>>> default value should work. Any mesh beacon intervals of multiple of AP
>>>> beacon intervals are supposed to work.
>>>>
>>>> (In other words, mesh beacon intervals that are not aligned by
>>>> multiple of AP beacon intervals won't work). These are valid for both
>>>> of QCA9880 and QCA4019 as far as I know.
>>>
>>> It would be nice if ath10k could print a warning if the beacon intervals
>>> are not compatible. Or is there a way to enforce the beacon interval
>>> with help of cfg80211 or mac80211?
>>
>> There is beacon interval checking in utility function
>> cfg80211_check_combinations() ->
>> cfg80211_iter_combinations() -> cfg80211_calculate_bi_data() for that.
>
> Nice, that looks useful. Thanks for the tip.
Initally was added by:
commit 0c317a02ca982ca093e71bf07cb562265ba40032
Author: Purushottam Kushwaha <pkushwah@qti.qualcomm.com>
Date: Wed Oct 12 18:26:51 2016 +0530
cfg80211: support virtual interfaces with different beacon intervals
And last touched by Johannes:
commit 4c8dea638c16141adb046fd2e0cab51dfe43650c
Author: Johannes Berg <johannes.berg@intel.com>
Date: Fri Oct 21 14:25:13 2016 +0200
cfg80211: validate beacon int as part of iface combinations
The last commit message has some info on how to use in case of AP/mesh.
>> However, it seems brcmfmac is the only user of that function according
>> to lxr (or elixir).
>
> git-grep says the same.
Yeah. git-grep has not sunk in my system yet ;-)
Regards,
Arend
prev parent reply other threads:[~2017-11-15 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e6b02c56-38c7-323e-2bc9-e2b4276b654c@tu-bs.de>
[not found] ` <cc8baced-bd74-5703-d885-6ec444eb62ce@candelatech.com>
[not found] ` <43bf6a27-be58-35e4-26fa-5e6b380353ac@bowerswilkins.com>
[not found] ` <7dc592a5-9381-f715-6ea7-0a8b8deee311@tu-bs.de>
[not found] ` <CADjYELwdUxEap_z=_HD4DS4FEQ2_2HP3w9cvDU-BTFLoOTDipg@mail.gmail.com>
[not found] ` <5c04c7fe-8cf8-ddd8-d6a7-f42629586a63@bowerswilkins.com>
[not found] ` <067d234a-59f0-4175-55af-9354617057b9@tu-bs.de>
[not found] ` <61192d3b-b4c7-f47e-2ff9-44e17595d6a9@bowerswilkins.com>
[not found] ` <fc1993f5-8b83-4e74-7866-2adcf318ff5f@tu-bs.de>
[not found] ` <03700343-7b5c-b21e-8b7b-2ac8c7d3258b@bowerswilkins.com>
2017-11-15 10:01 ` mesh point and ap mode on same interface Kalle Valo
2017-11-15 10:13 ` Arend van Spriel
2017-11-15 10:27 ` Kalle Valo
2017-11-15 10:36 ` Arend van Spriel [this message]
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=5A0C18C1.4000507@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=hannes.harms@tu-bs.de \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=peter.oh@bowerswilkins.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).