2023-08-30 17:31:07 +02:00
|
|
|
# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
|
|
|
|
|
%YAML 1.2
|
|
|
|
|
---
|
2023-10-24 12:59:35 +02:00
|
|
|
$id: http://devicetree.org/schemas/phy/phy-tegra194-p2u.yaml#
|
|
|
|
|
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
2023-08-30 17:31:07 +02:00
|
|
|
|
|
|
|
|
title: NVIDIA Tegra194 & Tegra234 P2U
|
|
|
|
|
|
|
|
|
|
maintainers:
|
|
|
|
|
- Thierry Reding <treding@nvidia.com>
|
|
|
|
|
|
|
|
|
|
description: >
|
|
|
|
|
Tegra194 has two PHY bricks namely HSIO (High Speed IO) and NVHS (NVIDIA High
|
|
|
|
|
Speed) each interfacing with 12 and 8 P2U instances respectively.
|
|
|
|
|
Tegra234 has three PHY bricks namely HSIO, NVHS and GBE (Gigabit Ethernet)
|
|
|
|
|
each interfacing with 8, 8 and 8 P2U instances respectively.
|
|
|
|
|
A P2U instance is a glue logic between Synopsys DesignWare Core PCIe IP's PIPE
|
|
|
|
|
interface and PHY of HSIO/NVHS/GBE bricks. Each P2U instance represents one
|
|
|
|
|
PCIe lane.
|
|
|
|
|
|
|
|
|
|
properties:
|
|
|
|
|
compatible:
|
|
|
|
|
enum:
|
|
|
|
|
- nvidia,tegra194-p2u
|
|
|
|
|
- nvidia,tegra234-p2u
|
|
|
|
|
|
|
|
|
|
reg:
|
|
|
|
|
maxItems: 1
|
|
|
|
|
description: Should be the physical address space and length of respective each P2U instance.
|
|
|
|
|
|
|
|
|
|
reg-names:
|
|
|
|
|
items:
|
|
|
|
|
- const: ctl
|
|
|
|
|
|
|
|
|
|
nvidia,skip-sz-protect-en:
|
|
|
|
|
description: Should be present if two PCIe retimers are present between
|
|
|
|
|
the root port and its immediate downstream device.
|
|
|
|
|
type: boolean
|
|
|
|
|
|
|
|
|
|
'#phy-cells':
|
|
|
|
|
const: 0
|
|
|
|
|
|
|
|
|
|
additionalProperties: false
|
|
|
|
|
|
|
|
|
|
examples:
|
|
|
|
|
- |
|
|
|
|
|
p2u_hsio_0: phy@3e10000 {
|
|
|
|
|
compatible = "nvidia,tegra194-p2u";
|
|
|
|
|
reg = <0x03e10000 0x10000>;
|
|
|
|
|
reg-names = "ctl";
|
|
|
|
|
|
|
|
|
|
#phy-cells = <0>;
|
|
|
|
|
};
|
