From: Jie Luo <jie.luo@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: 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>,
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: Wed, 12 Aug 2026 15:16:06 +0800 [thread overview]
Message-ID: <1c260f20-711c-46a8-95f7-c03bccc41222@oss.qualcomm.com> (raw)
In-Reply-To: <oijzkh6xykig4vufjsxup6xg3mohgqcyhc3fxaimxbhqbg3niy@2c7tgkdk7tm3>
On 8/12/2026 5:44 AM, Dmitry Baryshkov wrote:
> On Tue, Aug 11, 2026 at 11:24:13PM +0800, Jie Luo wrote:
>>
>>
>> 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.
>
> Is it expected that the drive strength is also common to all boards?
>
Yes. The MDC/MDIO pin configurations, including the drive strength, are
identical across the IPQ5018 RDP boards.
next prev parent reply other threads:[~2026-08-12 7:16 UTC|newest]
Thread overview: 7+ 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
2026-08-11 16:11 ` Kathiravan Thirumoorthy
2026-08-11 21:44 ` Dmitry Baryshkov
2026-08-12 7:16 ` Jie Luo [this message]
2026-08-17 12:43 ` Konrad Dybcio
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=1c260f20-711c-46a8-95f7-c03bccc41222@oss.qualcomm.com \
--to=jie.luo@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--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