Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Michael Walle <michael@walle.cc>
To:     "David S . Miller" <davem@davemloft.net>,
        Eric Dumazet <edumazet@google.com>,
        Jakub Kicinski <kuba@kernel.org>,
        Paolo Abeni <pabeni@redhat.com>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Lars Povlsen <lars.povlsen@microchip.com>,
        Steen Hegelund <Steen.Hegelund@microchip.com>,
        Horatiu Vultur <horatiu.vultur@microchip.com>,
        Philipp Zabel <p.zabel@pengutronix.de>
Cc:     UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
        devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org, Michael Walle <michael@walle.cc>
Subject: [PATCH 0/3] reset: microchip-sparx5: fix the broken switch reset
Date:   Fri, 26 Aug 2022 13:56:04 +0200
Message-Id: <20220826115607.1148489-1-michael@walle.cc>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

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