[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250131-omniscient-obedient-locust-9313c0@krzk-bin>
Date: Fri, 31 Jan 2025 08:31:37 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Chris Packham <chris.packham@...iedtelesis.co.nz>
Cc: lee@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, tsbogend@...ha.franken.de,
hkallweit1@...il.com, linux@...linux.org.uk, sander@...nheule.net,
markus.stockhausen@....de, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, linux-mips@...r.kernel.org
Subject: Re: [PATCH v5 1/4] dt-bindings: net: Add Realtek MDIO controller
On Fri, Jan 31, 2025 at 02:01:48PM +1300, Chris Packham wrote:
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> + reg:
> + maxItems: 1
> +
> +patternProperties:
> + '^mdio-bus@[0-4]$':
4 or 5 buses?
> + $ref: mdio.yaml#
> +
> + properties:
> + reg:
> + maxItems: 1
> +
> + required:
> + - reg
> +
> + patternProperties:
> + '^ethernet-phy@[a-f0-9]+$':
> + type: object
> + $ref: ethernet-phy.yaml#
> +
> + properties:
> + realtek,port:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + The MDIO communication on the RTL9300 is abstracted by the switch. At
> + the software level communication uses the switch port to address the
> + PHY with the actual MDIO bus and address having been setup via the
> + parent mdio-bus and reg property.
maximum: 8 ?
also property should be required or you miss here default.
Best regards,
Krzysztof
Powered by blists - more mailing lists