From: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
To: andersson@kernel.org, robh@kernel.org,
manivannan.sadhasivam@linaro.org, krzk@kernel.org,
helgaas@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
lpieralisi@kernel.org, kw@linux.com, conor+dt@kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree-spec@vger.kernel.org, quic_vbadigan@quicinc.com
Subject: Re: [PATCH] schemas: pci: Document PCIe T_POWER_ON
Date: Mon, 10 Nov 2025 18:43:34 +0530 [thread overview]
Message-ID: <511ebf46-63ed-45af-9d66-ccd1d944763a@oss.qualcomm.com> (raw)
In-Reply-To: <20251110112550.2070659-1-krishna.chundru@oss.qualcomm.com>
Please ignore this patch, it has some mistakes which I have sent
accidentally.
- Krishna Chaitanya.
On 11/10/2025 4:55 PM, Krishna Chaitanya Chundru wrote:
> From PCIe r6, sec 5.5.4 & Table 5-11 in sec 5.5.5 T_POWER_ON is the
> minimum amount of time(in us) that each component must wait in L1.2.Exit
> after sampling CLKREQ# asserted before actively driving the interface to
> ensure no device is ever actively driving into an unpowered component and
> these values are based on the components and AC coupling capacitors used
> in the connection linking the two components.
>
> This property should be used to indicate the T_POWER_ON for each Root Port.
>
> Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
> ---
> Changes in V1:
> - Updated the commit text (Mani).
>
> dtschema/schemas/pci/pci-bus-common.yaml | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/dtschema/schemas/pci/pci-bus-common.yaml b/dtschema/schemas/pci/pci-bus-common.yaml
> index 5257339..bbe5510 100644
> --- a/dtschema/schemas/pci/pci-bus-common.yaml
> +++ b/dtschema/schemas/pci/pci-bus-common.yaml
> @@ -152,6 +152,15 @@ properties:
> This property is invalid in host bridge nodes.
> maxItems: 1
>
> + t-power-on-us:
> + description:
> + The minimum amount of time that each component must wait in
> + L1.2.Exit after sampling CLKREQ# asserted before actively driving
> + the interface to ensure no device is ever actively driving into an
> + unpowered component. This value is based on the components and AC
> + coupling capacitors used in the connection linking the two
> + components(PCIe r6.0, sec 5.5.4).
> +
> supports-clkreq:
> description:
> If present this property specifies that CLKREQ signal routing exists from
next prev parent reply other threads:[~2025-11-10 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 11:25 [PATCH] schemas: pci: Document PCIe T_POWER_ON Krishna Chaitanya Chundru
2025-11-10 13:13 ` Krishna Chaitanya Chundru [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-06 11:39 Krishna Chaitanya Chundru
2025-11-06 12:38 ` Manivannan Sadhasivam
2025-11-06 14:07 ` Krishna Chaitanya Chundru
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=511ebf46-63ed-45af-9d66-ccd1d944763a@oss.qualcomm.com \
--to=krishna.chundru@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@kernel.org \
--cc=krzk@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--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