From: Jie Luo <jie.luo@oss.qualcomm.com>
To: Kathiravan Thirumoorthy
<kathiravan.thirumoorthy@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: ipq5018: Add pinctrl for MDIO bus
Date: Tue, 11 Aug 2026 23:24:13 +0800 [thread overview]
Message-ID: <5a8a773d-5fa8-4e93-8130-2b49997691fc@oss.qualcomm.com> (raw)
In-Reply-To: <076b0942-7e1a-4a6c-9293-04a7ff77abcb@oss.qualcomm.com>
On 8/11/2026 10:00 PM, Kathiravan Thirumoorthy wrote:
>
> On 8/11/2026 7:06 PM, Luo Jie wrote:
>> The external MDIO bus (mdio1) needs its MDC/MDIO lines configured via
>> TLMM pinctrl; without this the pins are left in their default state and
>> the bus does not function on boards that enable it.
>
> Should we move the TLMM definitions to the board DTS file rather than
> keeping it in the SoC DTSI?
The MDC/MDIO pin-group definition is SoC-specific. On IPQ5018, only
these two TLMM pins support the MDIO interface—one for MDC and one for
MDIO—with no alternative pin assignments available. Therefore, the
definition can remain in the IPQ5018 pinctrl/SoC DTSI for reuse.
next prev parent reply other threads:[~2026-08-11 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 13:36 [PATCH] arm64: dts: qcom: ipq5018: Add pinctrl for MDIO bus Luo Jie
2026-08-11 14:00 ` Kathiravan Thirumoorthy
2026-08-11 15:24 ` Jie Luo [this message]
2026-08-11 16:11 ` Kathiravan Thirumoorthy
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=5a8a773d-5fa8-4e93-8130-2b49997691fc@oss.qualcomm.com \
--to=jie.luo@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@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