From patchwork Thu Nov 17 11:49:05 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Fabrizio Castro X-Patchwork-Id: 13046654 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C3C6BC433FE for ; Thu, 17 Nov 2022 11:49:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239483AbiKQLtv (ORCPT ); Thu, 17 Nov 2022 06:49:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52602 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239943AbiKQLtX (ORCPT ); Thu, 17 Nov 2022 06:49:23 -0500 Received: from relmlie6.idc.renesas.com (relmlor2.renesas.com [210.160.252.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id EB14A317C3; Thu, 17 Nov 2022 03:49:15 -0800 (PST) X-IronPort-AV: E=Sophos;i="5.96,171,1665414000"; d="scan'208";a="142991195" Received: from unknown (HELO relmlir5.idc.renesas.com) ([10.200.68.151]) by relmlie6.idc.renesas.com with ESMTP; 17 Nov 2022 20:49:15 +0900 Received: from mulinux.example.org (unknown [10.226.93.80]) by relmlir5.idc.renesas.com (Postfix) with ESMTP id 4C63040031D7; Thu, 17 Nov 2022 20:49:11 +0900 (JST) From: Fabrizio Castro To: Wim Van Sebroeck , Guenter Roeck , Philipp Zabel , Geert Uytterhoeven Cc: Fabrizio Castro , Biju Das , linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org, Chris Paterson , Biju Das , linux-renesas-soc@vger.kernel.org, Laurent Pinchart , Jacopo Mondi Subject: [PATCH 0/2] Reset related fixes for rzg2l_wdt Date: Thu, 17 Nov 2022 11:49:05 +0000 Message-Id: <20221117114907.138583-1-fabrizio.castro.jz@renesas.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-renesas-soc@vger.kernel.org Dear All, this series addresses a couple of issues found with the rzg2l_wdt driver: 1) on the RZ/Five SoC it was observed that changing the timeout wouldn't reset the system as expected 2) on the RZ/V2M SoC it was observed that calling into the restart callback from the reboot command wouldn't reboot the system straight away As it turns out, the RZ/Five watchdog IP requires the module clock to be supplied during a reset. On RZ/V2M, a specific procedure has to be followed to reset the watchdog IP. This series comes with two patches, one to fix the problem affecting RZ/Five, and one to fix the problem affecting RZ/V2M. Thanks, Fab Fabrizio Castro (1): watchdog: rzg2l_wdt: Handle TYPE-B reset for RZ/V2M Lad Prabhakar (1): watchdog: rzg2l_wdt: Issue a reset before we put the PM clocks drivers/watchdog/rzg2l_wdt.c | 45 +++++++++++++++++++++++++++++++----- 1 file changed, 39 insertions(+), 6 deletions(-)