public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
Cc: Kishon Vijay Abraham I <kishon@kernel.org>,
	Varadarajan Narayanan <quic_varada@quicinc.com>,
	Dmitry Baryshkov <lumag@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: qcom-qusb2: Update the phy settings for IPQ5424
Date: Fri, 11 Apr 2025 17:05:26 +0530	[thread overview]
Message-ID: <Z/j+fs6hCVhGKLcH@vaman> (raw)
In-Reply-To: <734cf70a-1d96-4a87-bc7e-c070c1e7dc8c@oss.qualcomm.com>

On 11-04-25, 14:29, Kathiravan Thirumoorthy wrote:
> 
> On 4/11/2025 12:34 PM, Vinod Koul wrote:
> > On 07-04-25, 19:51, Kathiravan Thirumoorthy wrote:
> > > Update the phy settings for IPQ5424 to meet compliance requirements.
> > Can you specify which requirements are these?
> 
> The eye diagram (Host High-speed Signal Quality) tests are failed with the
> current settings. So design team asked to revert.

That would be good to mention in changelog.. am sure you wont recall 6
months down the line, which requirement this triggered the change!

> > > The current settings do not meet the requirements, and the design team
> > > has requested to use the settings used for IPQ6018.
> > > 
> > > Revert the commit 9c56a1de296e ("phy: qcom-qusb2: add QUSB2 support for
> > > IPQ5424") and reuse the IPQ6018 settings.
> > Why not do revert first and then add the settings?
> 
> 
> I thought of submitting it separately. But what-if only the first patch
> merged and second one didn't due to some issue, it will break the USB
> feature. So, I thought it would be better to keep it in single commit.
> Please let me know, I can send V2 with 2 patches with the merging strategy
> (both patches should go together to avoid the USB breakage) in cover letter.

Series is applied together and you can mention the dependency on cover
letter

-- 
~Vinod

  reply	other threads:[~2025-04-11 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 14:21 [PATCH] phy: qcom-qusb2: Update the phy settings for IPQ5424 Kathiravan Thirumoorthy
2025-04-08 12:10 ` Dmitry Baryshkov
2025-04-11  7:04 ` Vinod Koul
2025-04-11  8:59   ` Kathiravan Thirumoorthy
2025-04-11 11:35     ` Vinod Koul [this message]
2025-04-11 12:56       ` Kathiravan Thirumoorthy

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=Z/j+fs6hCVhGKLcH@vaman \
    --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