From: Vinod Koul <vkoul@kernel.org>
To: David Carlier <devnexen@gmail.com>
Cc: neil.armstrong@linaro.org, qiang.yu@oss.qualcomm.com,
mani@kernel.org, konrad.dybcio@oss.qualcomm.com,
krishna.chundru@oss.qualcomm.com, linux-phy@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] phy: qcom: qmp-pcie: Select MFD_SYSCON for the multi-PHY driver
Date: Sat, 03 Oct 2026 17:25:30 +0200 [thread overview]
Message-ID: <179104113076.223537.8163260919027364085.b4-ty@kernel.org> (raw)
In-Reply-To: <20260825225729.230493-1-devnexen@gmail.com>
On Tue, 25 Aug 2026 23:57:28 +0100, David Carlier wrote:
> The driver reads the active link mode through
> syscon_regmap_lookup_by_phandle_args(). Without CONFIG_MFD_SYSCON the
> stub returning -ENOTSUPP is compiled in instead, so probe fails for
> every device and no PHY is ever registered.
>
> Nothing in the build catches this: the driver still compiles, and arm64
> defconfig happens to enable MFD_SYSCON through an unrelated select.
>
> [...]
Applied, thanks!
[1/2] phy: qcom: qmp-pcie: Select MFD_SYSCON for the multi-PHY driver
commit: 77a0e6ae5dec54fb6049e3ab88288bc40c81f9fd
[2/2] phy: qcom: qmp-pcie: Check clock-output-names count in the multi-PHY driver
commit: fb0f0e0e9e5dace7a6d9cde289537980ad35db3d
Best regards,
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2026-10-03 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 22:57 [PATCH 1/2] phy: qcom: qmp-pcie: Select MFD_SYSCON for the multi-PHY driver David Carlier
2026-08-25 22:57 ` [PATCH 2/2] phy: qcom: qmp-pcie: Check clock-output-names count in " David Carlier
2026-08-26 9:09 ` Konrad Dybcio
2026-09-02 13:58 ` Manivannan Sadhasivam
2026-08-25 23:11 ` [PATCH 1/2] phy: qcom: qmp-pcie: Select MFD_SYSCON for " sashiko-bot
2026-08-26 9:09 ` Konrad Dybcio
2026-09-02 13:56 ` Manivannan Sadhasivam
2026-10-03 15:25 ` 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=179104113076.223537.8163260919027364085.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=devnexen@gmail.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krishna.chundru@oss.qualcomm.com \
--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 \
--cc=qiang.yu@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