From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753625AbbA0Ejj (ORCPT ); Mon, 26 Jan 2015 23:39:39 -0500 Received: from mx0a-0016f401.pphosted.com ([67.231.148.174]:38426 "EHLO mx0a-0016f401.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752117AbbA0Eje (ORCPT ); Mon, 26 Jan 2015 23:39:34 -0500 Date: Tue, 27 Jan 2015 12:36:23 +0800 From: Jisheng Zhang To: Guenter Roeck CC: Doug Anderson , 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 Message-ID: <20150127123623.7e93b5f4@xhacker> In-Reply-To: <54C70F17.7070003@roeck-us.net> References: <1421882243-3631-1-git-send-email-dianders@chromium.org> <20150122132200.4729d38b@xhacker> <20150126142210.4cd0b33f@xhacker> <20150127114403.71736c3f@xhacker> <54C70F17.7070003@roeck-us.net> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.33,0.0.0000 definitions=2015-01-27_02:2015-01-27,2015-01-26,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1501270051 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 26 Jan 2015 20:07:51 -0800 Guenter Roeck wrote: > On 01/26/2015 07:44 PM, Jisheng Zhang wrote: > > Dear Doug, > > > > On Mon, 26 Jan 2015 09:01:37 -0800 > > Doug Anderson wrote: > > > >> Jisheng, > >> > >> On Sun, Jan 25, 2015 at 10:22 PM, Jisheng Zhang > >> wrote: > >>>> 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". > >>> > >>> Could you please dump registers' value at offset 0xf4 and 0xf8 if you > >>> don't mind? > >> > >> Those are not documented in the user manual that I have, but: > >> > >>>>> r(0xff8000f4) > >> 0x10000a02 > >>>>> r(0xff8000f8) > >> 0x3130332a > > > Hi Jisheng, > > This translates to ascii "103*". How does it translate to "1.02a" ? aha, yes. wdt version is v1.03* ;) > > > Thanks. Now I got some information about your platform: > > > > wdt version: v1.02a > > > > WDT_DUAL_TOP is configured as false, so there's no TOP_INIT > > WDT_DFLT_TOP is configured as 0, so it will timeout soon. > > > Any chance you can provide the bit map for the register reporting > those flags ? will do in Doug's v2 patch thread Thanks, Jisheng