Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BFD0CC04EBD for ; Tue, 16 Oct 2018 08:09:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 669D020866 for ; Tue, 16 Oct 2018 08:09:26 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 669D020866 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726990AbeJPP6i (ORCPT ); Tue, 16 Oct 2018 11:58:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58160 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726944AbeJPP6i (ORCPT ); Tue, 16 Oct 2018 11:58:38 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D304D3082144; Tue, 16 Oct 2018 08:09:24 +0000 (UTC) Received: from localhost (unknown [10.43.2.63]) by smtp.corp.redhat.com (Postfix) with ESMTP id 66A60183DF; Tue, 16 Oct 2018 08:09:24 +0000 (UTC) Date: Tue, 16 Oct 2018 10:09:22 +0200 From: Stanislaw Gruszka To: Tom Psyborg Cc: linux-wireless@vger.kernel.org, Daniel Golle , Mathias Kresin , Felix Fietkau Subject: Re: [PATCH v4 4/8] rt2800: fix registers init for MT7620 Message-ID: <20181016080922.GB4158@redhat.com> References: <1539334591-9965-1-git-send-email-sgruszka@redhat.com> <1539334591-9965-5-git-send-email-sgruszka@redhat.com> <20181012113656.GB2118@redhat.com> <20181012120329.GD2118@redhat.com> <20181012122630.GB2668@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.42]); Tue, 16 Oct 2018 08:09:24 +0000 (UTC) Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Fri, Oct 12, 2018 at 02:41:41PM +0200, Tom Psyborg wrote: > On 12/10/2018, Stanislaw Gruszka wrote: > > On Fri, Oct 12, 2018 at 02:20:07PM +0200, Tom Psyborg wrote: > >> > On upstream tree where this patch is intended > >> > additional registers where never programmed as proper branch > >> > were never used, because of additional check in RT5390 branch. > >> > > >> > >> on my hardware additional registers were programmed in regardless of > >> redundant check. that why i opened whole thread on forum since i > >> couldn't understand how's that happening > > > > I don't understand how that possible either. > > i'd assume because device use external lna I have no idea how this could be related. But I think I found somewhat reasonable explenation where the problem is. I think below code : if (a || b || c) { CODE1(); } else if (c) { CODE2(); } can not be deterministic and can be compiled differently depending on compiler version and used options. Sometimes it could result in this if (a || b || c) { CODE1(); } and sometimes in this: if (a || b) { CODE1(); } else if (c) { CODE2(); } So that would explain the problems you see. And indeed patch could cause regression on systems where second variant of initalizing RT6352 registers was used. Thanks Stanislaw