From: Krishna Chaitanya Chundru <quic_krichai@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <quic_vbadigan@quicinc.com>,
<quic_ramkri@quicinc.com>, <quic_nitegupt@quicinc.com>,
<quic_skananth@quicinc.com>, <quic_parass@quicinc.com>
Subject: Re: [PATCH] arm64: dts: qcom: qcs6490-rb3gen2: Add PCIe nodes
Date: Thu, 8 Feb 2024 11:44:02 +0530 [thread overview]
Message-ID: <dec2976e-6e1e-6121-e175-210377ff6925@quicinc.com> (raw)
In-Reply-To: <CAA8EJpqjm_2aE+7BtMkFUdet11q7v_jyHbUEpiDHSBSnzhndYA@mail.gmail.com>
On 2/7/2024 5:17 PM, Dmitry Baryshkov wrote:
> On Wed, 7 Feb 2024 at 12:42, Krishna chaitanya chundru
> <quic_krichai@quicinc.com> wrote:
>>
>> Enable PCIe1 controller and its corresponding PHY nodes on
>> qcs6490-rb3g2 platform.
>>
>> PCIe switch is connected to PCIe1, PCIe switch has multiple endpoints
>> connected. For each endpoint a unique BDF will be assigned and should
>> assign unique smmu id. So for each BDF add smmu id.
>>
>> Signed-off-by: Krishna chaitanya chundru <quic_krichai@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts | 42 ++++++++++++++++++++++++++++
>> 1 file changed, 42 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
>> index 8bb7d13d85f6..0082a3399453 100644
>> --- a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
>> +++ b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
>> @@ -413,6 +413,32 @@ vreg_bob_3p296: bob {
>> };
>> };
>>
>> +&pcie1 {
>> + perst-gpios = <&tlmm 2 GPIO_ACTIVE_LOW>;
>> +
>> + pinctrl-0 = <&pcie1_reset_n>, <&pcie1_wake_n>;
>> + pinctrl-names = "default";
>> +
>> + 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>,
>> + <0x400 &apps_smmu 0x1c88 0x1>,
>> + <0x500 &apps_smmu 0x1c89 0x1>,
>> + <0x501 &apps_smmu 0x1c90 0x1>;
>
> Is the iommu-map really board specific?
>
The iommu-map for PCIe varies if PCIe switch is connected.
For this platform a PCIe switch is connected and for that reason
we need to define additional smmu ID's for each BDF.
For that reason we defined here as these ID's are applicable only
for this board.
- Krishna Chaitanya.
>> +
>> + status = "okay";
>> +};
>> +
>> +&pcie1_phy {
>> + vdda-phy-supply = <&vreg_l10c_0p88>;
>> + vdda-pll-supply = <&vreg_l6b_1p2>;
>> +
>> + status = "okay";
>> +};
>> +
>> &qupv3_id_0 {
>> status = "okay";
>> };
>> @@ -420,6 +446,22 @@ &qupv3_id_0 {
>> &tlmm {
>> gpio-reserved-ranges = <32 2>, /* ADSP */
>> <48 4>; /* NFC */
>> +
>> + pcie1_reset_n: pcie1-reset-n-state {
>> + pins = "gpio2";
>> + function = "gpio";
>> + drive-strength = <16>;
>> + output-low;
>> + bias-disable;
>> + };
>> +
>> + pcie1_wake_n: pcie1-wake-n-state {
>> + pins = "gpio3";
>> + function = "gpio";
>> + drive-strength = <2>;
>> + bias-pull-up;
>> + };
>> +
>> };
>>
>> &uart5 {
>>
>> ---
>> base-commit: 70d201a40823acba23899342d62bc2644051ad2e
>> change-id: 20240207-enable_pcie-95b1d6612b27
>>
>> Best regards,
>> --
>> Krishna chaitanya chundru <quic_krichai@quicinc.com>
>>
>>
>
>
next prev parent reply other threads:[~2024-02-08 6:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 10:41 [PATCH] arm64: dts: qcom: qcs6490-rb3gen2: Add PCIe nodes Krishna chaitanya chundru
2024-02-07 11:47 ` Dmitry Baryshkov
2024-02-08 6:14 ` Krishna Chaitanya Chundru [this message]
2024-02-08 6:51 ` Dmitry Baryshkov
2024-02-08 14:58 ` Krishna Chaitanya Chundru
2024-02-08 15:19 ` Dmitry Baryshkov
2024-02-09 7:28 ` Krishna Chaitanya Chundru
2024-02-09 7:57 ` Manivannan Sadhasivam
2024-02-09 10:56 ` Dmitry Baryshkov
2024-02-12 13:15 ` Manivannan Sadhasivam
2024-02-12 13:26 ` Dmitry Baryshkov
2024-10-01 10:16 ` Manivannan Sadhasivam
2024-10-01 12:30 ` Dmitry Baryshkov
2024-10-01 14:19 ` Manivannan Sadhasivam
2024-10-01 15:08 ` Dmitry Baryshkov
2024-10-11 11:54 ` Krishna Chaitanya Chundru
2024-10-12 12:43 ` Manivannan Sadhasivam
2024-10-13 23:25 ` Dmitry Baryshkov
2024-10-16 5:13 ` Krishna Chaitanya Chundru
2024-10-17 11:12 ` Dmitry Baryshkov
2024-10-22 15:10 ` Manivannan Sadhasivam
2024-10-22 17:22 ` 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=dec2976e-6e1e-6121-e175-210377ff6925@quicinc.com \
--to=quic_krichai@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_nitegupt@quicinc.com \
--cc=quic_parass@quicinc.com \
--cc=quic_ramkri@quicinc.com \
--cc=quic_skananth@quicinc.com \
--cc=quic_vbadigan@quicinc.com \
--cc=robh+dt@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