linux_dsm_epyc7002/Documentation/devicetree/bindings/phy/calxeda-combophy.yaml
Rob Herring 086e9074f5 dt-bindings: Remove more cases of 'allOf' containing a '$ref'
Another round of 'allOf' removals that came in this cycle.

json-schema versions draft7 and earlier have a weird behavior in that
any keywords combined with a '$ref' are ignored (silently). The correct
form was to put a '$ref' under an 'allOf'. This behavior is now changed
in the 2019-09 json-schema spec and '$ref' can be mixed with other
keywords. The json-schema library doesn't yet support this, but the
tooling now does a fixup for this and either way works.

This has been a constant source of review comments, so let's change this
treewide so everyone copies the simpler syntax.

Signed-off-by: Rob Herring <robh@kernel.org>
2020-06-11 13:50:43 -06:00

51 lines
1.2 KiB
YAML

# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/phy/calxeda-combophy.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Calxeda Highbank Combination PHYs binding for SATA
description: |
The Calxeda Combination PHYs connect the SoC to the internal fabric
and to SATA connectors. The PHYs support multiple protocols (SATA,
SGMII, PCIe) and can be assigned to different devices (SATA or XGMAC
controller).
Programming the PHYs is typically handled by those device drivers,
not by a dedicated PHY driver.
maintainers:
- Andre Przywara <andre.przywara@arm.com>
properties:
compatible:
const: calxeda,hb-combophy
'#phy-cells':
const: 1
reg:
maxItems: 1
phydev:
description: device ID for programming the ComboPHY.
$ref: /schemas/types.yaml#/definitions/uint32
maximum: 31
required:
- compatible
- reg
- phydev
- '#phy-cells'
additionalProperties: false
examples:
- |
combophy5: combo-phy@fff5d000 {
compatible = "calxeda,hb-combophy";
#phy-cells = <1>;
reg = <0xfff5d000 0x1000>;
phydev = <31>;
};