Commit 8453c88c authored by Christian Marangi's avatar Christian Marangi Committed by David S. Miller
Browse files

dt-bindings: net: document ethernet PHY package nodes



Document ethernet PHY package nodes used to describe PHY shipped in
bundle of 2-5 PHY. The special node describe a container of PHY that
share common properties. This is a generic schema and PHY package
should create specialized version with the required additional shared
properties.

Example are PHY packages that have some regs only in one PHY of the
package and will affect every other PHY in the package, for example
related to PHY interface mode calibration or global PHY mode selection.

The PHY package node MUST declare the base address used by the PHY driver
for global configuration by calculating the offsets of the global PHY
based on the base address of the PHY package.

Each reg of the PHYs defined in the PHY package node is absolute and
describe the real address of the Ethernet PHY on the bus.

Signed-off-by: default avatarChristian Marangi <ansuelsmth@gmail.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent b63cc733
Loading
Loading
Loading
Loading
+52 −0
Original line number Diff line number Diff line
# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
%YAML 1.2
---
$id: http://devicetree.org/schemas/net/ethernet-phy-package.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Ethernet PHY Package Common Properties

maintainers:
  - Christian Marangi <ansuelsmth@gmail.com>

description:
  PHY packages are multi-port Ethernet PHY of the same family
  and each Ethernet PHY is affected by the global configuration
  of the PHY package.

  Each reg of the PHYs defined in the PHY package node is
  absolute and describe the real address of the Ethernet PHY on
  the MDIO bus.

properties:
  $nodename:
    pattern: "^ethernet-phy-package@[a-f0-9]+$"

  reg:
    minimum: 0
    maximum: 31
    description:
      The base ID number for the PHY package.
      Commonly the ID of the first PHY in the PHY package.

      Some PHY in the PHY package might be not defined but
      still occupy ID on the device (just not attached to
      anything) hence the PHY package reg might correspond
      to a not attached PHY (offset 0).

  '#address-cells':
    const: 1

  '#size-cells':
    const: 0

patternProperties:
  ^ethernet-phy@[a-f0-9]+$:
    $ref: ethernet-phy.yaml#

required:
  - reg
  - '#address-cells'
  - '#size-cells'

additionalProperties: true