public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Wesley Cheng <quic_wcheng@quicinc.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Felipe Balbi <balbi@kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v3 1/2] usb: dwc3: core: configure TX/RX threshold for DWC3_IP
Date: Wed, 13 Sep 2023 01:54:08 +0000	[thread overview]
Message-ID: <608f80dc54164ef5be822890701362ad@realtek.com> (raw)
In-Reply-To: <20230913010637.c4eukssffviugkhl@synopsys.com>

Hi Wesley and Thinh,

> > Aren't there value limitations for some of these (if not all)
> > settings?  For example, in the DWC3 programming guide, the max burst
> > fields say (for
> > DWC31):
> >       "Note: This field can only be set to 2, 4, 8 or 16."
> >
> > And for the packet threshold count:
> >       "Valid values are from 1 to 16."
> >
> 
> Stanley documented this in the dt binding. I think what he had written there is
> fine.
> 

Thanks for Thinh's response.

Stanley

  reply	other threads:[~2023-09-13  1:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12  4:19 [PATCH v3 1/2] usb: dwc3: core: configure TX/RX threshold for DWC3_IP Stanley Chang
2023-09-12  4:19 ` [PATCH v3 2/2] dt-bindings: usb: dwc3: Add DWC_usb3 TX/RX threshold configurable Stanley Chang
2023-09-12 23:39 ` [PATCH v3 1/2] usb: dwc3: core: configure TX/RX threshold for DWC3_IP Wesley Cheng
2023-09-13  1:06   ` Thinh Nguyen
2023-09-13  1:54     ` Stanley Chang[昌育德] [this message]
2023-09-13  1:14 ` Thinh Nguyen

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=608f80dc54164ef5be822890701362ad@realtek.com \
    --to=stanley_chang@realtek.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=balbi@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=quic_wcheng@quicinc.com \
    --cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox