LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, pkurapat@codeaurora.org,
	avuyyuru@codeaurora.org, bjorn.andersson@linaro.org,
	cpratapa@codeaurora.org, subashab@codeaurora.org,
	evgreen@chromium.org, elder@kernel.org, netdev@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: ipa: GSI channel flow control
Date: Fri, 26 Nov 2021 10:08:17 -0800	[thread overview]
Message-ID: <20211126100817.09de8f7f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20211124194416.707007-1-elder@linaro.org>

On Wed, 24 Nov 2021 13:44:14 -0600 Alex Elder wrote:
> Starting with IPA v4.2, endpoint DELAY mode (which prevents data
> transfer on TX endpoints) does not work properly.  To address this,
> changes were made to allow underlying GSI channels to be put into
> a "flow controlled" state, which achieves a similar objective.
> The first patch in this series implements the flow controlled
> channel state and the commands used to control it.  It arranges
> to use the new mechanism--instead of DELAY mode--for IPA v4.2+.
> 
> In IPA v4.11, the notion of GSI channel flow control was enhanced,
> and implemented in a slightly different way.  For the most part this
> doesn't affect the way the IPA driver uses flow control, but the
> second patch adds support for the newer mechanism.

Applied, thanks.

      parent reply	other threads:[~2021-11-26 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 19:44 Alex Elder
2021-11-24 19:44 ` [PATCH net-next 1/2] net: ipa: introduce " Alex Elder
2021-11-24 19:44 ` [PATCH net-next 2/2] net: ipa: support enhanced " Alex Elder
2021-11-26 18:08 ` Jakub Kicinski [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=20211126100817.09de8f7f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=avuyyuru@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=cpratapa@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=elder@kernel.org \
    --cc=elder@linaro.org \
    --cc=evgreen@chromium.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pkurapat@codeaurora.org \
    --cc=subashab@codeaurora.org \
    --subject='Re: [PATCH net-next 0/2] net: ipa: GSI channel flow control' \
    /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

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).