From: Kalle Valo <kvalo@codeaurora.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: linux-wireless@vger.kernel.org, "Felix Fietkau" <nbd@nbd.name>,
"Daniel Golle" <daniel@makrotopia.org>,
"Tomislav Požega" <pozega.tomislav@gmail.com>,
"Mathias Kresin" <dev@kresin.me>,
"Sergey Maranchuk" <slav0nic0@gmail.com>
Subject: Re: [PATCH 5.3] Revert "rt2800: enable TX_PIN_CFG_LNA_PE_ bits per band"
Date: Tue, 3 Sep 2019 13:52:47 +0000 (UTC) [thread overview]
Message-ID: <20190903135248.E1C2760E3F@smtp.codeaurora.org> (raw)
In-Reply-To: <1567078199-3645-1-git-send-email-sgruszka@redhat.com>
Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> This reverts commit 9ad3b55654455258a9463384edb40077439d879f.
>
> As reported by Sergey:
>
> "I got some problem after upgrade kernel to 5.2 version (debian testing
> linux-image-5.2.0-2-amd64). 5Ghz client stopped to see AP.
> Some tests with 1metre distance between client-AP: 2.4Ghz -22dBm, for
> 5Ghz - 53dBm !, for longer distance (8m + walls) 2.4 - 61dBm, 5Ghz not
> visible."
>
> It was identified that rx signal level degradation was caused by
> 9ad3b5565445 ("rt2800: enable TX_PIN_CFG_LNA_PE_ bits per band").
> So revert this commit.
>
> Cc: <stable@vger.kernel.org> # v5.1+
> Reported-and-tested-by: Sergey Maranchuk <slav0nic0@gmail.com>
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Patch applied to wireless-drivers.git, thanks.
13fa451568ab Revert "rt2800: enable TX_PIN_CFG_LNA_PE_ bits per band"
--
https://patchwork.kernel.org/patch/11121089/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2019-09-03 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 11:29 [PATCH 5.3] Revert "rt2800: enable TX_PIN_CFG_LNA_PE_ bits per band" Stanislaw Gruszka
2019-09-03 13:52 ` Kalle Valo [this message]
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=20190903135248.E1C2760E3F@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=daniel@makrotopia.org \
--cc=dev@kresin.me \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=pozega.tomislav@gmail.com \
--cc=sgruszka@redhat.com \
--cc=slav0nic0@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