From: Rob Herring <robh@kernel.org>
To: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Cc: andersson@kernel.org, dmitry.baryshkov@linaro.org,
manivannan.sadhasivam@linaro.org, krzk@kernel.org,
helgaas@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
Subject: Re: [PATCH V3 0/2] schemas: pci: bridge: Document PCI L0s & L1 entry delay and N_FTS
Date: Wed, 19 Feb 2025 13:49:23 -0600 [thread overview]
Message-ID: <20250219194923.GA2776564-robh@kernel.org> (raw)
In-Reply-To: <20250216014510.3990613-1-krishna.chundru@oss.qualcomm.com>
On Sun, Feb 16, 2025 at 07:15:08AM +0530, Krishna Chaitanya Chundru wrote:
> Some controllers and endpoints provide provision to program the entry
> delays of L0s & L1 which will allow the link to enter L0s & L1 more
> aggressively to save power.
>
> Per PCIe r6.0, sec 4.2.5.1, during Link training, a PCIe component
> captures the N_FTS value it receives. Per 4.2.5.6, when
> transitioning the Link from L0s to L0, it must transmit N_FTS Fast
> Training Sequences to enable the receiver to obtain bit and Symbol
> lock.
>
> Components may have device-specific ways to configure N_FTS values
> to advertise during Link training. Define an n-fts array with an
> entry for each supported data rate.
>
> Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
> ---
> changes in v3:-
> - Update the description to specfify about entries of the array (rob)
> changes in v2:-
> - Split N_FTS & L1 and L0s entry delay in two patches (bjorn)
> - Update the commit text, description (bjorn)
>
> Krishna Chaitanya Chundru (2):
> schemas: pci: bridge: Document PCI L0s & L1 entry delay
> schemas: pci: bridge: Document PCIe N_FTS
>
> dtschema/schemas/pci/pci-bus-common.yaml | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
Applied, thanks.
Rob
prev parent reply other threads:[~2025-02-19 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 1:45 [PATCH V3 0/2] schemas: pci: bridge: Document PCI L0s & L1 entry delay and N_FTS Krishna Chaitanya Chundru
2025-02-16 1:45 ` [PATCH V3 1/2] schemas: pci: bridge: Document PCI L0s & L1 entry delay Krishna Chaitanya Chundru
2025-02-16 1:45 ` [PATCH V3 2/2] schemas: pci: bridge: Document PCIe N_FTS Krishna Chaitanya Chundru
2025-02-19 19:49 ` Rob Herring [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=20250219194923.GA2776564-robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=helgaas@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=manivannan.sadhasivam@linaro.org \
--cc=quic_vbadigan@quicinc.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).