From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from www.linux-watchdog.org (www.linux-watchdog.org [185.87.125.42]) by smtp.subspace.kernel.org (Postfix) with ESMTP id A5FE545BE4 for ; Sun, 17 Dec 2023 15:43:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=linux-watchdog.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux-watchdog.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-watchdog.org header.i=@linux-watchdog.org header.b="c65JLxqb" Received: by www.linux-watchdog.org (Postfix, from userid 500) id 2C40740A42; Sun, 17 Dec 2023 16:34:48 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 www.linux-watchdog.org 2C40740A42 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-watchdog.org; s=odk20180602; t=1702827288; bh=f8FMduk32J5mDv1FWQOJ4O+W0eVJwGdxtVr779KbgCA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=c65JLxqbBryj5L5Cjk6qXkAeeqZjYi1ctWs52vEW93G7yXBnEqRDnH3fVRFjIlJZr Rb7TYDjopF/iOVsxq85TLogiFR/KRPUjaCb+PyzNUCZLHdtfc8kKJO0f/fDfAMUS9Z 8X7405lWqJEazTU+m1WPu9Xd2dLgNgxC5KYd65eY= Date: Sun, 17 Dec 2023 16:34:48 +0100 From: Wim Van Sebroeck To: Stefan Wahren Cc: Guenter Roeck , Florian Fainelli , Wim Van Sebroeck , bcm-kernel-feedback-list@broadcom.com, Phil Elwell , Ray Jui , Scott Branden , linux-watchdog@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] watchdog: bcm2835_wdt: Fix WDIOC_SETTIMEOUT handling Message-ID: <20231217153448.GB6196@www.linux-watchdog.org> References: <20231112173251.4827-1-wahrenst@gmx.net> Precedence: bulk X-Mailing-List: linux-watchdog@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-12-10) Hi Stefan, > Hi, > > Am 13.11.23 um 15:31 schrieb Guenter Roeck: > >On Sun, Nov 12, 2023 at 06:32:51PM +0100, Stefan Wahren wrote: > >>Users report about the unexpected behavior for setting timeouts above > >>15 sec on Raspberry Pi. According to watchdog-api.rst the ioctl > >>WDIOC_SETTIMEOUT shouldn't fail because of hardware limitations. > >>But looking at the code shows that max_timeout based on the > >>register value PM_WDOG_TIME_SET, which is the maximum. > >> > >>Since 664a39236e71 ("watchdog: Introduce hardware maximum heartbeat > >>in watchdog core") the watchdog core is able to handle this problem. > >> > >>This fix has been tested with watchdog-test from selftests. > >> > >>Link: https://bugzilla.kernel.org/show_bug.cgi?id=217374 > >>Fixes: 664a39236e71 ("watchdog: Introduce hardware maximum heartbeat in watchdog core") > >>Signed-off-by: Stefan Wahren > >Reviewed-by: Guenter Roeck > who takes care of this patch? I did. Kind regards, Wim.