From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Sajid Dalvi" <sdalvi@google.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>
Cc: kernel-team@android.com, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: PCI: dwc: Add snps,skip-wait-link-up
Date: Fri, 24 Feb 2023 21:40:01 +0100 [thread overview]
Message-ID: <b50ab99f-e307-3a66-9198-85a71b012e5e@linaro.org> (raw)
In-Reply-To: <20230224195749.818282-2-sdalvi@google.com>
On 24/02/2023 20:57, Sajid Dalvi wrote:
> When the Root Complex is probed, the default behavior is to spin in a loop
> waiting for the link to come up. In some systems the link is not brought up
> during probe, but later in the context of an end-point turning on.
> This property will allow the loop to be skipped.
>
> Signed-off-by: Sajid Dalvi <sdalvi@google.com>
> ---
Thank you for your patch. There is something to discuss/improve.
> Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml b/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml
> index 1a83f0f65f19..0b8950a73b7e 100644
> --- a/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml
> +++ b/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml
> @@ -197,6 +197,14 @@ properties:
> - contains:
> const: msi
>
> + snps,skip-wait-link-up:
> + $ref: /schemas/types.yaml#/definitions/flag
> + description:
> + When the Root Complex is probed, the default behavior is to spin in a
> + loop waiting for the link to come up. In some systems the link is not
> + brought up during probe, but later in the context of an end-point turning
> + on. This property will allow the loop to be skipped.
I fail to see how probe behavior is related to properties of hardware.
You describe OS behavior, not hardware. This does not look like
belonging to DT.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-02-24 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 19:57 [PATCH v1 0/2] Skip waiting for link up during probe Sajid Dalvi
2023-02-24 19:57 ` [PATCH v1 1/2] dt-bindings: PCI: dwc: Add snps,skip-wait-link-up Sajid Dalvi
2023-02-24 20:40 ` Krzysztof Kozlowski [this message]
[not found] ` <CAEbtx1k-7TJPcd3+cueRoKLJcoUQLfF6nfOQFVfzB0YCUrbtqg@mail.gmail.com>
[not found] ` <2e4964c1-0831-c156-3372-81a56f8d623e@linaro.org>
2023-02-24 22:09 ` Sajid Dalvi
2023-02-25 10:00 ` Krzysztof Kozlowski
2023-02-25 10:08 ` Krzysztof Kozlowski
2023-02-27 20:15 ` Sajid Dalvi
2023-02-24 19:57 ` [PATCH v1 2/2] PCI: dwc: Skip waiting for link up on probe Sajid Dalvi
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=b50ab99f-e307-3a66-9198-85a71b012e5e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=sdalvi@google.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;
as well as URLs for NNTP newsgroup(s).