lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 17 Nov 2022 11:49:05 +0000 From: Fabrizio Castro <fabrizio.castro.jz@...esas.com> To: Wim Van Sebroeck <wim@...ux-watchdog.org>, Guenter Roeck <linux@...ck-us.net>, Philipp Zabel <p.zabel@...gutronix.de>, Geert Uytterhoeven <geert+renesas@...der.be> Cc: Fabrizio Castro <fabrizio.castro.jz@...esas.com>, Biju Das <biju.das.jz@...renesas.com>, linux-watchdog@...r.kernel.org, linux-kernel@...r.kernel.org, Chris Paterson <Chris.Paterson2@...esas.com>, Biju Das <biju.das@...renesas.com>, linux-renesas-soc@...r.kernel.org, Laurent Pinchart <laurent.pinchart@...asonboard.com>, Jacopo Mondi <jacopo@...ndi.org> Subject: [PATCH 0/2] Reset related fixes for rzg2l_wdt 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(-) -- 2.34.1
Powered by blists - more mailing lists