From: Markus Theil <markus.theil@tu-ilmenau.de>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: nbd@nbd.name, linux-wireless@vger.kernel.org,
lorenzo.bianconi@redhat.com
Subject: Re: [PATCH v8 2/6] mt76: mt76x02: split beaconing
Date: Mon, 25 Nov 2019 15:07:59 +0100 [thread overview]
Message-ID: <ec1b9623-2aa1-27c7-abcd-2b39e0d25a0c@tu-ilmenau.de> (raw)
In-Reply-To: <20191125130014.GB28102@redhat.com>
On 11/25/19 2:00 PM, Stanislaw Gruszka wrote:
> On Thu, Nov 21, 2019 at 06:59:57PM +0100, Markus Theil wrote:
>> +void mt76x02_mac_set_beacon_finish(struct mt76x02_dev *dev)
>> +{
>> + mt76_wr(dev, MT_BCN_BYPASS_MASK,
>> + 0xff00 | ~bitrev8(dev->beacon_data_mask));
> Since you arrange beacon slots continues starting from 0
> (i.e. 0,1,2 instead of "random" vif_idx values like 0,4,6),
> I think it would make sense to keep
> MT_MAC_BSSID_DW1_MBEACON_N = bcn_idx - 1 and set mask unchanged.
>
> But no strong opinion here, code with bitrev8 looks fine too.
I'd like to keep the bitrev8 code, as it saves a copy over usb for usb
devices, if MT_MAC_BSSID_DW_BEACON_N is kept constant.
bitrev8 should be a rather cheap operation compared to a copy over some
form of bus.
>> static void mt76x02u_beacon_enable(struct mt76x02_dev *dev, bool en)
>> {
>> - int i;
>> -
>> if (WARN_ON_ONCE(!dev->mt76.beacon_int))
>> return;
>>
>> if (en) {
>> mt76x02u_start_pre_tbtt_timer(dev);
>> - } else {
>> - /* Timer is already stopped, only clean up
>> - * PS buffered frames if any.
>> - */
> Please keep comment that timer is already disabled and
> nothing else is needed.
>
> Stanislaw
>
Ok, will keep it in an updated version.
Markus
next prev parent reply other threads:[~2019-11-25 14:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 17:59 [PATCH v8 0/6] mt76: channel switch support for USB devices Markus Theil
2019-11-21 17:59 ` [PATCH v8 1/6] mt76: mt76x02: ommit beacon slot clearing Markus Theil
2019-11-21 17:59 ` [PATCH v8 2/6] mt76: mt76x02: split beaconing Markus Theil
2019-11-25 13:00 ` Stanislaw Gruszka
2019-11-25 14:07 ` Markus Theil [this message]
2019-11-25 16:59 ` Stanislaw Gruszka
2019-11-25 17:12 ` Felix Fietkau
2019-11-25 17:32 ` Stanislaw Gruszka
2019-11-26 10:44 ` Stanislaw Gruszka
2019-11-21 17:59 ` [PATCH v8 3/6] mt76: mt76x02: add check for invalid vif idx Markus Theil
2019-11-24 3:30 ` kbuild test robot
2019-11-21 17:59 ` [PATCH v8 4/6] mt76: mt76x02: remove a copy call for usb speedup Markus Theil
2019-11-25 12:49 ` Stanislaw Gruszka
2019-11-21 18:00 ` [PATCH v8 5/6] mt76: speed up usb bulk copy Markus Theil
2019-11-21 18:00 ` [PATCH v8 6/6] mt76: mt76x02: add channel switch support for usb interfaces Markus Theil
2019-11-25 13:04 ` Stanislaw Gruszka
2019-11-25 14:51 ` Markus Theil
2019-11-25 15:32 ` Markus Theil
2019-11-25 17:02 ` Stanislaw Gruszka
2019-11-25 18:30 ` Markus Theil
2019-11-25 18:40 ` Markus Theil
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=ec1b9623-2aa1-27c7-abcd-2b39e0d25a0c@tu-ilmenau.de \
--to=markus.theil@tu-ilmenau.de \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=sgruszka@redhat.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).