From: Dmitry Osipenko <digetx@gmail.com>
To: Wright Feng <wright.feng@cypress.com>,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, brcm80211-dev-list@broadcom.com,
brcm80211-dev-list@cypress.com,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Amar Shankar <amsr@cypress.com>,
Jia-Shyr Chuang <joseph.chuang@cypress.com>
Subject: Re: [PATCH V2 3/6] brcmfmac: reserve 2 credits for host tx control path
Date: Fri, 14 Aug 2020 00:30:37 +0300 [thread overview]
Message-ID: <f4031cd9-edf8-9c7a-90fa-95cac370a656@gmail.com> (raw)
In-Reply-To: <8edbb3bb-a28b-6dae-1318-68c4b0478ad7@cypress.com>
13.08.2020 06:03, Wright Feng пишет:
..
>> Wright, thank you very much for the patch! It fixes the problem!
>>
>> Tested-by: Dmitry Osipenko <digetx@gmail.com>
>>
>> The 4329/3 is indeed an older chip, but it's also an "old" device (Acer
>> A500 tablet from 2011/12) that I'm using. Upstream v5.9 kernel just got
>> support for the A500. There are quite a lot of other older devices with
>> 4329/3 in a wild that are still very usable if user can wipe off ancient
>> Android and put a modern Linux distro on them. Today that A500 tablet is
>> still rocking hard running a modern upstream kernel, opensource drivers
>> and KDE Plasma 5. The 15Mbit is a good enough speed for a lot of things,
>> but of course 40Mbit will be better. Would be great if you could try to
>> help with improving the speed :) Please feel free to contact me at any
>> time if you'll have patches to try!
>>
> Dmitry,
> Thanks for the verification. The patch will be submitted to upstream
> within two days.
> And with regards to low THP problem on Acer A500 tablet, I will create
> another mail thread to discuss with you.
Thank you!
next prev parent reply other threads:[~2020-08-13 21:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 15:21 [PATCH V2 0/6] brcmfmac: flow control and p2p fix series Chi-Hsien Lin
2020-06-10 15:21 ` [PATCH V2 1/6] brcmfmac: allow credit borrowing for all access categories Chi-Hsien Lin
2020-07-14 9:47 ` Kalle Valo
2020-06-10 15:21 ` [PATCH V2 2/6] brcmfmac: increase message buffer size for control packets Chi-Hsien Lin
2020-06-10 15:21 ` [PATCH V2 3/6] brcmfmac: reserve 2 credits for host tx control path Chi-Hsien Lin
2020-08-03 16:27 ` Dmitry Osipenko
2020-08-04 11:08 ` Kalle Valo
2020-08-04 15:53 ` Dmitry Osipenko
2020-08-04 17:22 ` Kalle Valo
2020-08-05 8:24 ` Chi-Hsien Lin
2020-08-05 14:01 ` Dmitry Osipenko
2020-08-11 8:35 ` Wright Feng
2020-08-11 14:54 ` Dmitry Osipenko
2020-08-12 4:03 ` Wright Feng
2020-08-12 14:22 ` Dmitry Osipenko
2020-08-13 3:03 ` Wright Feng
2020-08-13 21:30 ` Dmitry Osipenko [this message]
2020-06-10 15:21 ` [PATCH V2 4/6] brcmfmac: update tx status flags to sync with firmware Chi-Hsien Lin
2020-06-10 15:21 ` [PATCH V2 5/6] brcmfmac: fix throughput zero stalls on PM 1 mode due to credit map Chi-Hsien Lin
2020-06-10 15:21 ` [PATCH V2 6/6] brcmfmac: initialize the requested dwell time Chi-Hsien Lin
2020-06-22 15:04 ` Chi-Hsien Lin
2020-07-14 9:30 ` Kalle Valo
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=f4031cd9-edf8-9c7a-90fa-95cac370a656@gmail.com \
--to=digetx@gmail.com \
--cc=amsr@cypress.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=joseph.chuang@cypress.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@cypress.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).