From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Sushrut Shree Trivedi <sushrut.trivedi@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,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: Add second TC9563 PCIe switch node for PCIe1
Date: Thu, 12 Feb 2026 12:46:21 +0100 [thread overview]
Message-ID: <97af21d5-7457-4dc1-bd47-2e34e6df094e@oss.qualcomm.com> (raw)
In-Reply-To: <20260212-industrial-mezzanine-pcie-v3-2-1e152937a76a@oss.qualcomm.com>
On 2/12/26 11:44 AM, Sushrut Shree Trivedi wrote:
> Add a node for the second TC9563 PCIe switch on PCIe1, which is connected
> in cascade to the first TC9563 switch via the former's downstream port.
>
> Two embedded Ethernet devices are present on one of the downstream
> ports of this second switch as well. All the ports present in the
> node represent the downstream ports and embedded endpoints.
>
> The second TC9563 is powered up via the same LDO regulators as the first
> one, and these can be controlled via two GPIOs, which are already present
> as fixed regulators. This TC9563 can also be configured through I2C.
>
> Signed-off-by: Sushrut Shree Trivedi <sushrut.trivedi@oss.qualcomm.com>
> ---
> +&pcie1 {
> + iommu-map = <0x0 &apps_smmu 0x1c80 0x1>,
> + <0x100 &apps_smmu 0x1c81 0x1>,
> + <0x208 &apps_smmu 0x1c84 0x1>,
> + <0x210 &apps_smmu 0x1c85 0x1>,
> + <0x218 &apps_smmu 0x1c86 0x1>,
> + <0x300 &apps_smmu 0x1c87 0x1>,
> + <0x408 &apps_smmu 0x1c90 0x1>,
> + <0x410 &apps_smmu 0x1c91 0x1>,
> + <0x418 &apps_smmu 0x1c92 0x1>,
> + <0x500 &apps_smmu 0x1c93 0x1>,
> + <0x600 &apps_smmu 0x1c94 0x1>,
> + <0x700 &apps_smmu 0x1c95 0x1>,
> + <0x701 &apps_smmu 0x1c96 0x1>,
> + <0x800 &apps_smmu 0x1c97 0x1>,
> + <0x900 &apps_smmu 0x1c98 0x1>,
> + <0x901 &apps_smmu 0x1c99 0x1>;
This map is not just an extension of the existing one - is that
intentional?
Konrad
next prev parent reply other threads:[~2026-02-12 11:46 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 [this message]
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
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=97af21d5-7457-4dc1-bd47-2e34e6df094e@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=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 \
--cc=sushrut.trivedi@oss.qualcomm.com \
/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