From: Rob Herring <robh@kernel.org>
To: Pengyu Luo <mitltlatltl@gmail.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Abel Vesa <abel.vesa@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: phy: qcom,snps-eusb2-repeater: Add more tuning overrides
Date: Mon, 21 Apr 2025 16:32:44 -0500 [thread overview]
Message-ID: <20250421213244.GA2725065-robh@kernel.org> (raw)
In-Reply-To: <20250416120201.244133-2-mitltlatltl@gmail.com>
On Wed, Apr 16, 2025 at 08:02:00PM +0800, Pengyu Luo wrote:
> In downstream tree, many registers need to be overridden, it varies
> from devices and platforms, not only HS trasmit amplitude(0x51),
spelling
> HS disconnect threshold(0x53), Tx pre-emphasis tuning(0x57). And
> some devices require different overrides for different dr_mode. So
> add property entries for host mode, original entries will be used
> for device mode.
>
> Signed-off-by: Pengyu Luo <mitltlatltl@gmail.com>
> ---
> .../phy/qcom,snps-eusb2-repeater.yaml | 41 +++++++++++++++++--
> 1 file changed, 38 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/qcom,snps-eusb2-repeater.yaml b/Documentation/devicetree/bindings/phy/qcom,snps-eusb2-repeater.yaml
> index d16a543a7..d0f5e770d 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,snps-eusb2-repeater.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,snps-eusb2-repeater.yaml
> @@ -36,25 +36,60 @@ properties:
>
> qcom,tune-usb2-disc-thres:
> $ref: /schemas/types.yaml#/definitions/uint8
> - description: High-Speed disconnect threshold
> + description: High-Speed disconnect threshold for device mode
> minimum: 0
> maximum: 7
> default: 0
>
> qcom,tune-usb2-amplitude:
> $ref: /schemas/types.yaml#/definitions/uint8
> - description: High-Speed transmit amplitude
> + description: High-Speed transmit amplitude for device mode
> minimum: 0
> maximum: 15
> default: 8
>
> qcom,tune-usb2-preem:
> $ref: /schemas/types.yaml#/definitions/uint8
> - description: High-Speed TX pre-emphasis tuning
> + description: High-Speed TX pre-emphasis tuning for device mode
> minimum: 0
> maximum: 7
> default: 5
>
> + qcom,tune-usb2-squelch:
> + $ref: /schemas/types.yaml#/definitions/uint8
> + description: Squelch detection threshold tuning for device mode
> + minimum: 0
> + maximum: 7
> + default: 3
> +
> + qcom,tune-usb2-disc-thres-host:
Put this and the others after each existing property (for device mode).
Ideally, these would all be in alphabetical order.
> + $ref: /schemas/types.yaml#/definitions/uint8
> + description: High-Speed disconnect threshold for host mode
> + minimum: 0
> + maximum: 7
> + default: 0
> +
> + qcom,tune-usb2-amplitude-host:
> + $ref: /schemas/types.yaml#/definitions/uint8
> + description: High-Speed transmit amplitude for host mode
> + minimum: 0
> + maximum: 15
> + default: 8
> +
> + qcom,tune-usb2-preem-host:
> + $ref: /schemas/types.yaml#/definitions/uint8
> + description: High-Speed TX pre-emphasis tuning for host mode
> + minimum: 0
> + maximum: 7
> + default: 5
> +
> + qcom,tune-usb2-squelch-host:
> + $ref: /schemas/types.yaml#/definitions/uint8
> + description: Squelch detection threshold tuning for host mode
> + minimum: 0
> + maximum: 7
> + default: 3
> +
> required:
> - compatible
> - reg
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-04-21 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 12:01 [PATCH v2 0/2] phy: qualcomm: phy-qcom-eusb2-repeater: rework reg override handler Pengyu Luo
2025-04-16 12:02 ` [PATCH v2 1/2] dt-bindings: phy: qcom,snps-eusb2-repeater: Add more tuning overrides Pengyu Luo
2025-04-21 21:32 ` Rob Herring [this message]
2025-04-16 12:02 ` [PATCH v2 2/2] phy: qualcomm: phy-qcom-eusb2-repeater: rework reg override handler Pengyu Luo
2025-04-25 19:41 ` Dmitry Baryshkov
2025-04-26 8:14 ` Pengyu Luo
2025-04-28 16:58 ` Dmitry Baryshkov
2025-04-29 9:23 ` Pengyu Luo
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=20250421213244.GA2725065-robh@kernel.org \
--to=robh@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mitltlatltl@gmail.com \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).