kernel/linux.git/Documentation/devicetree/bindings/net/microchip,lan966x-switch.yaml, branch v6.19.9

dt-bindings: net: Drop unneeded quotes

2023-03-23T04:54:19+00:00

Cleanup bindings dropping unneeded quotes. Once all these are fixed, checking for this can be enabled in yamllint. Acked-by: Marc Kleine-Budde # for bindings/net/can Reviewed-by: Krzysztof Kozlowski Acked-by: Jernej Skrabec Acked-by: Florian Fainelli Reviewed-by: Steen Hegelund Signed-off-by: Rob Herring Acked-by: Nobuhiro Iwamatsu # for bindings/net/toshiba,visconti-dwmac.yaml Reviewed-by: Heiko Stuebner #rockchip Link: https://lore.kernel.org/r/20230320233758.2918972-1-robh@kernel.org Signed-off-by: Jakub Kicinski

dt-bindings: net: lan966x: fix example

2022-05-05T03:40:19+00:00

In commit 4fdabd509df3 ("dt-bindings: net: lan966x: remove PHY reset") the PHY reset was removed, but I failed to remove it from the example. Fix it. Fixes: 4fdabd509df3 ("dt-bindings: net: lan966x: remove PHY reset") Reported-by: Rob Herring Signed-off-by: Michael Walle Acked-by: Rob Herring Link: https://lore.kernel.org/r/20220503132038.2714128-1-michael@walle.cc Signed-off-by: Jakub Kicinski

dt-bindings: net: lan966x: remove PHY reset

2022-04-30T12:09:25+00:00

The PHY reset was intended to be a phandle for a special PHY reset driver for the integrated PHYs as well as any external PHYs. It turns out, that the culprit is how the reset of the switch device is done. In particular, the switch reset also affects other subsystems like the GPIO and the SGPIO block and it happens to be the case that the reset lines of the external PHYs are connected to a common GPIO line. Thus as soon as the switch issues a reset during probe time, all the external PHYs will go into reset because all the GPIO lines will switch to input and the pull-down on that signal will take effect. So even if there was a special PHY reset driver, it (1) won't fix the root cause of the problem and (2) it won't fix all the other consumers of GPIO lines which will also be reset. It turns out, the Ocelot SoC has the same weird behavior (or the lack of a dedicated switch reset) and there the problem is already solved and all the bits and pieces are already there and this PHY reset property isn't not needed at all. There are no users of this binding. Just remove it. Signed-off-by: Michael Walle Signed-off-by: David S. Miller

dt-bindings: net: lan966x: Extend with the ptp external interrupt.

2022-04-27T11:03:17+00:00

Extend dt-bindings for lan966x with ptp external interrupt. This is generated when an external 1pps signal is received on the ptp pin. Signed-off-by: Horatiu Vultur Signed-off-by: David S. Miller

dt-bindings: net: lan966x: Extend with the ptp interrupt

2022-02-01T14:18:43+00:00

Extend dt-bindings for lan966x with ptp interrupt. This is generated when doing 2-step timestamping and the timestamp can be read from the FIFO. Signed-off-by: Horatiu Vultur Signed-off-by: David S. Miller

dt-bindings: net: lan966x: Extend with the analyzer interrupt

2021-12-20T11:44:05+00:00

Extend dt-bindings for lan966x with analyzer interrupt. This interrupt can be generated for example when the HW learn/forgets an entry in the MAC table. Acked-by: Rob Herring Reviewed-by: Vladimir Oltean Signed-off-by: Horatiu Vultur Signed-off-by: David S. Miller

dt-bindings: net: lan966x: Add additional properties for lan966x

2021-12-02T12:23:10+00:00

This patch updates the dt-bindings for lan966x switch. It adds the properties 'additionalProperties' and 'unevaluatedProperties' for ethernet-ports and ports nodes. In this way it is not possible to add more properties to these nodes. Signed-off-by: Horatiu Vultur Signed-off-by: David S. Miller

dt-bindings: net: lan966x: Add lan966x-switch bindings

2021-11-29T12:58:38+00:00

Document the lan966x switch device driver bindings Signed-off-by: Horatiu Vultur Signed-off-by: David S. Miller