From: Kalle Valo <kvalo@codeaurora.org>
To: Wright Feng <Wright.Feng@cypress.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Wright Feng <Wright.Feng@cypress.com>,
"arend.vanspriel@broadcom.com" <arend.vanspriel@broadcom.com>,
"franky.lin@broadcom.com" <franky.lin@broadcom.com>,
"hante.meuleman@broadcom.com" <hante.meuleman@broadcom.com>,
Chi-Hsien Lin <Chi-Hsien.Lin@cypress.com>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>
Subject: Re: [PATCH v3 1/3] brcmfmac: add credit numbers updating support
Date: Thu, 29 Nov 2018 15:43:32 +0000 (UTC) [thread overview]
Message-ID: <20181129154332.A81A46020A@smtp.codeaurora.org> (raw)
In-Reply-To: <20181105055137.13333-2-wright.feng@cypress.com>
Wright Feng <Wright.Feng@cypress.com> wrote:
> The credit numbers are static and tunable per chip in firmware side.
> However the credit number may be changed that is based on packet pool
> length and will send BRCMF_E_FIFO_CREDIT_MAP event to notify host driver
> updates the credit numbers during interface up.
> The purpose of this patch is making host driver has ability of updating
> the credit numbers when receiving the BRCMF_E_FIFO_CREDIT_MAP event.
>
> Signed-off-by: Wright Feng <wright.feng@cypress.com>
Arend, what should I do with this patchset?
--
https://patchwork.kernel.org/patch/10667393/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-11-29 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 5:51 [PATCH v3 0/3] brcmfmac: throughput enhancement for flow control mode Wright Feng
2018-11-05 5:51 ` [PATCH v3 1/3] brcmfmac: add credit numbers updating support Wright Feng
2018-11-29 15:43 ` Kalle Valo [this message]
2018-12-11 12:43 ` Arend Van Spriel
2018-12-13 14:56 ` Kalle Valo
2018-11-05 5:51 ` [PATCH v3 2/3] brcmfmac: enable frameburst mode in default firmware setting Wright Feng
2018-12-11 12:44 ` Arend Van Spriel
2018-11-05 5:52 ` [PATCH v3 3/3] brcmfmac: handle compressed tx status signal Wright Feng
2018-12-11 12:44 ` 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=20181129154332.A81A46020A@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Chi-Hsien.Lin@cypress.com \
--cc=Wright.Feng@cypress.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--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.