From: Hangtian Zhu <hangtian.zhu@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: disable WCN6750 and WPSS
Date: Thu, 12 Mar 2026 13:08:56 +0800 [thread overview]
Message-ID: <f5758d4c-d3a0-470a-9dbd-0003684805de@oss.qualcomm.com> (raw)
In-Reply-To: <igjdwtp7ox244c4iqh6t3ilqvxrh6ann23m2lo5m7daxncyffa@e6a34rl74kln>
On 3/12/2026 11:04, Dmitry Baryshkov wrote:
> On Wed, Mar 11, 2026 at 03:06:08PM +0800, Hangtian Zhu wrote:
>>
>>
>> On 3/11/2026 12:34, Dmitry Baryshkov wrote:
>>> On Wed, Mar 11, 2026 at 11:11:45AM +0800, Hangtian Zhu wrote:
>>>> From: Hangtian Zhu <hangtian@oss.qualcomm.com>
>>>>
>>>> Disable WCN6750 and WPSS on industrial mezzanine. On RB3 Gen2 industrial
>>>
>>> You can't disable these devices on the mezzanine, they are not a part of
>>> it.
>>>
>>>> mezzanine platform, pcie0 lines are moved from WCN6750 to QPS615 pcie
>>>
>>> PCIe0. How re they moved? What triggers the move?
>> Please refer to: https://lore.kernel.org/all/20260305-industrial-mezzanine-pcie-v4-0-1f2c9d1344d7@oss.qualcomm.com/
>> On RB3 Gen2 industrial mezzanine, WCN6750 is not connected, instead TC9563 PCIe bridge is connected to PCIe0.
>
> THis doesn't answer the question, what triggers the move? Is it done
> automatically? Is there a pin that is sourced by the carrier board?
> Is there something else?
It's the hardware design itself. Industrial mezzanine (should be called 'kit') is not a plugin device on top of core kit, but a non‑modular integrated device.
Hardware redesigned QCS6490 SOM and disconnected WCN6750 from PCIe0 for this device, PCIe0 connects TC9563 PCIe bridge.
>
>>
>>>
>>>> bridge. Hence disable WPSS and WCN6750 nodes for industrial mezzanine
>>>> platform.
>>>>
>>>> Depends-on: https://lore.kernel.org/all/20260305-industrial-mezzanine-pcie-v4-2-1f2c9d1344d7@oss.qualcomm.com/
>>>
>>> NAK. Don't invent non-standard tags.
>>>
>>>>
>>>> Signed-off-by: Hangtian Zhu <hangtian@oss.qualcomm.com>
>>>> ---
>>>> .../dts/qcom/qcs6490-rb3gen2-industrial-mezzanine.dtso | 8 ++++++++
>>>> 1 file changed, 8 insertions(+)
>>>>
>>>
>>
>
next prev parent reply other threads:[~2026-03-12 5:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 2:32 [PATCH] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: disable wcn6750 and wpss Hangtian Zhu
2026-03-11 2:40 ` Dmitry Baryshkov
2026-03-11 3:14 ` Hangtian Zhu
2026-03-11 4:32 ` Dmitry Baryshkov
2026-03-11 9:03 ` Konrad Dybcio
2026-03-11 3:11 ` [PATCH v2] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: disable WCN6750 and WPSS Hangtian Zhu
2026-03-11 4:34 ` Dmitry Baryshkov
2026-03-11 7:06 ` Hangtian Zhu
2026-03-12 3:04 ` Dmitry Baryshkov
2026-03-12 5:08 ` Hangtian Zhu [this message]
2026-03-13 3:08 ` Dmitry Baryshkov
2026-03-11 7:04 ` [PATCH v3] " Hangtian Zhu
2026-03-12 3:06 ` Dmitry Baryshkov
2026-03-12 3:07 ` Dmitry Baryshkov
2026-03-12 8:20 ` Hangtian Zhu
2026-03-13 3:09 ` Dmitry Baryshkov
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=f5758d4c-d3a0-470a-9dbd-0003684805de@oss.qualcomm.com \
--to=hangtian.zhu@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@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