devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Xu Yang <xu.yang_2@nxp.com>,
	peter.chen@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, gregkh@linuxfoundation.org
Cc: conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
	linux-imx@nxp.com, peng.fan@nxp.com, linux-usb@vger.kernel.org,
	devicetree@vger.kernel.org, jun.li@nxp.com
Subject: Re: [PATCH v2 2/3] dt-bindings: usb: ci-hdrc-usb2: add fsl,picophy-rise-fall-time-adjust property
Date: Tue, 27 Jun 2023 15:49:21 +0200	[thread overview]
Message-ID: <90422bdb-4385-b42c-b5f8-541c6c14be6b@linaro.org> (raw)
In-Reply-To: <20230627112126.1882666-2-xu.yang_2@nxp.com>

On 27/06/2023 13:21, Xu Yang wrote:
> The fsl,picophy-rise-fall-time-adjust property can help to adjust the
> rise/fall times of the high-speed transmitter waveform. The value can be
> 0~3. It has no unit. According to the description of USBNC_n_PHY_CFG1
> register, the rise/fall time will be increased or decreased by a certain
> percentage relative to design default time if a value is given to this
> property.
> 
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>


Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof


  reply	other threads:[~2023-06-27 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 11:21 [PATCH v2 1/3] usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0 Xu Yang
2023-06-27 11:21 ` [PATCH v2 2/3] dt-bindings: usb: ci-hdrc-usb2: add fsl,picophy-rise-fall-time-adjust property Xu Yang
2023-06-27 13:49   ` Krzysztof Kozlowski [this message]
2023-07-10  3:13   ` Peter Chen
2023-06-27 11:21 ` [PATCH v2 3/3] usb: chipidea: imx: add one fsl picophy parameter tuning implementation Xu Yang
2023-07-10  3:12   ` Peter Chen
2023-07-10  3:03 ` [PATCH v2 1/3] usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0 Peter Chen

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=90422bdb-4385-b42c-b5f8-541c6c14be6b@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jun.li@nxp.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=peter.chen@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=xu.yang_2@nxp.com \
    /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).