The motorcomm phy (YT8531) supports the ability to adjust the drive
strength of the rx_clk/rx_data, and the default strength may not be
suitable for all boards. So add configurable options to better match
the boards.(e.g. StarFive VisionFive 2)
The first patch adds a description of dt-bingding, and the second patch adds
YT8531's parsing and settings for pad-driver-strength-cfg.
'Magic numbers' are used because we haven't been able to get real units
from motorcomm yet, but similar usage has been found in
Documentation/devicetree/bindings/net/qca,ar803x.yaml.
qca,clk-out-strength:
description: Clock output driver strength.
$ref: /schemas/types.yaml#/definitions/uint32
enum: [0, 1, 2]
Changes since v2:
Patch 2:
- Readjusted the order of YT8531_RGMII_xxx to below YTPHY_PAD_DRIVE_STRENGTH_REG (by Frank Sae)
- Reversed Christmas tree, sort these longest first, shortest last (by Andrew Lunn)
- Rebased on tag v6.4
Changes since v1:
Patch 1:
- Renamed "rx-xxx-driver-strength" to "motorcomm,rx-xxx-driver-strength" (by Frank Sae)
Patch 2:
- Added default values for rxc/rxd driver strength (by Frank Sea/Andrew Lunn)
- Added range checking when val is in DT (by Frank Sea/Andrew Lunn)
Previous versions:
v1 - https://patchwork.kernel.org/project/netdevbpf/cover/20230426063541.15378-1-samin.guo@xxxxxxxxxxxxxxxx
v2 - https://patchwork.kernel.org/project/netdevbpf/cover/20230505090558.2355-1-samin.guo@xxxxxxxxxxxxxxxx
Samin Guo (2):
dt-bindings: net: motorcomm: Add pad driver strength cfg
net: phy: motorcomm: Add pad drive strength cfg support
.../bindings/net/motorcomm,yt8xxx.yaml | 12 +++++
drivers/net/phy/motorcomm.c | 46 +++++++++++++++++++
2 files changed, 58 insertions(+)
base-commit: 3201bee3a7171617da7cdbce06c428fb628c9944
--
2.17.1
