From: Rob Herring <robh@kernel.org>
To: Wesley Cheng <wcheng@codeaurora.org>
Cc: devicetree@vger.kernel.org, agross@kernel.org,
linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org,
balbi@kernel.org, gregkh@linuxfoundation.org, robh+dt@kernel.org,
bjorn.andersson@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v3 3/3] dt-bindings: usb: dwc3: Add entry for tx-fifo-resize
Date: Thu, 28 May 2020 08:55:23 -0600 [thread overview]
Message-ID: <20200528145523.GA51866@bogus> (raw)
In-Reply-To: <1590630363-3934-4-git-send-email-wcheng@codeaurora.org>
On Wed, 27 May 2020 18:46:03 -0700, Wesley Cheng wrote:
> Re-introduce the comment for the tx-fifo-resize setting for the DWC3
> controller. This allows for vendors to control if they require the TX FIFO
> resizing logic on their HW, as the default FIFO size configurations may
> already be sufficient.
>
> Signed-off-by: Wesley Cheng <wcheng@codeaurora.org>
> ---
> Documentation/devicetree/bindings/usb/dwc3.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-05-28 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 1:46 [RFC v3 0/3] Re-introduce TX FIFO resize for larger EP bursting Wesley Cheng
2020-05-28 1:46 ` [RFC v3 1/3] usb: dwc3: Resize TX FIFOs to meet EP bursting requirements Wesley Cheng
2020-05-29 16:28 ` Jack Pham
2020-05-30 6:42 ` Wesley Cheng
2020-05-28 1:46 ` [RFC v3 2/3] arm64: boot: dts: qcom: sm8150: Enable dynamic TX FIFO resize logic Wesley Cheng
2020-05-28 1:46 ` [RFC v3 3/3] dt-bindings: usb: dwc3: Add entry for tx-fifo-resize Wesley Cheng
2020-05-28 14:55 ` Rob Herring [this message]
2020-05-29 10:12 ` [RFC v3 0/3] Re-introduce TX FIFO resize for larger EP bursting Greg KH
2020-05-30 6:31 ` Wesley Cheng
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=20200528145523.GA51866@bogus \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wcheng@codeaurora.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 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).