From: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Wesley Cheng <wesley.cheng@oss.qualcomm.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kathiravan T <quic_kathirav@quicinc.com>,
Baruch Siach <baruch@tkos.co.il>,
Dmitry Baryshkov <lumag@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] phy: qcom-qusb2: don't unrelated bits if autoresume is not used
Date: Thu, 2 Jul 2026 19:13:29 +0530 [thread overview]
Message-ID: <e39c9092-30f3-4c04-8bdc-c6400871cecf@oss.qualcomm.com> (raw)
In-Reply-To: <3c533783-e2a5-48f3-8275-4cef5651938b@oss.qualcomm.com>
On 7/2/2026 5:54 PM, Konrad Dybcio wrote:
> On 7/2/26 2:21 PM, Dmitry Baryshkov wrote:
>> On Thu, Jul 02, 2026 at 02:00:06PM +0200, Konrad Dybcio wrote:
>>> On 7/2/26 1:40 PM, Dmitry Baryshkov wrote:
>>>> The IPQ6018 and QCS615 platforms don't need to toggle the autoresume
>>>> bit.
>>>
>>> why?
>>
>> Here I have no idea, the HPG is unspecific, exact details are to be
>> defined somewhere else. The platforms, when they were added, just stated
>> that autoresume is to be skipped. Maybe original developers (in cc) can
>> answer this question. Anyway, if autoresume is to be toggled, it should
>> be coming as a separate fixup. I can reorder the patches though, so that
>> at least register layout is correct.
>
> +Krishna, Wesley?
>
I checked downstream driver code and I see this:
1. If the phy is qusb2 v2, then we are setting and clearing BIT(0) of
TEST1 register.
2. If the phy is qusb2, then we are setting and clearing BIT(3) of
TEST_CTRL register.
For both IPQ6018 and QCS615, I checked and its BIT(3) of TEST_CTRL
register to be set.
For msm8998 it is BIT(0) of TEST1 register.
Also for qcs615, in downstream code, I see that auto-resume is being
set. Its a mistake from my end when I added [1].
[1]:
https://lore.kernel.org/all/20241014084432.3310114-5-quic_kriskura@quicinc.com/
Regards,
Krishna,
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-07-02 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 11:40 [PATCH 0/2] phy: qcom-qusb2: sort out register layouts Dmitry Baryshkov
2026-07-02 11:40 ` [PATCH 1/2] phy: qcom-qusb2: don't unrelated bits if autoresume is not used Dmitry Baryshkov
2026-07-02 12:00 ` Konrad Dybcio
2026-07-02 12:21 ` Dmitry Baryshkov
2026-07-02 12:24 ` Konrad Dybcio
2026-07-02 13:43 ` Krishna Kurapati [this message]
2026-07-02 13:46 ` Dmitry Baryshkov
2026-07-02 12:02 ` Konrad Dybcio
2026-07-02 11:40 ` [PATCH 2/2] phy: qcom-qusb2: fix autoresume handling Dmitry Baryshkov
2026-07-02 12:03 ` Konrad Dybcio
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=e39c9092-30f3-4c04-8bdc-c6400871cecf@oss.qualcomm.com \
--to=krishna.kurapati@oss.qualcomm.com \
--cc=baruch@tkos.co.il \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lumag@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_kathirav@quicinc.com \
--cc=vkoul@kernel.org \
--cc=wesley.cheng@oss.qualcomm.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