From: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
cros-qcom-dts-watchers@chromium.org,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_vbadigan@quicinc.com, quic_mrana@quicinc.com
Subject: Re: [PATCH v5 2/2] PCI: qcom: Add support for multi-root port
Date: Thu, 3 Jul 2025 09:48:17 +0530 [thread overview]
Message-ID: <cbf32980-8608-42ba-99c7-deed56afae32@oss.qualcomm.com> (raw)
In-Reply-To: <ws2kdznvbrvuvb6k4jov5cd4qzvadeaffjqgeso7u72stormlg@2ffiexejkrk6>
On 7/2/2025 9:03 PM, Manivannan Sadhasivam wrote:
> On Wed, Jul 02, 2025 at 04:50:42PM GMT, Krishna Chaitanya Chundru wrote:
>
> [...]
>
>> - ret = phy_init(pcie->phy);
>> - if (ret)
>> - goto err_pm_runtime_put;
>> + for_each_available_child_of_node(dev->of_node, of_port) {
>> + ret = qcom_pcie_parse_port(pcie, of_port);
>> + of_node_put(of_port);
>> + if (ret) {
>> + if (ret != -ENOENT) {
>> + dev_err_probe(pci->dev, ret,
>> + "Failed to parse port nodes %d\n",
>> + ret);
>> + goto err_port_del;
>> + }
>> + break;
>> + }
>> + }
>> +
>> + /*
>> + * In the case of properties not populated in root port, fallback to the
>> + * legacy method of parsing the host bridge node. This is to maintain DT
>> + * backwards compatibility.
>> + */
>> + if (ret) {
>> + pcie->phy = devm_phy_optional_get(dev, "pciephy");
>> + if (IS_ERR(pcie->phy)) {
>> + ret = PTR_ERR(pcie->phy);
>> + goto err_pm_runtime_put;
>
> Shouldn't this and below be err_port_del?
>
This is a legacy way of parsing property, if the execution
comes here means the port parsing has failed and ports are not created.
so err_port_del will not have any effect.
- Krishna Chaitanya.
> - Mani
>
next prev parent reply other threads:[~2025-07-03 4:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 11:20 [PATCH v5 0/2] PCI: qcom: Move PERST# GPIO & phy retrieval from controller to PCIe bridge node Krishna Chaitanya Chundru
2025-07-02 11:20 ` [PATCH v5 1/2] dt-bindings: PCI: qcom: Move phy & reset gpio's to root port Krishna Chaitanya Chundru
2025-07-02 11:20 ` [PATCH v5 2/2] PCI: qcom: Add support for multi-root port Krishna Chaitanya Chundru
2025-07-02 15:33 ` Manivannan Sadhasivam
2025-07-03 4:18 ` Krishna Chaitanya Chundru [this message]
2025-07-03 6:59 ` Manivannan Sadhasivam
2025-09-08 18:33 ` Bjorn Helgaas
2025-07-03 8:30 ` [PATCH v5 0/2] PCI: qcom: Move PERST# GPIO & phy retrieval from controller to PCIe bridge node Manivannan Sadhasivam
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=cbf32980-8608-42ba-99c7-deed56afae32@oss.qualcomm.com \
--to=krishna.chundru@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=quic_mrana@quicinc.com \
--cc=quic_vbadigan@quicinc.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
all inboxes | Powered by JetHome®