From: Manikanta Maddireddy <mmaddireddy@nvidia.com>
To: <vkoul@kernel.org>, <kishon@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <vidyas@nvidia.com>
Cc: <linux-phy@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-pci@vger.kernel.org>, <bhelgaas@google.com>,
<lpieralisi@kernel.org>, <nkristam@nvidia.com>,
Manikanta Maddireddy <mmaddireddy@nvidia.com>
Subject: [IP REVIEW PATCH 0/3] Add support for Lane Margining at Receiver
Date: Thu, 24 Nov 2022 14:05:07 +0530 [thread overview]
Message-ID: <20221124083510.3008139-1-mmaddireddy@nvidia.com> (raw)
Tegra234 supports Lane Margining at Receiver feature. However, this
requires programming of per lane PIPE2UPHY hardware instance to relay
the lane margin control and margin status information between PCIe
controller and UPHY modules. This series adds this support in PIPE2UPHY
driver.
Manikanta Maddireddy (3):
phy: tegra: p2u: Add lane margin support
dts: soc: t234: Add uphy lane number and intr in p2u nodes
dt-bindings: PHY: P2U: Add PCIe lane margining support
.../bindings/phy/phy-tegra194-p2u.yaml | 50 ++++
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 120 ++++++++
drivers/phy/tegra/phy-tegra194-p2u.c | 274 ++++++++++++++++++
3 files changed, 444 insertions(+)
--
2.25.1
next reply other threads:[~2022-11-24 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 8:35 Manikanta Maddireddy [this message]
2022-11-24 8:35 ` [PATCH 1/3] dt-bindings: PHY: P2U: Add PCIe lane margining support Manikanta Maddireddy
2022-11-24 8:45 ` Krzysztof Kozlowski
2022-11-30 15:11 ` Manikanta Maddireddy
2022-11-30 15:15 ` Krzysztof Kozlowski
2022-11-30 16:13 ` Manikanta Maddireddy
2022-11-24 8:35 ` [PATCH 2/3] arm64: tegra: Add uphy lane number and intr in p2u nodes Manikanta Maddireddy
2022-12-01 9:44 ` Jon Hunter
2022-12-02 5:14 ` Manikanta Maddireddy
2022-11-24 8:35 ` [PATCH 3/3] phy: tegra: Add lane margin support Manikanta Maddireddy
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=20221124083510.3008139-1-mmaddireddy@nvidia.com \
--to=mmaddireddy@nvidia.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=nkristam@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=vidyas@nvidia.com \
--cc=vkoul@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).