Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp1657024ybc; Wed, 20 Nov 2019 01:58:23 -0800 (PST) X-Google-Smtp-Source: APXvYqwJEXu5+nSXl6yTYvl6RWU460TmI4LPrDXsVlocapTrA9Ya7x58t/I/447/eYjh19f7fZR2 X-Received: by 2002:a17:906:5c0d:: with SMTP id e13mr4108252ejq.82.1574243903686; Wed, 20 Nov 2019 01:58:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574243903; cv=none; d=google.com; s=arc-20160816; b=z35OwcV8qYG+B8Jz1uHMQw60ExXVB8/J7xzbACgQ2/rYO1rcSDpz0c5+kT6Yyd20p3 ObdVlIzHg9sUFjS0bnlwfjIUxfMLjPLbcqVjMt2JZwIAzt4kapbddegGV5jo0WmhNKWK IjDF9WNclvrJKTqHrbkWcoCWjYB1+xXyvpL9QdJ4iVQpUgQ5a8xhyzbdcszJepcPGNGO StZfUsFXUdB8TPJUOhKbV3YC/Skgf7szsFzsr9/aTSpZZzgjB/nTbZmXpznPX0MDar0i y6WUvOlUojcgZWmX7tCAtFaRX3auMysBNAOzEipnyrnVmZhNAqqM4AlzLzQkjikKzq/s AQQQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-disposition :content-transfer-encoding:user-agent:in-reply-to:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=4P8AxkoeMgsJhci2AUBreMbcjF9DmmicMU49Qec3kgY=; b=yDRnIPFore4joS/iBVPk8B3eL/P3Ml7szIUqKapqVo7Gku+FDzQ1Mnb4VWPmyuZObT mtPKWbMo5A25d+rCnSuucz32e0jTavXMRHNl03GwGW4+/sWv2I7dOqgQXTy25/SXPApZ eKLw/QGsJ9SZhOC0uiszEcJMyLVjN0fBweZ7hx63fSFtAvlju5Er6HvD79Ki8PQ14PjT JPAJnRpN0qI6NDTjD5q8+d65y6PVSdTo3ppLVaJLiuH1xeMuwH6NnM+nDVELsCCDtp3A gCOk07TgziUumE0QlJrRC2R4zP3TSez6xTL7bAvaDM2bKfxO5Pf/qe6ZuzpNom/QLJ36 0fSg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=DVjdeVgb; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p21si17922470edc.305.2019.11.20.01.57.44; Wed, 20 Nov 2019 01:58:23 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=DVjdeVgb; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728255AbfKTJ2O (ORCPT + 99 others); Wed, 20 Nov 2019 04:28:14 -0500 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:37994 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726762AbfKTJ2O (ORCPT ); Wed, 20 Nov 2019 04:28:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1574242093; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4P8AxkoeMgsJhci2AUBreMbcjF9DmmicMU49Qec3kgY=; b=DVjdeVgbcsZa2NHWHKijNu8haZ6M4dTyIfRBAyrKyuXhe8+b8UEt/YsieCIwdilj/MwQ34 1aSqE2C0zdwK8rYJDEFCKAU3Fb1l3KNcHA4A+sFBSD/hz8bIcAE00Wr9lkJLCV986c/Gbw 1AUo8n5leAVSRcCEqKhLI4ZyI0CbNHs= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-125-IJa3Lri6M_C8ggSOWhcfwQ-1; Wed, 20 Nov 2019 04:28:10 -0500 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 4A244107ACC5; Wed, 20 Nov 2019 09:28:09 +0000 (UTC) Received: from localhost (unknown [10.40.205.83]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0869D60FFB; Wed, 20 Nov 2019 09:28:05 +0000 (UTC) Date: Wed, 20 Nov 2019 10:28:04 +0100 From: Stanislaw Gruszka To: Markus Theil Cc: nbd@nbd.name, linux-wireless@vger.kernel.org, lorenzo.bianconi@redhat.com Subject: Re: [PATCH v6 2/5] mt76: mt76x02: split beaconing Message-ID: <20191120092803.GA517@redhat.com> References: <20191119154746.20821-1-markus.theil@tu-ilmenau.de> <20191119154746.20821-3-markus.theil@tu-ilmenau.de> MIME-Version: 1.0 In-Reply-To: <20191119154746.20821-3-markus.theil@tu-ilmenau.de> User-Agent: Mutt/1.8.3 (2017-05-23) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-MC-Unique: IJa3Lri6M_C8ggSOWhcfwQ-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Tue, Nov 19, 2019 at 04:47:43PM +0100, Markus Theil wrote: > Sending beacons to the hardware always happens in batches. In order to > speed up beacon processing on usb devices, this patch splits out common > code an calls it only once (mt76x02_mac_set_beacon_prepare, > mt76x02_mac_set_beacon_finish). Making this split breaks beacon > enabling/disabling per vif. This is fixed by adding a call to set the > bypass mask, if beaconing should be disabled for a vif. Otherwise the > beacon is send after the next beacon interval. >=20 > The code is also adapted for the mmio part of the driver, but should not > have any performance implication there. >=20 > Signed-off-by: Markus Theil > --- > .../wireless/mediatek/mt76/mt76x02_beacon.c | 44 +++++++------------ > .../net/wireless/mediatek/mt76/mt76x02_mac.h | 1 + > .../net/wireless/mediatek/mt76/mt76x02_mmio.c | 5 +++ > .../wireless/mediatek/mt76/mt76x02_usb_core.c | 5 +++ > 4 files changed, 26 insertions(+), 29 deletions(-) >=20 > diff --git a/drivers/net/wireless/mediatek/mt76/mt76x02_beacon.c b/driver= s/net/wireless/mediatek/mt76/mt76x02_beacon.c > index 403866496640..09013adae854 100644 > --- a/drivers/net/wireless/mediatek/mt76/mt76x02_beacon.c > +++ b/drivers/net/wireless/mediatek/mt76/mt76x02_beacon.c > @@ -47,10 +47,6 @@ __mt76x02_mac_set_beacon(struct mt76x02_dev *dev, u8 b= cn_idx, > =09int beacon_len =3D dev->beacon_ops->slot_size; > =09int beacon_addr =3D MT_BEACON_BASE + (beacon_len * bcn_idx); > =09int ret =3D 0; > -=09int i; > - > -=09/* Prevent corrupt transmissions during update */ > -=09mt76_set(dev, MT_BCN_BYPASS_MASK, BIT(bcn_idx)); > =20 > =09if (skb) { > =09=09ret =3D mt76x02_write_beacon(dev, beacon_addr, skb); > @@ -60,41 +56,30 @@ __mt76x02_mac_set_beacon(struct mt76x02_dev *dev, u8 = bcn_idx, > =09=09dev->beacon_data_mask &=3D ~BIT(bcn_idx); > =09} > =20 > -=09mt76_wr(dev, MT_BCN_BYPASS_MASK, 0xff00 | ~dev->beacon_data_mask); > - > =09return ret; > } > =20 > -int mt76x02_mac_set_beacon(struct mt76x02_dev *dev, u8 vif_idx, > -=09=09=09 struct sk_buff *skb) > +void mt76x02_mac_set_beacon_finish(struct mt76x02_dev *dev) > { > -=09bool force_update =3D false; > -=09int bcn_idx =3D 0; > =09int i; > +=09int bcn_idx =3D 0; > =20 > -=09for (i =3D 0; i < ARRAY_SIZE(dev->beacons); i++) { > -=09=09if (vif_idx =3D=3D i) { > -=09=09=09force_update =3D !!dev->beacons[i] ^ !!skb; > -=09=09=09dev_kfree_skb(dev->beacons[i]); > -=09=09=09dev->beacons[i] =3D skb; > -=09=09=09__mt76x02_mac_set_beacon(dev, bcn_idx, skb); > -=09=09} else if (force_update && dev->beacons[i]) { > -=09=09=09__mt76x02_mac_set_beacon(dev, bcn_idx, > -=09=09=09=09=09=09 dev->beacons[i]); > -=09=09} > - > +=09for (i =3D 0; i < hweight8(dev->mt76.beacon_mask); ++i) > =09=09bcn_idx +=3D !!dev->beacons[i]; This looks wrong since we do not calculate all beacons, only=20 up to hweight8(dev->mt76.beacon_mask). But since we need to calculate number of all beacons we can just use hweight8(dev->mt76.beacon_mask) directly. > -=09} > - > -=09for (i =3D bcn_idx; i < ARRAY_SIZE(dev->beacons); i++) { > -=09=09if (!(dev->beacon_data_mask & BIT(i))) > -=09=09=09break; > - > -=09=09__mt76x02_mac_set_beacon(dev, i, NULL); > -=09} > =20 > =09mt76_rmw_field(dev, MT_MAC_BSSID_DW1, MT_MAC_BSSID_DW1_MBEACON_N, > =09=09 bcn_idx - 1); > + > +=09mt76_wr(dev, MT_BCN_BYPASS_MASK, 0xff00 | ~dev->beacon_data_mask); I'm not sure if this is correct for multi bss. In MT7620 manual BCM_BAYPASS_MASK is described as below: " Directly bypasses the Tx Beacon frame with the specified=20 Beacon number. Bit0=3DNth Beacon, bit1=3D(N- 1)th Beacon,... etc. N is the number of Beacons defined in the MULTI_BCN_NUM field in the=20 MAC_BSSID_DW1(offset: 0x1014) register. 0: Disable 1: Enable " Assuming manual is correct (it could be wrong) bypass mask should be calculated differently. Stanislaw