dt-bindings: phy: Convert st,spear1310-miphy to DT schema

Convert the ST SPEAr MIPHY PHY binding to DT schema format. It's a
straight forward conversion.

Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
Link: https://lore.kernel.org/r/20250607212629.744191-1-robh@kernel.org
Signed-off-by: Vinod Koul <vkoul@kernel.org>
pull/1279/head
Rob Herring (Arm) 2025-06-07 16:26:28 -05:00 committed by Vinod Koul
parent 3ed7be1275
commit ea54c9d157
2 changed files with 53 additions and 15 deletions

View File

@ -0,0 +1,53 @@
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/phy/st,spear1310-miphy.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: ST SPEAr miphy
maintainers:
- Pratyush Anand <pratyush.anand@gmail.com>
description:
ST Microelectronics SPEAr miphy is a phy controller supporting PCIe and SATA.
properties:
compatible:
enum:
- st,spear1310-miphy
- st,spear1340-miphy
reg:
maxItems: 1
misc:
description: Phandle for the syscon node to access misc registers.
$ref: /schemas/types.yaml#/definitions/phandle
'#phy-cells':
description: >
Cell[0] indicates interface type: 0 = SATA, 1 = PCIe.
const: 1
phy-id:
description: Instance id of the phy. Required when multiple PHYs are present.
$ref: /schemas/types.yaml#/definitions/uint32
required:
- compatible
- reg
- misc
- '#phy-cells'
additionalProperties: false
examples:
- |
miphy@1000 {
compatible = "st,spear1310-miphy";
reg = <0x1000 0x100>;
misc = <&syscon>;
#phy-cells = <1>;
phy-id = <0>;
};

View File

@ -1,15 +0,0 @@
ST SPEAr miphy DT details
=========================
ST Microelectronics SPEAr miphy is a phy controller supporting PCIe and SATA.
Required properties:
- compatible : should be "st,spear1310-miphy" or "st,spear1340-miphy"
- reg : offset and length of the PHY register set.
- misc: phandle for the syscon node to access misc registers
- #phy-cells : from the generic PHY bindings, must be 1.
- cell[1]: 0 if phy used for SATA, 1 for PCIe.
Optional properties:
- phy-id: Instance id of the phy. Only required when there are multiple phys
present on a implementation.