Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Hangtian Zhu <hangtian.zhu@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] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: disable wcn6750 and wpss
Date: Wed, 11 Mar 2026 10:03:39 +0100	[thread overview]
Message-ID: <2fa0b336-0ca8-4418-9866-e240fc12079f@oss.qualcomm.com> (raw)
In-Reply-To: <ogn3a6chd2s6ys5voxktnzyldoqfmytadsavvaku5ym22yisyk@uvpf7ax6wwno>

On 3/11/26 5:32 AM, Dmitry Baryshkov wrote:
> On Wed, Mar 11, 2026 at 11:14:55AM +0800, Hangtian Zhu wrote:
>>
>>
>> On 3/11/2026 10:40, Dmitry Baryshkov wrote:
>>> On Wed, Mar 11, 2026 at 10:32:19AM +0800, Hangtian Zhu wrote:
>>>> From: Hangtian Zhu <hangtian@oss.qualcomm.com>
>>>>
>>>> Disable wcn6750 and wpss on industrial mezzanine. On rb3gen2 industrial
>>>
>>> RB3 Gen2, WCN6750, WPSS, etc.
>> Done, udpated.
>>>
>>>> mezzanine platform, pcie0 lines are moved from wcn6750 to qps615 pcie
>>>> bridge. Hence disable wpss and wcn6750 nodes for industrial mezzanine
>>>> platform.
>>>
>>> Are they rerouted on the mezzanine or should the user toggle a DIP
>>> switch somewhere?
>> It's routed signals inside of SOM, no DIP switch changes needed.
> 
> How?
> 
>>>
>>>>
>>>> Depends-on: [PATCH v4 1/2] arm64: dts: qcom:
>>>> qcs6490-rb3gen2-industrial-mezzanine: Add TC9563 PCIe switch node for PCIe0
>>>> Depends-on: [PATCH v4 2/2] arm64: dts: qcom:
>>>> qcs6490-rb3gen2-industrial-mezzanine: Add second TC9563 PCIe switch node
>>>> for PCIe1
>>>
>>> ENOSUCH tag, please learn to use b4 or git-send-email to define
>>> dependencies.
>> Updated with lore link.
> 
> Nice, but the tag is still not documented and isn't used as such. Please
> use standarard ways to declare dependencies (I pointed them).

(b4 prep --edit-deps)

Konrad

  reply	other threads:[~2026-03-11  9:03 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 [this message]
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
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=2fa0b336-0ca8-4418-9866-e240fc12079f@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=hangtian.zhu@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