From: Vinod Koul <vkoul@kernel.org>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH 0/3] Fix up AON clamps on qmp-combo-phy
Date: Thu, 19 Nov 2026 21:54:09 +0530 [thread overview]
Message-ID: <179510544997.1370333.11528579298614736658.b4-ty@kernel.org> (raw)
In-Reply-To: <20261102-topic-qmp_aon_clamp-v1-0-141c2cb6cdf6@oss.qualcomm.com>
On Mon, 02 Nov 2026 14:59:31 +0100, Konrad Dybcio wrote:
> Various platforms have apparently not had the AON clamp writes end up
> at the desired registers. This fixes that up, based on the robot's
> findings.
>
> Depends on (reviewed and ready to be picked up):
> https://lore.kernel.org/linux-arm-msm/20261023123512.1912-1-26rote@gmail.com/
>
> [...]
Applied, thanks!
[1/3] phy: qcom: qmp-combo: Separate PCS misc clamp mapping
commit: 391a14a0a31505c9202369258d47d1fc42c1fe65
[2/3] phy: qcom: qmp-combo: Make v4/v5 targets use the right clamp
commit: ff2aca40e0d58c4f7f4fbddcb95f15d7d983af05
[3/3] phy: qcom: qmp-combo: Use V6 offsets for PCS-AON clamps
commit: 478797c9284d2ad85a2fd1f61ba021932099b36e
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-11-19 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 13:59 Konrad Dybcio
2026-11-02 13:59 ` [PATCH 1/3] phy: qcom: qmp-combo: Separate PCS misc clamp mapping Konrad Dybcio
2026-11-03 9:56 ` Abel Vesa
2026-11-02 13:59 ` [PATCH 2/3] phy: qcom: qmp-combo: Make v4/v5 targets use the right clamp Konrad Dybcio
2026-11-03 9:57 ` Abel Vesa
2026-11-02 13:59 ` [PATCH 3/3] phy: qcom: qmp-combo: Use V6 offsets for PCS-AON clamps Konrad Dybcio
2026-11-03 9:57 ` Abel Vesa
2026-11-15 20:39 ` [PATCH 0/3] Fix up AON clamps on qmp-combo-phy Manivannan Sadhasivam
2026-11-17 15:03 ` Konrad Dybcio
2026-11-19 16:24 ` 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=179510544997.1370333.11528579298614736658.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mani@kernel.org \
--cc=neil.armstrong@linaro.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
all inboxes | Powered by JetHome®