From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758735AbcEFNLy (ORCPT ); Fri, 6 May 2016 09:11:54 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:36148 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757596AbcEFNLx (ORCPT ); Fri, 6 May 2016 09:11:53 -0400 Date: Fri, 6 May 2016 15:11:56 +0200 From: Arthur LAMBERT To: linux-kernel@vger.kernel.org Subject: uboot watchdog and linux kernel Message-ID: <20160506131156.GB4072@arthur-bzh> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I am working on custom imx6 board with linux 3.14.52. I am trying to use hardware watchdog from uboot. I am able to enable with success the watchdog in uboot. Booting with an invalid kernel will reboot the board after timeout. Problem is in linux side. I have some random reboot sometimes. I am not able to understand where is the code to ping the uboot hardware watchdog in linux kernel. * There is no /dev/watchdog entry associate to my uboot watchdog (there are entries only for pmic watchdog) * Only code where I find ping of uboot watchdog seems to be in imx2 watchdog driver. But this driver is not enable in my kernel config. But if noone is pinging the watchdog, why I am able to play with my board during few hours sometimes ?? Thanks, Arthur.