From: Vinod Koul <vkoul@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Shazad Hussain <quic_shazhuss@quicinc.com>,
Adrien Thierry <athierry@redhat.com>
Cc: linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org
Subject: Re: [PATCH v2 0/2] phy: qcom-qmp-usb: fix initialization of PCS_USB
Date: Thu, 21 Sep 2023 16:26:03 +0200 [thread overview]
Message-ID: <169530636318.106093.4451140958293220977.b4-ty@kernel.org> (raw)
In-Reply-To: <20230828152353.16529-1-athierry@redhat.com>
On Mon, 28 Aug 2023 11:23:49 -0400, Adrien Thierry wrote:
> This series attempts at making sure PCS_USB registers are properly
> initialized. I tested it on the sa8775p. AFAICT there's no noticeable
> change before/after the patch series: lsusb and dmesg output are the same.
> USB is still working properly. I don't know what those PCS_USB registers
> do exactly on the qmp PHY and I don't have access to the PHY datasheet, so
> it's hard for me to tell the impact of them being initialized vs not.
>
> [...]
Applied, thanks!
[1/2] phy: qcom-qmp-usb: initialize PCS_USB registers
commit: 2d3465a75c9f83684d17da6807423824bf260524
[2/2] phy: qcom-qmp-usb: split PCS_USB init table for sc8280xp and sa8775p
commit: c599dc5cca4dd6a5c664e4a8837246e68a96cb4c
Best regards,
--
~Vinod
prev parent reply other threads:[~2023-09-21 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 15:23 [PATCH v2 0/2] phy: qcom-qmp-usb: fix initialization of PCS_USB Adrien Thierry
2023-08-28 15:23 ` [PATCH v2 1/2] phy: qcom-qmp-usb: initialize PCS_USB registers Adrien Thierry
2023-08-28 15:44 ` Dmitry Baryshkov
2023-08-28 19:07 ` Konrad Dybcio
2023-08-28 15:23 ` [PATCH v2 2/2] phy: qcom-qmp-usb: split PCS_USB init table for sc8280xp and sa8775p Adrien Thierry
2023-09-14 20:48 ` [PATCH v2 0/2] phy: qcom-qmp-usb: fix initialization of PCS_USB Adrien Thierry
2023-09-21 14:26 ` 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=169530636318.106093.4451140958293220977.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=athierry@redhat.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=quic_shazhuss@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