From: Xu Yang <xu.yang_2@nxp.com>
To: Frank Li <Frank.li@nxp.com>
Cc: vkoul@kernel.org, kishon@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, jun.li@nxp.com,
alexander.stein@ew.tq-group.com, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/3] dt-bindings: phy: imx8mq-usb: improve some tuning properties
Date: Tue, 29 Apr 2025 14:26:40 +0800 [thread overview]
Message-ID: <20250429062640.cqqtkp3vwkd5a2gp@hippo> (raw)
In-Reply-To: <aBBpzljSQEnQwlvU@lizhi-Precision-Tower-5810>
Hi Frank,
On Tue, Apr 29, 2025 at 01:55:26AM -0400, Frank Li wrote:
> On Tue, Apr 29, 2025 at 11:30:07AM +0800, Xu Yang wrote:
> > Commit b2e75563dc39 ("dt-bindings: phy: imx8mq-usb: add phy tuning
> > properties") add many tuning properties, but some parameter value doesn't
> > match the register description. It made some changes based on the original
> > value: add offset to a negative number so turn it to a non-negative number.
> > However, it's not easy to find an exact tuning value from register field
> > with such conversion.
> >
> > Because device-tree supports negative parameter number, this will improve
> > some propertie's parameter.
> >
> > Mainly include below properties:
> > - fsl,phy-tx-vref-tune-percent
> > - fsl,phy-tx-rise-tune-percent
> > - fsl,phy-comp-dis-tune-percent
>
> It should be standard unit. for example 0% to 100%. DT don't prefer you
> direct use register value.
Yes. The dtschema and driver already use standard unit.
This patch is going to correct the unintuitive expression.
Take tx-rise-tune as example, register field as below:
00b - + 3%
[21:20] 01b - 0 (default)
TXRISETUNE 10b - - 1%
11b - - 3%
The valid value of tx-rise-tune is [-3%, +3%]. However, the current dtschema
add an offset which caused the valid value to [97%, 103%].
fsl,phy-tx-rise-tune-percent:
minimum: 97
maximum: 103
When I first added tuning property to DTS, I thought I was reading the wrong
dtschema. Other users may meet such confuse too.
Thanks,
Xu Yang
>
> Frank
>
> >
> > The parameter value of above 3 properties are USB PHY specific. i.MX8MP
> > and i.MX95 USB PHY has different meanings. So this add restrictions for
> > them.
> >
> > - fsl,phy-tx-vboost-level-microvolt
> >
> > For this property, the parameter value is wrong in register description.
> > This will correct it according to true value.
> >
> > For detailed info, please refer to i.MX8MP and i.MX95 latest reference
> > manual.
> >
> > Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> >
> > ---
> > Changes in v2:
> > - keep widest constraints
> > - use multipleOf for some properties
> > ---
> > .../bindings/phy/fsl,imx8mq-usb-phy.yaml | 60 +++++++++++++++----
> > 1 file changed, 49 insertions(+), 11 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml b/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml
> > index daee0c0fc915..71e5940ef4b8 100644
> > --- a/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml
> > +++ b/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml
> > @@ -42,16 +42,17 @@ properties:
> >
> > fsl,phy-tx-vref-tune-percent:
> > description:
> > - Tunes the HS DC level relative to the nominal level
> > - minimum: 94
> > - maximum: 124
> > + Tunes the HS DC level relative to the nominal level. It varies
> > + between different PHY versions
> > + minimum: -1000
> > + maximum: 875
> >
> > fsl,phy-tx-rise-tune-percent:
> > description:
> > Adjusts the rise/fall time duration of the HS waveform relative to
> > - its nominal value
> > - minimum: 97
> > - maximum: 103
> > + its nominal value. It varies between different PHY versions
> > + minimum: -10
> > + maximum: 20
> >
> > fsl,phy-tx-preemp-amp-tune-microamp:
> > description:
> > @@ -63,15 +64,14 @@ properties:
> > fsl,phy-tx-vboost-level-microvolt:
> > description:
> > Adjust the boosted transmit launch pk-pk differential amplitude
> > - minimum: 880
> > - maximum: 1120
> > + enum: [844, 1008, 1156]
> >
> > fsl,phy-comp-dis-tune-percent:
> > description:
> > Adjust the voltage level used to detect a disconnect event at the host
> > - relative to the nominal value
> > - minimum: 91
> > - maximum: 115
> > + relative to the nominal value. It varies between different PHY versions
> > + minimum: -60
> > + maximum: 45
> >
> > fsl,phy-pcs-tx-deemph-3p5db-attenuation-db:
> > description:
> > @@ -112,6 +112,44 @@ allOf:
> > reg:
> > maxItems: 1
> >
> > + - if:
> > + properties:
> > + compatible:
> > + enum:
> > + - fsl,imx8mq-usb-phy
> > + - fsl,imx8mp-usb-phy
> > + then:
> > + properties:
> > + fsl,phy-tx-vref-tune-percent:
> > + minimum: -6
> > + maximum: 24
> > + multipleOf: 2
> > + fsl,phy-tx-rise-tune-percent:
> > + enum: [-3, -1, 0, 3]
> > + fsl,phy-comp-dis-tune-percent:
> > + enum: [-9, -6, -3, 0, 4, 7, 11, 15]
> > +
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - fsl,imx95-usb-phy
> > + then:
> > + properties:
> > + fsl,phy-tx-vref-tune-percent:
> > + description: 100x the original
> > + minimum: -1000
> > + maximum: 875
> > + multipleOf: 125
> > + fsl,phy-tx-rise-tune-percent:
> > + enum: [-10, 0, 15, 20]
> > + fsl,phy-comp-dis-tune-percent:
> > + description: 10x the original
> > + minimum: -60
> > + maximum: 45
> > + multipleOf: 15
> > +
> > - if:
> > required:
> > - orientation-switch
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2025-04-29 6:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 3:30 [PATCH v2 1/3] dt-bindings: phy: imx8mq-usb: improve some tuning properties Xu Yang
2025-04-29 3:30 ` [PATCH v2 2/3] phy: fsl-imx8mq-usb: improve some tuning parameters Xu Yang
2025-04-29 3:30 ` [PATCH v2 3/3] phy: fsl-imx8mq-usb: add i.MX95 tuning support Xu Yang
2025-04-29 5:55 ` [PATCH v2 1/3] dt-bindings: phy: imx8mq-usb: improve some tuning properties Frank Li
2025-04-29 6:26 ` Xu Yang [this message]
2025-04-29 12:10 ` Frank Li
2025-04-29 9:30 ` Xu Yang
2025-04-29 13:10 ` Krzysztof Kozlowski
2025-04-29 15:10 ` Conor Dooley
2025-04-30 5:57 ` Xu Yang
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=20250429062640.cqqtkp3vwkd5a2gp@hippo \
--to=xu.yang_2@nxp.com \
--cc=Frank.li@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--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