The reset which is used by the switch to reset the switch core has many
different side effects. It is not just a switch reset. Thus don't treat it
as one, but just issue the reset early during boot.

Michael Walle (3):
  reset: microchip-sparx5: issue a reset on startup
  dt-bindings: net: sparx5: don't require a reset line
  net: lan966x: make reset optional

 .../bindings/net/microchip,sparx5-switch.yaml |  2 --
 .../ethernet/microchip/lan966x/lan966x_main.c |  3 ++-
 drivers/reset/reset-microchip-sparx5.c        | 22 ++++++++++++++-----
 3 files changed, 19 insertions(+), 8 deletions(-)

-- 
2.30.2

Am 2022-08-26 13:56, schrieb Michael Walle:
> The reset which is used by the switch to reset the switch core has many
> different side effects. It is not just a switch reset. Thus don't treat 
> it
> as one, but just issue the reset early during boot.
> 
> Michael Walle (3):
>   reset: microchip-sparx5: issue a reset on startup
>   dt-bindings: net: sparx5: don't require a reset line
>   net: lan966x: make reset optional
> 
>  .../bindings/net/microchip,sparx5-switch.yaml |  2 --
>  .../ethernet/microchip/lan966x/lan966x_main.c |  3 ++-
>  drivers/reset/reset-microchip-sparx5.c        | 22 ++++++++++++++-----
>  3 files changed, 19 insertions(+), 8 deletions(-)

Philipp, you could just patch #1, I guess. I'd then
resend patches #2 and #3 to the netdev ML targetting net-next.
As long as the device tree itself isn't changed, there should
be no dependency between these two.

-michael