mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
	robh@kernel.org, saravanak@kernel.org
Cc: andersson@kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	qiang.yu@oss.qualcomm.com
Subject: Re: [PATCH] of: property: Create devlink between PCI Host bridge and Root Port suppliers
Date: Thu, 5 Feb 2026 09:50:20 +0100	[thread overview]
Message-ID: <bfba9d62-2741-47b8-8325-2d932c20c9e7@oss.qualcomm.com> (raw)
In-Reply-To: <20260205070640.10653-1-manivannan.sadhasivam@oss.qualcomm.com>

On 2/5/26 8:06 AM, Manivannan Sadhasivam wrote:
> In the recent times, devicetree started to represent the PCI Host bridge
> supplies like PHY in the Root Port nodes as seen in commit 38fcbfbd4207
> ("dt-bindings: PCI: qcom: Move PHY & reset GPIO to Root Port node"). But
> the Host bridge drivers still need to control these supplies as a part of
> their controller initialization/deinitialization sequence.
> 
> So the Host bridge drivers end up parsing the Root Port supplies in their
> probe() and controlled them. A downside to this approach is that the
> devlink dependency between the suppliers and Host bridge is completely
> broken. Due to this, the driver core probes the Host bridge drivers even if
> the suppliers are not ready, causing probe deferrals and setup teardowns in
> probe().
> 
> These probe deferrals sometime happen over 1000 times (as reported in Qcom
> Glymur platform) leading to a waste of CPU resources and increase in boot
> time. So to fix these unnecessary deferrals, create devlink between the
> Host bridge and Root Port suppliers in of_fwnode_add_links(). This will
> allow the driver core to probe the Host bridge drivers only when all Root
> Port suppliers are available.
> 
> Reported-by: Bjorn Andersson <andersson@kernel.org>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> ---

[...]

This is not 'required' in bindings and device_type="pci" doesn't uniquely
identify root complexes (as can be seen below).. but I suppose this is the
best delimiter we've got

Perhaps it could be made 'required'?

Konrad

> +		for_each_available_child_of_node_scoped(con_np, child) {
> +			if (of_node_is_type(child, "pci")) {
> +				for_each_property_of_node(child, p)
> +					of_link_property(child, con_np, p->name);
> +			}
> +		}
> +	}
>  
>  	return 0;
>  }

  reply	other threads:[~2026-02-05  8:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05  7:06 Manivannan Sadhasivam
2026-02-05  8:50 ` Konrad Dybcio [this message]
2026-02-05  8:50   ` Konrad Dybcio
2026-02-05  9:01   ` Manivannan Sadhasivam
2026-02-08  1:27     ` Saravana Kannan
2026-02-08 15:21       ` Manivannan Sadhasivam
2026-02-08 23:09         ` Bjorn Andersson
2026-02-09 10:38       ` Konrad Dybcio
2026-02-09 18:20         ` Rob Herring
2026-02-09 18:26     ` Rob Herring

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=bfba9d62-2741-47b8-8325-2d932c20c9e7@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@oss.qualcomm.com \
    --cc=qiang.yu@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=saravanak@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®