From: Vinod Koul <vkoul@kernel.org>
To: Esteban Urrutia <esteuwu@proton.me>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Initial PCIe0 PHY support for SM8475
Date: Fri, 7 Aug 2026 13:17:06 +0530 [thread overview]
Message-ID: <anWNemb2WCYUwRJm@vaman> (raw)
In-Reply-To: <f0c1eba8-c6d9-4831-a460-980bead03c4d@proton.me>
On 07-08-26, 03:27, Esteban Urrutia wrote:
> On 7/15/26 2:37 AM, Esteban Urrutia via B4 Relay wrote:
> > This series adds support for the PCIe0 PHY found in the SM8475 SoC.
> > The initialization sequence varies noticeably when compared to the one used
> > in the SM8450 SoC, hence the need to add support for this PHY.
> Any chance on this series being picked up?
> Kind of related (since both series belong to the same subsystem): I
> resent USB SS support for SM8475 some days ago and this has been picked
> up already.
Already picked up, should be pushed later today
--
~Vinod
prev parent reply other threads:[~2026-08-07 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 6:37 [PATCH v2 0/3] Initial PCIe0 PHY support for SM8475 Esteban Urrutia via B4 Relay
2026-07-15 6:37 ` [PATCH v2 1/3] dt-bindings: phy: qcom,sc8280xp-qmp-pcie-phy: Add SM8475 QMP PHY Esteban Urrutia via B4 Relay
2026-07-21 8:19 ` Krzysztof Kozlowski
2026-07-15 6:37 ` [PATCH v2 2/3] phy: qcom: qmp-pcie: Add pcs_lane1 offset to V5 offsets Esteban Urrutia via B4 Relay
2026-07-21 22:51 ` Dmitry Baryshkov
2026-07-22 0:20 ` Esteban Urrutia
2026-07-15 6:37 ` [PATCH v2 3/3] phy: qcom: qmp-pcie: Add support for SM8475 Gen3x1 PCIe0 port Esteban Urrutia via B4 Relay
2026-07-21 22:53 ` Dmitry Baryshkov
2026-08-07 3:27 ` [PATCH v2 0/3] Initial PCIe0 PHY support for SM8475 Esteban Urrutia
2026-08-07 7:47 ` 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=anWNemb2WCYUwRJm@vaman \
--to=vkoul@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=esteuwu@proton.me \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.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