github-mirror/linux
1
0
Fork 0
mirror of https://github.com/torvalds/linux.git synced 2026-11-07 06:17:02 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity Graph

dt-bindings: net: x-powers: add AC200/AC300 EPHY packages

Browse Source 
The AC200 and AC300 contain compatible Fast Ethernet link PHYs which
report the same Clause 22 identifier and use the same link-side register
layout. Their package control paths differ: AC200 control registers are
accessed through the I2C register interface of the companion IC, while
the AC300 control range is at a second Clause 22 address fixed at 16 plus
the link address.

Describe both variants as Ethernet PHY packages. The package reg value is
the link PHY base address and the child supplies the documented PHY ID,
because the identification registers cannot be read until package setup
has completed. The AC300 driver reaches its control range with the PHY
package offset helpers. The AC200 package instead references the companion
IC described by the separately submitted x-powers,ac200 MFD binding. Its
I2C interface provides access to the package controls.

Give fixed hardware variant-specific compatibles. Also provide an ACx00
compatible for systems which can contain either package, with one packed
NVMEM field containing calibration in bits 3 through 0, the AC300 selector
in bit 8 and its low-calibration selector in bit 9. Such a description
contains the potential resources for both backends; the driver consumes
only those selected by the configuration field.

Document the little-endian encoding and two-byte full configuration,
while allowing a one-byte calibration value for fixed AC200 packages.

Describe the package clock, supply and optional xMII receive-clock
inversion needed by some integrations. A fixed AC200 package may omit the
NVMEM field and use its internal calibration copy. Limit both the package
and child link-PHY addresses in AC300-capable descriptions to 0 through 7
so the control address remains in the documented range 16 through 23.

Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Link: https://patch.msgid.link/20260909-submit-acx00-of-dynamic-v1-v11-1-eb45e89ef918@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
This commit is contained in:
James Hilliard 2026-09-09 18:15:37 -06:00 committed by Jakub Kicinski
parent a952507ca0
commit 783f6f1fdc
1 changed files with 170 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

170
Documentation/devicetree/bindings/net/x-powers,acx00-ephy-package.yaml Normal file
View File

@ -0,0 +1,170 @@
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/net/x-powers,acx00-ephy-package.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: X-Powers AC200 and AC300 Ethernet PHY packages
maintainers:
- James Hilliard <james.hilliard1@gmail.com>
description:
The AC200 and AC300 contain compatible Fast Ethernet PHY blocks which report
the same Clause 22 PHY ID and use the same link-side register layout. The
package control paths differ. AC200 package control registers are accessed
through the companion IC's I2C register interface, while AC300 control
registers occupy a second Clause 22 address fixed at 16 plus the link PHY
address.
Systems with a known package use the corresponding AC200 or AC300 compatible.
Systems which can contain either package use the ACx00 compatible and a
packed NVMEM configuration field to select the backend at runtime.
The link PHY cannot report its ID until the package control sequence has
completed, so its child node supplies the documented PHY ID. The package and
child use the same base address. The AC200 driver programs that address into
the package, while the AC300 driver derives its control address from it.
properties:
compatible:
enum:
- x-powers,ac200-ephy-package
- x-powers,ac300-ephy-package
- x-powers,acx00-ephy-package
reg:
maximum: 31
clocks:
maxItems: 1
description: AC300 input clock, running at 24, 25, or 27 MHz
vcc-supply:
description:
3.3 V package supply. This is connected to EPHY_VCC on AC200 and VCC1
on AC300.
nvmem-cells:
maxItems: 1
description:
Packed little-endian EPHY configuration value, with the least-significant
byte first. Bits 3 through 0 contain the analog calibration code, bits 7
through 4 are reserved, bit 8 selects AC300 when set and AC200 when clear,
and bit 9 requests the AC300 low-calibration tuning sequence. Bits 15
through 10 are reserved.
AC300 and selectable ACx00 packages require the full configuration
field, including bits 8 and 9 even when their values are zero, returned
as two bytes. A fixed AC200 package may provide a one-byte calibration
value or a two-byte configuration with bit 8 clear, or omit the cell
and use its internal eFuse calibration copy.
nvmem-cell-names:
const: configuration
x-powers,ac200:
$ref: /schemas/types.yaml#/definitions/phandle
description:
Phandle to the AC200 companion IC described by the x-powers,ac200 MFD
binding. Its I2C interface provides access to the package control
registers used to power and configure the Ethernet PHY.
x-powers,xmii-rx-clock-inverted:
type: boolean
description:
Invert the xMII receive clock inside the PHY. This is required by some
SoC integrations, including the Allwinner H6 AC200 connection.
patternProperties:
^ethernet-phy@[a-f0-9]+$:
$ref: ethernet-phy.yaml#
properties:
compatible:
const: ethernet-phy-id0044.1400
required:
- compatible
unevaluatedProperties: false
required:
- compatible
- vcc-supply
dependentRequired:
nvmem-cells: [ nvmem-cell-names ]
allOf:
- $ref: ethernet-phy-package.yaml#
- if:
properties:
compatible:
const: x-powers,ac200-ephy-package
then:
properties:
clocks: false
required:
- x-powers,ac200
- if:
properties:
compatible:
const: x-powers,ac300-ephy-package
then:
properties:
x-powers,ac200: false
required:
- clocks
- nvmem-cells
- nvmem-cell-names
- if:
properties:
compatible:
const: x-powers,acx00-ephy-package
then:
required:
- clocks
- nvmem-cells
- nvmem-cell-names
- x-powers,ac200
- if:
properties:
compatible:
enum:
- x-powers,ac300-ephy-package
- x-powers,acx00-ephy-package
then:
properties:
reg:
maximum: 7
patternProperties:
^ethernet-phy@[a-f0-9]+$:
properties:
reg:
maximum: 7
unevaluatedProperties: false
examples:
- |
mdio {
#address-cells = <1>;
#size-cells = <0>;
ethernet-phy-package@0 {
compatible = "x-powers,acx00-ephy-package";
reg = <0>;
#address-cells = <1>;
#size-cells = <0>;
clocks = <&pwm 5>;
vcc-supply = <&reg_3v3>;
nvmem-cells = <&ephy_configuration>;
nvmem-cell-names = "configuration";
x-powers,ac200 = <&ac200>;
ethernet-phy@0 {
compatible = "ethernet-phy-id0044.1400";
reg = <0>;
};
};
};
...