From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Chi-Hsien Lin <Chi-Hsien.Lin@cypress.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "brcm80211-dev-list@broadcom.com"
<brcm80211-dev-list@broadcom.com>,
brcm80211-dev-list <brcm80211-dev-list@cypress.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Wright Feng <Wright.Feng@cypress.com>,
Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [PATCH 02/11] brcmfmac: set F2 watermark to 256 for 4373
Date: Thu, 8 Nov 2018 12:53:13 +0100 [thread overview]
Message-ID: <702baa16-c2ba-eab2-5aca-a684ca9505d0@broadcom.com> (raw)
In-Reply-To: <1541476188-75475-3-git-send-email-chi-hsien.lin@cypress.com>
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
> From: Wright Feng <wright.feng@cypress.com>
>
> We got SDIO_CRC_ERROR with 4373 on SDR104 when doing bi-directional
> throughput test. Enable watermark to 256 to guarantee the operation
> stability.
Maybe it would be better to clarify the unit of the watermark. Here you
use bytes, but in the register it needs number of words (word being 4
bytes). So is this really only applicable to 4373? I have had question
about SDIO crc errors before for other chips. Other than that....
Reviewed-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> Signed-off-by: Wright Feng <wright.feng@cypress.com>
> Signed-off-by: Chi-Hsien Lin <chi-hsien.lin@cypress.com>
> ---
> .../wireless/broadcom/brcm80211/brcmfmac/sdio.c | 25 ++++++++++++++++++++--
> 1 file changed, 23 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
> index b2e1ab5adb64..541d54661c9e 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
> @@ -49,6 +49,9 @@
> #define DCMD_RESP_TIMEOUT msecs_to_jiffies(2500)
> #define CTL_DONE_TIMEOUT msecs_to_jiffies(2500)
Mention the unit so:
+/* watermark expressed in number of words */
> +#define DEFAULT_F2_WATERMARK 0x8
> +#define CY_4373_F2_WATERMARK 0x40
or
+#define DEFAULT_F2_WATERMARK (32 >> 2)
+@define CY_4373_F2_WATERMARK (256 >> 2)
next prev parent reply other threads:[~2018-11-08 11:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 3:50 [PATCH 00/11] chip related changes Chi-Hsien Lin
2018-11-06 3:50 ` [PATCH 01/11] brcmfmac: add 4354 raw pcie device id Chi-Hsien Lin
2018-11-08 11:52 ` Arend van Spriel
2018-11-06 3:50 ` [PATCH 02/11] brcmfmac: set F2 watermark to 256 for 4373 Chi-Hsien Lin
2018-11-08 11:53 ` Arend van Spriel [this message]
2018-11-06 3:50 ` [PATCH 03/11] brcmfmac: set SDIO F1 MesBusyCtrl for CYW4373 Chi-Hsien Lin
2018-11-08 11:53 ` Arend van Spriel
2018-11-09 7:34 ` Chi-Hsien Lin
2018-11-09 12:20 ` Arend van Spriel
2018-11-06 3:50 ` [PATCH 04/11] brcmfmac: add support for CYW43012 SDIO chipset Chi-Hsien Lin
2018-11-08 11:53 ` Arend van Spriel
2018-11-06 3:50 ` [PATCH 05/11] brcmfmac: allow GCI core enumuration Chi-Hsien Lin
2018-11-08 11:53 ` Arend van Spriel
2018-11-06 3:50 ` [PATCH 06/11] brcmfmac: saverestore support changes for 43012 Chi-Hsien Lin
2018-11-08 11:53 ` Arend van Spriel
2018-11-06 3:50 ` [PATCH 07/11] brcmfmac: update 43012 F2 watermark setting to fix DMA Error during UDP RX Traffic Chi-Hsien Lin
2018-11-08 11:53 ` Arend van Spriel
2018-11-06 3:50 ` [PATCH 08/11] brcmfmac: 4373 save-restore support Chi-Hsien Lin
2018-11-08 11:54 ` Arend van Spriel
2018-11-06 3:50 ` [PATCH 09/11] brcmfmac: disable command decode in sdio_aos for 43012/4339/4345 Chi-Hsien Lin
2018-11-08 11:54 ` Arend van Spriel
2018-11-06 3:50 ` [PATCH 10/11] brcmfmac: disable command decode in sdio_aos for 4354 Chi-Hsien Lin
2018-11-08 11:55 ` Arend van Spriel
2018-11-06 3:50 ` [PATCH 11/11] brcmfmac: disable command decode in sdio_aos for 4373 Chi-Hsien Lin
2018-11-08 11:55 ` Arend van Spriel
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=702baa16-c2ba-eab2-5aca-a684ca9505d0@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=Chi-Hsien.Lin@cypress.com \
--cc=Wright.Feng@cypress.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.