From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Rob Herring <robh@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
"Douglas Anderson" <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Flavio Suligoi <f.suligoi@asem.it>, Ray Chi <raychi@google.com>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: [PATCH v6 4/5] dt-bindings: phy: realtek: Add the doc about the Realtek SoC USB 2.0 PHY
Date: Fri, 30 Jun 2023 07:33:45 +0000 [thread overview]
Message-ID: <f17378f003144f4ba50ec08e0ad38c0b@realtek.com> (raw)
In-Reply-To: <20230629164220.GA3146341-robh@kernel.org>
Hi Rob,
> On Thu, Jun 29, 2023 at 01:45:12PM +0800, Stanley Chang wrote:
> > Add the documentation explain the property about Realtek USB PHY driver.
>
> In the subject, drop "the doc about the". It's redundant. And perhaps add 'DHC
> RTD SoC' if this isn't for *all* Realtek SoCs.
>
> > Realtek DHC (digital home center) RTD SoCs support DWC3 XHCI USB
> > controller. Added the driver to drive the USB 2.0 PHY transceivers.
>
> driver? This is a binding for the h/w.
I mean, the driver is drivers/phy/realtek/phy-rtk-usb2.c
I will revise as
dt-bindings: phy: realtek: Add the Realtek DHC RTD SoC USB 2.0 PHY
Add the documentation explain the property about Realtek USB PHY driver.
Realtek DHC (digital home center) RTD SoCs support DWC3 XHCI USB
controller and uses phy-rtk-usb2 as driver for USB 2.0 PHY transceiver..
> > +$id: http://devicetree.org/schemas/phy/realtek,usb2phy.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Realtek DHC SoCs USB 2.0 PHY
> > +
> > +maintainers:
> > + - Stanley Chang <stanley_chang@realtek.com>
> > +
> > +description:
>
> You need '|' if formatting (line breaks) are important.
I think I need it. I will add it.
> > + realtek,inverse-hstx-sync-clock:
> > + description:
> > + For one of the phys of RTD1619b SoC, the synchronous clock of the
> > + high-speed tx must be inverted.
>
> "invert" assumes I know what non-inverted means. I do not. Better to state in
> terms of active high, low, falling edge, rising edge, etc.
Meaning, the clock must be reversed.
>
> > + type: boolean
> > +
> > + realtek,driving-level:
> > + description:
> > + Control the magnitude of High speed Dp/Dm output swing.
> > + For a different board or port, the original magnitude maybe not
> meet
> > + the specification. In this situation we can adjust the value to meet
> > + the specification.
>
> What are the units?
There is no unit. It is only a gain for adjusting the magnitude.
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + default: 8
> > + minimum: 0
> > + maximum: 31
> > +
> > + realtek,driving-compensate:
>
> compensate what?
It is to compensate the driving level. In other word, to adjust the driving level.
Thanks,
Stanley
next prev parent reply other threads:[~2023-06-30 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 5:45 [PATCH v6 1/5] usb: phy: add usb phy notify port status API Stanley Chang
2023-06-29 5:45 ` [PATCH v6 2/5] phy: realtek: usb: Add driver for the Realtek SoC USB 2.0 PHY Stanley Chang
2023-06-29 5:45 ` [PATCH v6 3/5] phy: realtek: usb: Add driver for the Realtek SoC USB 3.0 PHY Stanley Chang
2023-06-29 5:45 ` [PATCH v6 4/5] dt-bindings: phy: realtek: Add the doc about the Realtek SoC USB 2.0 PHY Stanley Chang
2023-06-29 16:42 ` Rob Herring
2023-06-30 7:33 ` Stanley Chang[昌育德] [this message]
2023-06-30 18:21 ` Conor Dooley
2023-07-03 7:52 ` Stanley Chang[昌育德]
2023-06-29 5:45 ` [PATCH v6 5/5] dt-bindings: phy: realtek: Add the doc about the Realtek SoC USB 3.0 PHY Stanley Chang
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=f17378f003144f4ba50ec08e0ad38c0b@realtek.com \
--to=stanley_chang@realtek.com \
--cc=bagasdotme@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=f.suligoi@asem.it \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mka@chromium.org \
--cc=raychi@google.com \
--cc=robh@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=vkoul@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