Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753191AbbKWFEL (ORCPT ); Mon, 23 Nov 2015 00:04:11 -0500 Received: from mx0a-0016f401.pphosted.com ([67.231.148.174]:15912 "EHLO mx0a-0016f401.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750703AbbKWFEI (ORCPT ); Mon, 23 Nov 2015 00:04:08 -0500 Date: Mon, 23 Nov 2015 12:59:53 +0800 From: Jisheng Zhang To: Sebastian Hesselbarth CC: , , , , , , , , , , Subject: Re: [PATCH RESEND 1/8] arm: dts: berlin2q: add watchdog nodes Message-ID: <20151123125953.5c30a0ef@xhacker> In-Reply-To: <564F8062.8070609@gmail.com> References: <1447672194-483-1-git-send-email-jszhang@marvell.com> <1447672194-483-2-git-send-email-jszhang@marvell.com> <564E3549.2050700@gmail.com> <20151120113414.1aa1e48e@xhacker> <564F8062.8070609@gmail.com> X-Mailer: Claws Mail 3.13.0 (GTK+ 2.24.28; 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:,, definitions=2015-11-23_04:,, signatures=0 X-Proofpoint-Spam-Details: rule=inbound_notspam policy=inbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1507310000 definitions=main-1511230094 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2906 Lines: 92 On Fri, 20 Nov 2015 21:19:46 +0100 Sebastian Hesselbarth wrote: > On 20.11.2015 04:34, Jisheng Zhang wrote: > > On Thu, 19 Nov 2015 21:47:05 +0100 > > Sebastian Hesselbarth wrote: > >> On 16.11.2015 12:09, Jisheng Zhang wrote: > >>> The Marvell Berlin BG2Q has 3 watchdogs which are compatible with the > >>> snps,dw-wdt driver sit in the sysmgr domain. This patch adds the > >>> corresponding device tree nodes. > >>> > >>> Signed-off-by: Jisheng Zhang > >>> --- > >>> arch/arm/boot/dts/berlin2q.dtsi | 24 ++++++++++++++++++++++++ > >>> 1 file changed, 24 insertions(+) > >>> > >>> diff --git a/arch/arm/boot/dts/berlin2q.dtsi b/arch/arm/boot/dts/berlin2q.dtsi > >>> index a3ecde5..fac4315 100644 > >>> --- a/arch/arm/boot/dts/berlin2q.dtsi > >>> +++ b/arch/arm/boot/dts/berlin2q.dtsi > >>> @@ -483,6 +483,30 @@ > >>> ranges = <0 0xfc0000 0x10000>; > >>> interrupt-parent = <&sic>; > >>> > >>> + wdt0: watchdog@1000 { > >>> + compatible = "snps,dw-wdt"; > >>> + reg = <0x1000 0x100>; > >>> + clocks = <&refclk>; > >>> + interrupts = <0>; > >>> + status = "disabled"; > >> > >> as the watchdogs are internal and cannot be clock gated > >> at all, how about we remove the status = "disabled" and > >> make them always available? > > > > there are two issues here: > > > > 1. the dw-wdt can't support multiple variants now. I have rewrite the driver > > with watchdog core supplied framework, but the patch isn't sent out and > > may be need time to clean up and review. > > Ok. > > > 2. not all dw-wdt devices are available and functional. This depends on > > board design and configuration. > > I understand that "board design and configuration" may hinder the wdt > to issue a hard reset. But all others are able to issue a soft reset > or just an interrupt, right? > > So, I still don't see why we should disable wdt nodes by default > except for the driver issue above. > > > So IMHO status=disabled and patch5-8 is necessary, what do you think? > > No. I'd agree to enable wdt0 by default and leave wdt[1,2] disabled > because of the driver issue. Patches 5-8 only enable wdt0 anyway. That's fine. > > As soon as the driver issue is resolved, we enable all wdt nodes > unconditionally. I will submit patch for the wdt driver and hope it will be merged in v4.5. Thanks, Jisheng > > Sebastian > > >> I have applied patches 1-4 with the status property removed. > >> This also renders patches 5-8 useless. > >> > >> So, for now tentatively > >> > >> Appled to berlin/dt and berlin64/dt respectivly > >> > >> with status property removed. > >> > >> Sebastian > >> > > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/