Received: by 10.223.176.5 with SMTP id f5csp1051996wra; Fri, 9 Feb 2018 11:34:47 -0800 (PST) X-Google-Smtp-Source: AH8x226iZ+1Q5VucihdsAXrBW9K6TBV7DkGZ0ydPihLmyvPfN3NOfxxtsn3P264T25XasrAlk06Y X-Received: by 2002:a17:902:2c43:: with SMTP id m61-v6mr2601540plb.387.1518204887065; Fri, 09 Feb 2018 11:34:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518204887; cv=none; d=google.com; s=arc-20160816; b=LxZG7cotlD5/m9WZ9flxvNZVQ+PU+rjdEeVYc8qJ9tE3Cxjk/zBwyaie9g1qPv6Unc Hk5HczG/5e7WjbeGBS7bGgiLNJB5d6Ne5bgZT4rfjouSOT/hu7mIw7CrEYyU3qXFSgrE xI5Dt+5uvCMxbSkuRtwnnl3KxscxelX0wTgNc0Vv0za8FA1BOu+BoTKxUQidhX1/dpI4 Zc8BOzNb5b3zBxiqjeix8Dl+scsHSPwgZn3szXZbxxF8s3Q14Fue4jjziSTfswVtl8co zpdVSKD59Q9zxNojLvqQMnrzncAdbfOg19PKRftGX5+fWAeRG+A3LRo2MIp0em5Xju7L tNbg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=1dAU1YAD4LB4McSfOPMBUWpqi2K3w49v8zKpY6AFmc4=; b=hvjySg+9dS6tHzjx/meLs4g3sBybxF/Is2hkJabsIIh5QZhoCuhjMo9ZLmbGhwy9r9 waalPXnhy0bxWDg1AnbMGflzSGdps9/MxiAlC0NPuYAeBQNxIBYYghMWS7stY/4P3p0s 4ZH/N1wEjST3+Igw27u9ZKOtf4zXnnTyhrvTvQ/ao4i/xyNqkp8Is6565ePMPNZNp8R/ c4132FqhDfnCfbxbW96i5hJQi06lV4xEbKxh8FqbK1Se0jJ261j6O5anfIbWlJrt0TFz jdMg3SeWo8FXM8FbbbxeKZYe4BPwAQhRwsVbzSsK/CYvfGFF96Ut3lE0aQDjqUqEUgSP dM3Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ef/FaTNn; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j11si2126647pff.406.2018.02.09.11.34.32; Fri, 09 Feb 2018 11:34:47 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ef/FaTNn; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752689AbeBITcg (ORCPT + 99 others); Fri, 9 Feb 2018 14:32:36 -0500 Received: from mail-lf0-f66.google.com ([209.85.215.66]:38800 "EHLO mail-lf0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752396AbeBITce (ORCPT ); Fri, 9 Feb 2018 14:32:34 -0500 Received: by mail-lf0-f66.google.com with SMTP id g72so12694426lfg.5; Fri, 09 Feb 2018 11:32:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=1dAU1YAD4LB4McSfOPMBUWpqi2K3w49v8zKpY6AFmc4=; b=ef/FaTNnGVyQx0j9TSt2kuM4d7mGSwRndnYD8Uy6OSqs63LgjOFeDuqAMNg2tQqDp1 JitEdv9uGNQDT5mHOGgj/AZlPCqS4dQpuYOoUQ02s1pAl8gPKDuOzDdcaVCvPh3oH9Fl khE+T4B+AoihPkUlk/Hj/abGHFgtUyYAaCdo3F1Y9fb3KhWuBkvYBf5jtyGxwhbsiAZC 3sQnFwAh/vZwiKnj0w8GevahBDrM7CLXtdDQZkCt3qwQKRefT90aIKz8eHLZx517J1u2 d0gKxfAvcjgTXgIq+tbuP6JjGGybc7j6o+PLeLqMvCJo596Om+2sAbQ3AkCJvRYQSLwd H6SA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=1dAU1YAD4LB4McSfOPMBUWpqi2K3w49v8zKpY6AFmc4=; b=UBq0iIY9suvgy02fnIZf+P9S4H9v6muBKLRdAYPI1Ca12UuuV/AAYz66X+byrfT0QE Rab/4/2Kb+aqsCxo+yoi3Mq8X9UHUqmDuVllWFzkK3oOE4+4oiLC9im0vkdV7eMEErdD wUUBHtfKX4QPzgo64UXYqH2HVBcqthDGv0ITkDZ0ZwIgL9fom3IHX84NSMaEqkhwVgJL U7zAKvwheAMcdYA+H9FeCxHBMcZedYbah5lpX2ePJtXiOfDVrld894F1eW6EzN0VVHCt OWZFmQ/2HNPG9Pv5xvd+WHgdO2WwoWISYZWa1FpvSzOFl8Qw+MoKeL7nif09i2Nxs4Vx FaDA== X-Gm-Message-State: APf1xPAt5mFXqkVytZjJ+H8VyTu6B0FU2X6mgmYZ8VO+SytgcDDPzyC7 CWSX0krGQQHuKTebED8d0jQ= X-Received: by 10.46.41.9 with SMTP id u9mr2847093lje.26.1518204752280; Fri, 09 Feb 2018 11:32:32 -0800 (PST) Received: from gmail.com (c-2ec27091-74736162.cust.telenor.se. [46.194.112.145]) by smtp.gmail.com with ESMTPSA id u8sm578063lfk.54.2018.02.09.11.32.30 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 09 Feb 2018 11:32:31 -0800 (PST) Date: Fri, 9 Feb 2018 20:32:25 +0100 From: Marcus Folkesson To: Wim Van Sebroeck , Guenter Roeck , Rob Herring , Mark Rutland , Carlo Caione , Kevin Hilman , Matthias Brugger , Barry Song , Maxime Ripard , Chen-Yu Tsai , Linus Walleij , Vladimir Zapolskiy , Sylvain Lemieux , Nicolas Ferre , Alexandre Belloni Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org Subject: Re: [PATCH 1/7] watchdog: sama5d4: make use of timeout-secs provided in devicetree Message-ID: <20180209193225.GA1932@gmail.com> References: <20180209192724.1227-1-marcus.folkesson@gmail.com> <20180209192724.1227-2-marcus.folkesson@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180209192724.1227-2-marcus.folkesson@gmail.com> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The summary email did not make it for some reason. However. All these drivers is using watchdog_init_timeout() to set timeout. If the timeout-parameter is set to an valid value, it will allways pick that and not even consider if timeout-secs is set in devicetree. Most of the patches will just remove the initial value for timeout-parameter. Some of the drivers allready has documented device-tree-bindings for timeout-secs (but will not work), add property for those which not. I wrote a similiar (tested) patch for imx2 and simply did the same to these drivers. These patches is *NOT* tested, so please review extra carefully. Taken from Documentation/watchdog/watchdog-kernel-api.txt: The watchdog_init_timeout function allows you to initialize the timeout field using the module timeout parameter or by retrieving the timeout-sec property from the device tree (if the module timeout parameter is invalid). Best practice is to set the default timeout value as timeout value in the watchdog_device and then use this function to set the user "preferred" timeout value. Best regards Marcus Folkesson