From: Hans Zhang <18255117159@163.com>
To: Manivannan Sadhasivam <mani@kernel.org>, Rob Herring <robh@kernel.org>
Cc: bhelgaas@google.com, lpieralisi@kernel.org, kw@linux.com,
krzk+dt@kernel.org, manivannan.sadhasivam@linaro.org,
conor+dt@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: PCI: Extend max-link-speed to support PCIe Gen5/Gen6
Date: Wed, 18 Jun 2025 22:22:45 +0800 [thread overview]
Message-ID: <9203cf6e-ca59-416a-9c98-a2d6a5c6ce6f@163.com> (raw)
In-Reply-To: <q5ltnilbdhfxwh6ucjnm3wichrmu5wyjsx6eheiazqypveu3sm@euuvpjwu77h4>
On 2025/6/18 00:45, Manivannan Sadhasivam wrote:
> On Thu, May 29, 2025 at 10:10:24AM +0800, Hans Zhang wrote:
>> Update the device tree binding documentation for PCI to include
>> PCIe Gen5 and Gen6 support in the `max-link-speed` property.
>> The original documentation limited the value to 1~4 (Gen1~Gen4),
>> but the kernel now supports up to Gen6. This change ensures the
>> documentation aligns with the actual code implementation.
>>
>> Signed-off-by: Hans Zhang <18255117159@163.com>
>> ---
>> dtschema/schemas/pci/pci-bus-common.yaml | 2 +-
>
> As Rob commented in v1, this file lives in dtschema project. So update it there:
> https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/pci/pci-bus-common.yaml
>
Dear Mani,
I made the patch based on the latest dtschema code pulled from github.
Also, I saw similar submissions as follows:
https://lore.kernel.org/linux-pci/advhonmqnxm4s6r3cl7ll5y3jfc566fcjvetvlzvy7bztzetev@t75xmo5fktde/
I don't know if Rob obtained this patch from here and then applied it to
the dtschema project? Is there still a special process to submit this patch?
Dear Rob,
Can you apply this patch directly to the dtschema project?
Best regards,
Hans
> - Mani
>
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/dtschema/schemas/pci/pci-bus-common.yaml b/dtschema/schemas/pci/pci-bus-common.yaml
>> index ca97a00..413ef05 100644
>> --- a/dtschema/schemas/pci/pci-bus-common.yaml
>> +++ b/dtschema/schemas/pci/pci-bus-common.yaml
>> @@ -121,7 +121,7 @@ properties:
>> unnecessary operation for unsupported link speed, for instance, trying to
>> do training for unsupported link speed, etc.
>> $ref: /schemas/types.yaml#/definitions/uint32
>> - enum: [ 1, 2, 3, 4 ]
>> + enum: [ 1, 2, 3, 4, 5, 6 ]
>>
>> num-lanes:
>> description: The number of PCIe lanes
>> --
>> 2.25.1
>>
>
next prev parent reply other threads:[~2025-06-18 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 2:10 [PATCH v2 0/3] Relax max-link-speed check to support PCIe Gen5/Gen6 Hans Zhang
2025-05-29 2:10 ` [PATCH v2 1/3] dt-bindings: PCI: Extend max-link-speed " Hans Zhang
2025-06-17 16:45 ` Manivannan Sadhasivam
2025-06-18 14:22 ` Hans Zhang [this message]
2025-06-28 15:40 ` Hans Zhang
2025-05-29 2:10 ` [PATCH v2 2/3] dt-bindings: PCI: pci-ep: Extend max-link-speed to " Hans Zhang
2025-05-29 2:10 ` [PATCH v2 3/3] PCI: of: Relax max-link-speed check to support " Hans Zhang
2025-06-17 16:50 ` Manivannan Sadhasivam
2025-06-18 14:24 ` Hans Zhang
2025-08-16 16:05 ` Hans Zhang
2025-06-17 16:49 ` [PATCH v2 0/3] " Manivannan Sadhasivam
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=9203cf6e-ca59-416a-9c98-a2d6a5c6ce6f@163.com \
--to=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).