From: Bjorn Helgaas <helgaas@kernel.org>
To: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Cc: andersson@kernel.org, robh@kernel.org, mani@kernel.org,
krzk@kernel.org, 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, lukas@wunner.de
Subject: Re: [PATCH v3] schemas: pci: Document PCIe T_POWER_ON
Date: Wed, 26 Nov 2025 08:44:09 -0600 [thread overview]
Message-ID: <20251126144409.GA2825768@bhelgaas> (raw)
In-Reply-To: <20251126103112.838549-1-krishna.chundru@oss.qualcomm.com>
On Wed, Nov 26, 2025 at 04:01:12PM +0530, Krishna Chaitanya Chundru wrote:
> From PCIe r7, 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 and drivers using
> this property are responsible for parsing both the scale and the value of
> T_POWER_ON to comply with the PCIe specification.
Add space before open "(" above and in description below.
> Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
> ---
> Changes in v2:
> - Move the property to pci-device.yaml so that it will be applicable to
> endpoint devices also (Mani).
> - Use latest spec (Lukas)
> - Link to v2: https://lore.kernel.org/all/20251110112947.2071036-1-krishna.chundru@oss.qualcomm.com/
> Changes in v1:
> - Updated the commiit text (Mani).
> - Link to v1: https://lore.kernel.org/all/20251110112550.2070659-1-krishna.chundru@oss.qualcomm.com/#t
>
> dtschema/schemas/pci/pci-device.yaml | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/dtschema/schemas/pci/pci-device.yaml b/dtschema/schemas/pci/pci-device.yaml
> index ca094a0..4baab71 100644
> --- a/dtschema/schemas/pci/pci-device.yaml
> +++ b/dtschema/schemas/pci/pci-device.yaml
> @@ -63,6 +63,15 @@ properties:
> description: GPIO controlled connection to WAKE# signal
> 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 r7.0, sec 5.5.4).
> +
> required:
> - reg
>
> --
> 2.34.1
>
prev parent reply other threads:[~2025-11-26 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 10:31 [PATCH v3] schemas: pci: Document PCIe T_POWER_ON Krishna Chaitanya Chundru
2025-11-26 13:30 ` Manivannan Sadhasivam
2025-11-26 14:44 ` Bjorn Helgaas [this message]
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=20251126144409.GA2825768@bhelgaas \
--to=helgaas@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--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=lukas@wunner.de \
--cc=mani@kernel.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