From: Bjorn Helgaas <helgaas@kernel.org>
To: Priyank Rathod <rathodpriyank@google.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v4] PCI/pcie: Add PCIe Lane Margining at Receiver (LMR) support
Date: Tue, 18 Aug 2026 17:29:16 -0500 [thread overview]
Message-ID: <20260818222916.GA747146@bhelgaas> (raw)
In-Reply-To: <20260818-pcie-lmt-v4-1-eb17a6d755fa@google.com>
On Tue, Aug 18, 2026 at 09:20:24PM +0000, Priyank Rathod wrote:
> Per PCIe Base Specification r6.0, sec 8.4.4 ("Lane Margining at
> Receiver"), PCIe devices operating at 16.0 GT/s (Gen 4) or higher data
> rates support the Lane Margining at Receiver Extended Capability
> (ID 0x27), and it is mandatory for receivers operating at 64.0 GT/s
> (Gen 6) or higher data rates. Lane Margining allows software to
> evaluate high-speed link margins by measuring timing and voltage steps
> for each individual physical lane and receiver.
Aug 18 13:57 Priyank Rathod [PATCH] PCI/pcie: Add PCIe Lane ...
Aug 18 14:26 Priyank Rathod ├─>[PATCH v2] PCI/pcie: Add PCIe Lane ...
Aug 18 15:49 Priyank Rathod ├─>[PATCH v3] PCI/pcie: Add PCIe Lane ...
Aug 18 16:20 Priyank Rathod └─>[PATCH v4] PCI/pcie: Add PCIe Lane ...
No need to rush:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=v7.2#n361
The v7.3 merge window is open now, so this is likely v7.4 material.
prev parent reply other threads:[~2026-08-18 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 18:57 [PATCH] PCI/pcie: Add PCIe Lane Margining at Receiver (LMR) support Priyank Rathod
2026-08-18 19:10 ` sashiko-bot
2026-08-18 19:26 ` [PATCH v2] " Priyank Rathod
2026-08-18 20:00 ` sashiko-bot
2026-08-18 20:49 ` [PATCH v3] " Priyank Rathod
2026-08-18 21:00 ` sashiko-bot
2026-08-18 21:20 ` [PATCH v4] " Priyank Rathod
2026-08-18 21:32 ` sashiko-bot
2026-08-18 22:29 ` 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=20260818222916.GA747146@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rathodpriyank@google.com \
--cc=shuah@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