From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755998AbbAWRC7 (ORCPT ); Fri, 23 Jan 2015 12:02:59 -0500 Received: from bh-25.webhostbox.net ([208.91.199.152]:40690 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754585AbbAWRCz (ORCPT ); Fri, 23 Jan 2015 12:02:55 -0500 Message-ID: <54C27EBB.9000200@roeck-us.net> Date: Fri, 23 Jan 2015 09:02:51 -0800 From: Guenter Roeck User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Doug Anderson CC: Jisheng Zhang , Wim Van Sebroeck , Heiko Stuebner , Lunxue Dai , Dinh Nguyen , "linux-watchdog@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 1/2] watchdog: dw_wdt: pat the watchdog before enabling it References: <1421882243-3631-1-git-send-email-dianders@chromium.org> <20150122132200.4729d38b@xhacker> <54C270C4.4010407@roeck-us.net> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-CTCH-PVer: 0000001 X-CTCH-Spam: Suspect X-CTCH-VOD: Unknown X-CTCH-Flags: 512 X-CTCH-RefID: str=0001.0A020204.54C27EBE.03CF,ss=1,re=0.001,recu=0.000,reip=0.000,cl=1,cld=1,fgs=512,sb=0 X-CTCH-Score: 0.001 X-CTCH-ScoreCust: 0.000 X-CTCH-Rules: C_4847, X-CTCH-SenderID: linux@roeck-us.net X-CTCH-SenderID-Flags: 0 X-CTCH-SenderID-TotalMessages: 30 X-CTCH-SenderID-TotalSpam: 0 X-CTCH-SenderID-TotalSuspected: 1 X-CTCH-SenderID-TotalConfirmed: 0 X-CTCH-SenderID-TotalBulk: 0 X-CTCH-SenderID-TotalVirus: 0 X-CTCH-SenderID-TotalRecipients: 0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: mailgid no entry from get_relayhosts_entry X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/23/2015 08:20 AM, Doug Anderson wrote: > Guenter, > > On Fri, Jan 23, 2015 at 8:03 AM, Guenter Roeck wrote: >> On 01/22/2015 09:09 AM, Doug Anderson wrote: >>> >>> Jisheng, >>> >>> On Wed, Jan 21, 2015 at 9:22 PM, Jisheng Zhang >>> wrote: >>>> >>>> Dear Doug, >>>> >>>> On Wed, 21 Jan 2015 15:17:22 -0800 >>>> Doug Anderson wrote: >>>> >>>>> On some dw_wdt implementations the "top" register may be initted to 0 >>>>> at bootup. In such a case, each "pat" of the watchdog will reset the >>>>> timer to 0xffff. That's pretty short. >>>> >>>> >>>> + Guenter Roeck >>>> >>>> This should have been fixed by dfa07141e7a792("watchdog: dw_wdt: >>>> initialise >>>> TOP_INIT in dw_wdt_set_top()") >>> >>> >>> I will admit that I'm testing on a tree that doesn't have your patch >>> (I'm on a 3.14 kernel with lots of backports). ...but I did try >>> cherry-picking your patch before I wrote up mine and it didn't fix my >>> problem. I believe that the watchdog that's in Rockchip rk3288 must >>> be a slightly different version of the IP block than you're working >>> with. >>> >>> Specifically I see the register WDT_TORR that has an offset of 0x4. >>> That's the RANGE_REG in your code. It shows bits 3:0 set the timeout >>> period (0 = 0xffff and 15 = 0x7fffffff). It shows bits 31:4 as >>> "reserved". >>> >> Not sure where that leaves us. Does that mean the driver supports different >> hardware with different register sets ? > > Apparently so. I've only seen the documentation from rk3288, but it's > clearly different than what you saw. > >> Should that be documented in the >> driver, > > Probably not a terrible idea. > >> and should we have (or do we need) different compatible statements for those >> variants, and conditional code in the driver ? > > I'm not sure we actually need any conditional code. I've put the > other patch on rk3288 and it didn't hurt to write those reserved bits. > I also can't quite believe that the extra pat will hurt on other > hardware. > > >> And does it mean we need both patches, at least for some of the hardware >> variants ? If so, what happens if those patches are applied and the >> resulting >> driver runs on the other hardware ? > > I think it should be fine. > > > Do you want me to spin my patch and add some extra comments (but > otherwise keep it roughly unchanged?). We can get Jisheng to add his > Tested-by... > Yes, that would be great. Thanks, Guenter