Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Sushrut Shree Trivedi <sushrut.trivedi@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@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>,
	Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v3 0/2] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: Add TC9563 PCIe switch nodes
Date: Tue, 24 Feb 2026 12:03:51 +0530	[thread overview]
Message-ID: <40eb66b5-7f3d-4df5-b6db-719168d85b72@oss.qualcomm.com> (raw)
In-Reply-To: <3c06c3cd-cc10-4e2c-9001-9e0a4174d489@oss.qualcomm.com>


On 2/12/2026 5:18 PM, Konrad Dybcio wrote:
> On 2/12/26 11:44 AM, Sushrut Shree Trivedi wrote:
>> Add nodes for the two additional TC9563 PCIe switches present on the
>> QCOM RB3Gen2 Industrial Mezzanine platform.
>>
>> One of the TC9563 is connected directly to the PCIe0 root-port while
>> the second TC9563 switch is connected in cascade fashion to another
>> already available TC9563 switch on PCIe1 via the former's downstream
>> port (DSP). The final PCIe hierarchy on the Industrial Mezz platform
> 	^ +Mani is that PCIe terminology, or is that a Toshiba-ism?
The PCIe Spec actually uses the DSP terminology
under r6.2 sec 7.9.29: Streamlined Virtual Channel
Extended Capability (SVC)

"If the SVC Extended Capability structure is implemented in a
USP containing one or more Switch USP Functions, it must be
implemented in all associated Switch DSP Functions"

Sushrut
>
> Konrad

      reply	other threads:[~2026-02-24  6:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 10:44 [PATCH v3 0/2] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: Add TC9563 PCIe switch nodes Sushrut Shree Trivedi
2026-02-12 10:44 ` [PATCH v3 1/2] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: Add TC9563 PCIe switch node for PCIe0 Sushrut Shree Trivedi
2026-02-12 11:47   ` Konrad Dybcio
2026-02-13 16:40   ` Dmitry Baryshkov
2026-02-12 10:44 ` [PATCH v3 2/2] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: Add second TC9563 PCIe switch node for PCIe1 Sushrut Shree Trivedi
2026-02-12 11:46   ` Konrad Dybcio
2026-02-15 14:19     ` Sushrut Shree Trivedi
2026-02-16 11:28       ` Konrad Dybcio
2026-02-18 10:00         ` Sushrut Shree Trivedi
2026-02-18 10:43           ` Konrad Dybcio
2026-02-18 10:43   ` Konrad Dybcio
2026-02-12 11:48 ` [PATCH v3 0/2] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: Add TC9563 PCIe switch nodes Konrad Dybcio
2026-02-24  6:33   ` Sushrut Shree Trivedi [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=40eb66b5-7f3d-4df5-b6db-719168d85b72@oss.qualcomm.com \
    --to=sushrut.trivedi@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konrad.dybcio@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=manivannan.sadhasivam@oss.qualcomm.com \
    --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