Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp596744yba; Wed, 15 May 2019 06:49:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqxVnnnazK6YHM7xo6GH/jdcCC07a0tprq54NSGq4BB9X8xmcZOT8h2EwE6GOYFPFElFHNRQ X-Received: by 2002:a63:1316:: with SMTP id i22mr44116844pgl.274.1557928176954; Wed, 15 May 2019 06:49:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557928176; cv=none; d=google.com; s=arc-20160816; b=HPRDB+PiiYYYDKRkqQig2JHEVqJVD+dGmjXIDInqmBZcb5iSDR6TEMjgzBE+uS3sYe uVeOWkRv40230+ERhhP31SsCnKEs8uHcZsuSLZsyJTROpWBxhVlPd3zF8hof/N4cZoA4 dJvuJ37p9Jppgwj+z4M71CECx1LnvKGXeYu/M8ioOcl7adOFMtTp+B0IOWSZX7DP6EUg YxDzx3201/pY/m12kngeN1QN/6wKtn4wDwE+Pcka+UvUnH1VJwK8o78w9Vpy+koeUjzQ ZmEnBzcFzTuAVDlLuyNrR/xQSpYtYl1ReUt7ryb2uhNIqUzbyNXbEJ4YZxuSZXb2JTk9 Cd2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=yctOM3PXB8vEctpSe1xSF9vcILPTeYiyQum/5bJEP1o=; b=pIED8/vDiFDmar7jbvT/S81pGo0Y1N85SIVpJ+5UzNv1lAhsXRdA+Ovo72Hnm1b9hB YFh53XRjbDBNldOL2NtPccVrnZjuAlbdbHkt6R/BrRbkmANjKydw7U6Ji+Q7AzsetRNG LpOh9hkUx5ZZNCCuikwoUisMb0webn2HMGSXOpcaeAyqT+IIeRXQ3C6m2knVfxkJ3NDs 00c0P9QSnhLrdmxZpcjDk7IVFzKEsorMkGvwV32C3E1f/SB6Dh17bHvJyTg3b6mdV77Q NpXXiwR6OYuUtxSsmvKgfcbE1C8MMBr2JRL+AZUjS/S4vc5p7SqkXzSyD9jFu2V9xVyr A2Cg== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (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 l12si1943153pgq.351.2019.05.15.06.49.15; Wed, 15 May 2019 06:49:36 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728136AbfEONse (ORCPT + 99 others); Wed, 15 May 2019 09:48:34 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41226 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728068AbfEONsd (ORCPT ); Wed, 15 May 2019 09:48:33 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id AA3063082B5F; Wed, 15 May 2019 13:48:33 +0000 (UTC) Received: from localhost (ovpn-204-245.brq.redhat.com [10.40.204.245]) by smtp.corp.redhat.com (Postfix) with ESMTP id 946FD5C28E; Wed, 15 May 2019 13:48:30 +0000 (UTC) Date: Wed, 15 May 2019 15:48:29 +0200 From: Stanislaw Gruszka To: Lorenzo Bianconi Cc: Kalle Valo , nbd@nbd.name, lorenzo.bianconi@redhat.com, linux-wireless@vger.kernel.org Subject: Re: [PATCH] mt76: mt7603: add debugfs knob to enable/disable edcca Message-ID: <20190515134828.GA2992@redhat.com> References: <20190513084127.GA3127@localhost.localdomain> <20190513094837.GB15694@redhat.com> <20190515093333.GA2333@redhat.com> <20190515094354.GA30757@localhost.localdomain> <20190515095440.GB3407@redhat.com> <20190515100343.GB30757@localhost.localdomain> <20190515103309.GA15134@redhat.com> <20190515111348.GC30757@localhost.localdomain> <20190515114615.GB15134@redhat.com> <20190515120741.GD30757@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190515120741.GD30757@localhost.localdomain> User-Agent: Mutt/1.11.3 (2019-02-01) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.45]); Wed, 15 May 2019 13:48:33 +0000 (UTC) Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Wed, May 15, 2019 at 02:07:42PM +0200, Lorenzo Bianconi wrote: > > On Wed, May 15, 2019 at 01:13:49PM +0200, Lorenzo Bianconi wrote: > > > > On Wed, May 15, 2019 at 12:03:44PM +0200, Lorenzo Bianconi wrote: > > > > > > On Wed, May 15, 2019 at 11:43:55AM +0200, Lorenzo Bianconi wrote: > > > > > > > > On Mon, May 13, 2019 at 11:48:37AM +0200, Stanislaw Gruszka wrote: > > > > > > > > > On Mon, May 13, 2019 at 10:41:28AM +0200, Lorenzo Bianconi wrote: > > > > > > > > > > > Lorenzo Bianconi writes: > > > > > > > > > > > > > > > > > > > > > > > Introduce a knob in mt7603 debugfs in order to enable/disable > > > > > > > > > > > > edcca processing > > > > > > > > > > > > > > > > > > > > > > > > Signed-off-by: Lorenzo Bianconi > > > > > > > > > > > > > > > > > > > > > > It's good to explain what edcca does and how the file is used supposed > > > > > > > > > > > to be used. In other words, have a small introduction for the user. > > > > > > > > > > > > > > > > > > > > Hi Kalle, > > > > > > > > > > > > > > > > > > > > edcca is used for adjusting energy detect based on CCA thresholds. > > > > > > > > > > The code was already there so I just reported the acronym. > > > > > > > > > > > > > > > > > > What for it is needed ? > > > > > > > > > > > > > > > > Care to comment why EDCCA is needed at all ? > > > > > > > > > > > > > > > > Taking that debugfs file that enable it is read-only, it looks like > > > > > > > > feature that nobody needs nor tests. > > > > > > > > > > > > > > already fixed in v2 > > > > > > > https://patchwork.kernel.org/patch/10940645/ > > > > > > > > > > > > I'm aware of this patch and other one for mt76x02. But so far in the > > > > > > sources EDCCA is disabled for mt76x02 without possibility to enable it > > > > > > (and this permission file issue was pointed by Kalle during review, not > > > > > > by someone who want to test EDCCA). So again, what for EDCCA is needed ? > > > > > > > > > > As I have already written in a previous email, ED/CCA is used to control tx power > > > > > according to the CCA MIB counters (e.g do not transmit if the channel busy time > > > > > is higher than 90% for given amount of time in a row). I guess it is required > > > > > by ETSI regulatory. > > > > But what is user case for that, i.e. who need this (it wasn't implemented in > > > > mt76x2 since you added it on Dec 2018). What will happen if it will be removed? > > > > > > > > > Regarding file permission for mt76x02 debugfs edcca node is a typo. > > > > Typo or not, effectively disable the feature and show nobody is > > > > testing it. > > > > > > > > The reason I'm asking is that seems EDCCA is the main reason to > > > > implement watchod for mt76x2, it wasn't necessary to have a watchdog > > > > as seems devices did not hung before EDCCA was added. > > > > > > IIRC I added the first watchdog implementation to fix tx hangs that occur > > > under heavy load even using FCC regulatory (so when EDCCA processing is > > > disabled) > > > > There was changes in various registers programming introduced by EDCCA > > support, even with EDCCA disabled. It's rally not convenient that > > watchdog and EDCCA are not related, since you added tx hung watchdog > > 2 weeks after adding EDCCA. > > > > You can look at this report: > > https://github.com/openwrt/mt76/issues/246 > > Before mt76x2e worked without hungs & watchodg. Now, even with EDCCA > > disabled watchdog and HW restarts are required to fix hungs on runtime. > > Tx hangs occur in very particular conditions (e.g 200Mbps bidirectional > traffic) and moreover they do not always occur so I am not convinced they > are always EDCCA related and so I am not confident to remove the watchdog I'm not opting for watchdog removal, but for full EDCCA removal. Apparently nobody cares, if it can be enabled or not. Stanislaw