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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: qcm6490-idp: Enable PCIe1
Date: Thu, 19 Feb 2026 15:46:21 +0530 [thread overview]
Message-ID: <aac6bf18-0529-416a-b10a-c72b56532010@oss.qualcomm.com> (raw)
In-Reply-To: <5f62d384-cd53-4e35-87c3-67b45241b90f@oss.qualcomm.com>
On 2/12/2026 5:49 PM, Konrad Dybcio wrote:
> On 2/12/26 1:06 PM, Sushrut Shree Trivedi wrote:
>> Remove PCIe1 clocks from protected-list and enable PCIe1 controller
>> and its corresponding PHY nodes on qcm6490-idp platform.
>>
>> PCIe1 is used to connect NVMe based SSD's on this platform.
> Is that a M.2 slot? What key (B/M etc.)?
The NVMe is actually soldered onto the board.
>
> [...]
>
>> &pm7250b_gpios {
>> lcd_disp_bias_en: lcd-disp-bias-en-state {
>> pins = "gpio2";
>> @@ -920,6 +931,22 @@ &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;
> You're asserting the active state of a pin permanently this way, unless
> the driver takes over, please drop this line
If we de-assert the reset, it is an indication to the endpoint that it
can participate
in link-training with the host. Hence, until the host driver is probed
and necessary
resources enabled, we keep the perst asserted so endpoint doesn't try to
participate in link training.
>
>> + bias-disable;
>> + };
> Wrong indentation
Ack'd.
>
>> +
>> + pcie1_wake_n: pcie1-wake-n-state {
>> + pins = "gpio3";
>> + function = "gpio";
>> + drive-strength = <2>;
>> + bias-pull-up;
>> + };
>> +
>> +
> Double \n
Ack'd.
>
>> sd_cd: sd-cd-state {
>> pins = "gpio91";
>> function = "gpio";
>>
>> ---
>> base-commit: 4f938c7d3b25d87b356af4106c2682caf8c835a2
>> change-id: 20260212-qcm6490-idp-24f7b6a1812d
>>
>> Best regards,
next prev parent reply other threads:[~2026-02-19 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 12:06 [PATCH] arm64: dts: qcom: qcm6490-idp: Enable PCIe1 Sushrut Shree Trivedi
2026-02-12 12:19 ` Konrad Dybcio
2026-02-19 10:16 ` Sushrut Shree Trivedi [this message]
2026-02-19 13:32 ` Bjorn Andersson
2026-03-21 6:58 ` 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=aac6bf18-0529-416a-b10a-c72b56532010@oss.qualcomm.com \
--to=sushrut.trivedi@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=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