From: Krishna Chaitanya Chundru <quic_krichai@quicinc.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Cc: <andersson@kernel.org>, <robh@kernel.org>,
<dmitry.baryshkov@linaro.org>, <manivannan.sadhasivam@linaro.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>
Subject: Re: [PATCH V1] schemas: pci: bridge: Document PCI L0s & L1 entry delay and nfts
Date: Tue, 7 Jan 2025 19:51:56 +0530 [thread overview]
Message-ID: <16ba024e-1e51-be4a-8c6a-e8752abf7b49@quicinc.com> (raw)
In-Reply-To: <20250106233246.GA116572@bhelgaas>
On 1/7/2025 5:02 AM, Bjorn Helgaas wrote:
> On Mon, Jan 06, 2025 at 03:03:04PM +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.
>
> Although these are sort of related because FTS is used during L0s->L1
> transitions, I think these are subtle enough that it's worth splitting
> this into two patches.
>
Ack I will split the patches as suggested in next series.
>> As per PCIe spec 6 sec 4.2.5.6, the number of Fast Training Sequence (FTS)
>> can be programmed by the controllers or endpoints that is used for bit and
>> Symbol lock when transitioning from L0s to L0 based upon the PCIe data rate
>> FTS value can vary. So define a array for each data rate for nfts.
>>
>> These values needs to be programmed before link training.
>
> IIUC, the point of this is to program the N_FTS value ("number of Fast
> Training Sequences required by the Receiver" as described in PCIe
> r6.0, sec 4.2.5.1, tables 4-25, 4-26, 4-27 for TS1, TS2, and Modified
> TS1/TS2 Ordered Sets).
>
> During Link training, all PCIe components transmit the N_FTS value
> they require. Sec 4.2.5.6 only describes the Fast Training Sequence
> from a protocol perspective. The fact that the N_FTS value of a
> device may be programmable is device-specific.
>
> Possible text:
>
> 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.
>
Ack
>> Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
>> ---
>> - This change was suggested in this patch: https://lore.kernel.org/all/20241211060000.3vn3iumouggjcbva@thinkpad/
>> ---
>> dtschema/schemas/pci/pci-bus-common.yaml | 16 ++++++++++++++++
>> 1 file changed, 16 insertions(+)
>>
>> diff --git a/dtschema/schemas/pci/pci-bus-common.yaml b/dtschema/schemas/pci/pci-bus-common.yaml
>> index 94b648f..f0655ba 100644
>> --- a/dtschema/schemas/pci/pci-bus-common.yaml
>> +++ b/dtschema/schemas/pci/pci-bus-common.yaml
>> @@ -128,6 +128,16 @@ properties:
>> $ref: /schemas/types.yaml#/definitions/uint32
>> enum: [ 1, 2, 4, 8, 16, 32 ]
>>
>> + nfts:
>> + description:
>> + Number of Fast Training Sequence (FTS) used during L0s to L0 exit for bit
>> + and Symbol lock.
>
> I think it's worth using the "number of Fast Training Sequences
> required by the Receiver" language from the spec to hint that these
> values will be used to program a component with the number of FTSs
> that it requires as a Receiver, and the component will advertise this
> number as N_FTS during Link training.
>
> n_fts:
> description:
> The number of Fast Training Sequences (N_FTS) required by the
> Receiver (this component) when transitioning the Link from L0s
> to L0; advertised during initial Link training
>
Ack
>> + $ref: /schemas/types.yaml#/definitions/uint32-array
>> + minItems: 1
>> + maxItems: 5
>> + items:
>> + maximum: 255
>> +
>> reset-gpios:
>> description: GPIO controlled connection to PERST# signal
>> maxItems: 1
>> @@ -150,6 +160,12 @@ properties:
>> description: Disables ASPM L0s capability
>> type: boolean
>>
>> + aspm-l0s-entry-delay-ns:
>> + description: Aspm l0s entry delay.
>> +
>> + aspm-l1-entry-delay-ns:
>> + description: Aspm l1 entry delay.
>
> s/Aspm/ASPM/
> s/l0s/L0s/
> s/l1/L1/
>
Ack
> (I mentioned these earlier in the conversation you pointed to above,
> but they got missed)
>
Sorry I missed these to update I will update these in the next patch.
and thanks for reviewing and suggestions for the descriptions and commit
text.
- Krishna Chaitanya.
> Also, to match surrounding items:
> s/\.$//
>
>> vpcie12v-supply:
>> description: 12v regulator phandle for the slot
>>
>> --
>> 2.34.1
>>
>
next prev parent reply other threads:[~2025-01-07 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 9:33 [PATCH V1] schemas: pci: bridge: Document PCI L0s & L1 entry delay and nfts Krishna Chaitanya Chundru
2025-01-06 15:07 ` Rob Herring
2025-01-07 14:19 ` Krishna Chaitanya Chundru
2025-01-07 20:42 ` Bjorn Helgaas
2025-01-08 2:42 ` Krishna Chaitanya Chundru
2025-01-06 23:32 ` Bjorn Helgaas
2025-01-07 14:21 ` Krishna Chaitanya Chundru [this message]
2025-01-07 14:22 ` 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=16ba024e-1e51-be4a-8c6a-e8752abf7b49@quicinc.com \
--to=quic_krichai@quicinc.com \
--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 \
--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