Re: [PATCH net-next v20 1/3] dt-bindings: net: Document Motorcomm YT8824 PHY package

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: unit-address mismatch with reg property in example
--

commit 21a69a542a09b6b2571122c2f9f0dadf390d6020
Author: Kyle Switch <kyle.switch@motor-comm.com>

dt-bindings: net: Document Motorcomm YT8824 PHY package

This commit introduces device tree binding documentation for the Motorcomm
YT8824 Ethernet PHY, describing it as a package of 4 PHYs.

> diff --git a/Documentation/devicetree/bindings/net/motorcomm,yt8824.yaml b/Documentation/devicetree/bindings/net/motorcomm,yt8824.yaml
> new file mode 100644
> index 0000000000000..9737364744a07
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/motorcomm,yt8824.yaml

[ ... ]

> +examples:
> +  - |
> +    mdio {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        ethernet-phy-package@0 {
> +            #address-cells = <1>;
> +            #size-cells = <0>;
> +            compatible = "motorcomm,yt8824-package";
> +            reg = <9>;

[Severity: Low]
Does this unit-address cause a validation warning during make
dt_binding_check? The node name uses @0, but the reg property is assigned
<9>. This mismatch typically triggers a unit_address_vs_reg warning from
the dtc compiler.

> +
> +            phy-mode = "internal";

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260917131441.3428554-1-kyle.switch@motor-comm.com?part=1