From: Dmitry Osipenko <digetx@gmail.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Wright Feng <wright.feng@cypress.com>,
Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com, netdev@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] brcmfmac: increase F2 watermark for BCM4329
Date: Thu, 27 Aug 2020 09:13:00 +0300 [thread overview]
Message-ID: <ba942825-e165-68f1-00d1-81cc66ff518b@gmail.com> (raw)
In-Reply-To: <20200827060441.15487-2-digetx@gmail.com>
27.08.2020 09:04, Dmitry Osipenko пишет:
> This patch fixes SDHCI CRC errors during of RX throughput testing on
> BCM4329 chip if SDIO BUS is clocked above 25MHz. In particular the
> checksum problem is observed on NVIDIA Tegra20 SoCs. The good watermark
> value is borrowed from downstream BCMDHD driver and it's matching to the
> value that is already used for the BCM4339 chip, hence let's re-use it
> for BCM4329.
>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
I accidentally missed to add the r-b from Arend that he gave to the v1:
Reviewed-by: Arend van Spriel <arend.vanspriel@broadcom.com>
next prev parent reply other threads:[~2020-08-27 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 6:04 [PATCH v2 0/4] Fixes and improvements for brcmfmac driver Dmitry Osipenko
2020-08-27 6:04 ` [PATCH v2 1/4] brcmfmac: increase F2 watermark for BCM4329 Dmitry Osipenko
2020-08-27 6:13 ` Dmitry Osipenko [this message]
2020-08-27 6:04 ` [PATCH v2 2/4] brcmfmac: drop unnecessary "fallthrough" comments Dmitry Osipenko
2020-08-27 6:23 ` Gustavo A. R. Silva
2020-08-27 6:20 ` Dmitry Osipenko
2020-08-27 6:04 ` [PATCH v2 3/4] brcmfmac: drop chip id from debug messages Dmitry Osipenko
2020-08-27 6:04 ` [PATCH v2 4/4] brcmfmac: set F2 SDIO block size to 128 bytes for BCM4329 Dmitry Osipenko
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=ba942825-e165-68f1-00d1-81cc66ff518b@gmail.com \
--to=digetx@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@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=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).