From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Tom Psyborg <pozega.tomislav@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Daniel Golle <daniel@makrotopia.org>,
Mathias Kresin <dev@kresin.me>, Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH v4 4/8] rt2800: fix registers init for MT7620
Date: Tue, 16 Oct 2018 10:09:22 +0200 [thread overview]
Message-ID: <20181016080922.GB4158@redhat.com> (raw)
In-Reply-To: <CAKR_QVLtJGzpBuz-BBi5yzFPoTUnadDdEXcwnR4XrB3DuWchjQ@mail.gmail.com>
On Fri, Oct 12, 2018 at 02:41:41PM +0200, Tom Psyborg wrote:
> On 12/10/2018, Stanislaw Gruszka <sgruszka@redhat.com> 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
next prev parent reply other threads:[~2018-10-16 8:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 8:56 [PATCH v4 0/8] rt2800: register programing tweaks and clean ups Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 1/8] rt2x00: remove unneeded check Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 2/8] rt2x00: remove confusing AGC register Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 3/8] rt2x00: update TX_SW_CFG2 value Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 4/8] rt2800: fix registers init for MT7620 Stanislaw Gruszka
2018-10-12 10:48 ` Tom Psyborg
2018-10-12 11:36 ` Stanislaw Gruszka
2018-10-12 11:51 ` Tom Psyborg
2018-10-12 12:03 ` Stanislaw Gruszka
2018-10-12 12:20 ` Tom Psyborg
2018-10-12 12:26 ` Stanislaw Gruszka
2018-10-12 12:41 ` Tom Psyborg
2018-10-16 8:09 ` Stanislaw Gruszka [this message]
2018-10-16 11:19 ` Felix Fietkau
2018-10-16 11:21 ` Stanislaw Gruszka
2018-10-16 11:25 ` Felix Fietkau
2018-10-16 11:32 ` Tom Psyborg
2018-10-16 15:49 ` Stanislaw Gruszka
2018-10-17 13:25 ` Tom Psyborg
2018-10-19 9:00 ` Stanislaw Gruszka
2018-10-19 14:21 ` Tom Psyborg
2018-10-20 9:44 ` Stanislaw Gruszka
2018-10-18 15:51 ` Tom Psyborg
2018-10-16 8:11 ` Stanislaw Gruszka
2018-10-16 10:38 ` Daniel Golle
2018-10-13 9:46 ` Kalle Valo
2018-10-16 8:02 ` Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 5/8] rt2800: enable TX_PIN_CFG_LNA_PE_ bits per band Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 6/8] rt2800: enable TX_PIN_CFG_RFRX_EN only for MT7620 Stanislaw Gruszka
2018-10-12 10:52 ` Tom Psyborg
2018-10-12 11:38 ` Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 7/8] rt2800: remove unneeded RT6352 check Stanislaw Gruszka
2018-10-12 8:56 ` [PATCH v4 8/8] rt2800: comment and simplify AGC init for RT6352 Stanislaw Gruszka
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=20181016080922.GB4158@redhat.com \
--to=sgruszka@redhat.com \
--cc=daniel@makrotopia.org \
--cc=dev@kresin.me \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=pozega.tomislav@gmail.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).