From: Vinod Koul <vkoul@kernel.org>
To: Kishon Vijay Abraham I <kishon@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Varadarajan Narayanan <quic_varada@quicinc.com>,
Kathiravan Thirumoorthy
<kathiravan.thirumoorthy@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Reuse the IPQ6018 QUSB2 PHY settings for IPQ5424
Date: Wed, 14 May 2025 12:37:39 +0100 [thread overview]
Message-ID: <174722265904.85510.2115353055770936721.b4-ty@kernel.org> (raw)
In-Reply-To: <20250415-revert_hs_phy_settings-v3-0-3a8f86211b59@oss.qualcomm.com>
On Tue, 15 Apr 2025 09:52:49 +0530, Kathiravan Thirumoorthy wrote:
> With the current settings, compliance tests are failing, especially eye
> diagram (Host High-speed Signal Quality) tests. Reuse the IPQ6018
> settings, as mentioned in the Hardware Design Document.
>
> Merge Strategy:
> --------------
> Both the patch in the series should be merged together to avoid breaking
> the USB feature.
>
> [...]
Applied, thanks!
[1/2] Revert "phy: qcom-qusb2: add QUSB2 support for IPQ5424"
commit: 8a040e13afd94a1f91acaf8e0505769d4f7f5af4
[2/2] phy: qcom-qusb2: reuse the IPQ6018 settings for IPQ5424
commit: 25c36b54eafc98b3ef004e2037cea1328d9b8bc5
Best regards,
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2025-05-14 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 4:22 [PATCH v3 0/2] Reuse the IPQ6018 QUSB2 PHY settings for IPQ5424 Kathiravan Thirumoorthy
2025-04-15 4:22 ` [PATCH v3 1/2] Revert "phy: qcom-qusb2: add QUSB2 support for IPQ5424" Kathiravan Thirumoorthy
2025-04-15 4:22 ` [PATCH v3 2/2] phy: qcom-qusb2: reuse the IPQ6018 settings for IPQ5424 Kathiravan Thirumoorthy
2025-04-15 8:07 ` Dmitry Baryshkov
2025-04-30 16:43 ` [PATCH v3 0/2] Reuse the IPQ6018 QUSB2 PHY " Kathiravan Thirumoorthy
2025-05-14 11:37 ` Vinod Koul [this message]
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=174722265904.85510.2115353055770936721.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=kishon@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lumag@kernel.org \
--cc=quic_varada@quicinc.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