Re: [PATCH net-next v2 1/2] dt-bindings: net: add DAPU Telecom DAP8211R(I) PHY binding

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The 'dapu' vendor prefix used in 'dapu,tx-inverted-clk' is not documented in vendor-prefixes.yaml.
--

--- Patch [1]: [PATCH net-next v2 1/2] dt-bindings: net: add DAPU Telecom DAP8211R(I) PHY binding ---
commit 05e0cd0742ef4792c4b9865b36c3662e45293902
Author: Artem Shimko <a.shimko.dev@gmail.com>

dt-bindings: net: add DAPU Telecom DAP8211R(I) PHY binding

This commit adds device tree binding documentation for the DAPU Telecom
DAP8211R(I) Gigabit Ethernet PHY, including properties for configuring
TX and RX clock delays and a vendor-specific flag for clock inversion.

> diff --git a/Documentation/devicetree/bindings/net/dapu,dap8211r.yaml b/Documentation/devicetree/bindings/net/dapu,dap8211r.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/dapu,dap8211r.yaml
[ ... ]
> +  tx-internal-delay-ps:
> +    description:
> +      RGMII TX clock delay in picoseconds (0 to maximum).
> +    multipleOf: 150
> +    maximum: 2250
> +    default: 1950
> +
> +  dapu,tx-inverted-clk:

[Severity: Low]
Is the dapu vendor prefix documented in vendor-prefixes.yaml?

The dt-schema tool strictly validates all vendor prefixes against the
registry. Because it appears to be missing from
Documentation/devicetree/bindings/vendor-prefixes.yaml, running
make dt_binding_check will result in a schema validation error for an
undocumented vendor prefix.

> +    $ref: /schemas/types.yaml#/definitions/flag
> +    description:
> +      If present, the RGMII TX clock to the MAC is inverted (180 degree
[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260716113805.593215-1-a.shimko.dev@gmail.com?part=1