Tom Rini | 6bb92fc | 2024-05-20 09:54:58 -0600 | [diff] [blame] | 1 | # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause |
| 2 | %YAML 1.2 |
| 3 | --- |
| 4 | $id: http://devicetree.org/schemas/net/ethernet-phy-package.yaml# |
| 5 | $schema: http://devicetree.org/meta-schemas/core.yaml# |
| 6 | |
| 7 | title: Ethernet PHY Package Common Properties |
| 8 | |
| 9 | maintainers: |
| 10 | - Christian Marangi <ansuelsmth@gmail.com> |
| 11 | |
| 12 | description: |
| 13 | PHY packages are multi-port Ethernet PHY of the same family |
| 14 | and each Ethernet PHY is affected by the global configuration |
| 15 | of the PHY package. |
| 16 | |
| 17 | Each reg of the PHYs defined in the PHY package node is |
| 18 | absolute and describe the real address of the Ethernet PHY on |
| 19 | the MDIO bus. |
| 20 | |
| 21 | properties: |
| 22 | $nodename: |
| 23 | pattern: "^ethernet-phy-package@[a-f0-9]+$" |
| 24 | |
| 25 | reg: |
| 26 | minimum: 0 |
| 27 | maximum: 31 |
| 28 | description: |
| 29 | The base ID number for the PHY package. |
| 30 | Commonly the ID of the first PHY in the PHY package. |
| 31 | |
| 32 | Some PHY in the PHY package might be not defined but |
| 33 | still occupy ID on the device (just not attached to |
| 34 | anything) hence the PHY package reg might correspond |
| 35 | to a not attached PHY (offset 0). |
| 36 | |
| 37 | '#address-cells': |
| 38 | const: 1 |
| 39 | |
| 40 | '#size-cells': |
| 41 | const: 0 |
| 42 | |
| 43 | patternProperties: |
| 44 | ^ethernet-phy@[a-f0-9]+$: |
| 45 | $ref: ethernet-phy.yaml# |
| 46 | |
| 47 | required: |
| 48 | - reg |
| 49 | - '#address-cells' |
| 50 | - '#size-cells' |
| 51 | |
| 52 | additionalProperties: true |