Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3757779yba; Tue, 23 Apr 2019 09:07:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqyF1btpBd5Vpr2ADC6RxrgOeqxmyYz5+KEIrMUYNooWgW2AmVbTU/cTC30CuSu1xvpBQ72y X-Received: by 2002:a63:1a5d:: with SMTP id a29mr20780076pgm.262.1556035648520; Tue, 23 Apr 2019 09:07:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556035648; cv=none; d=google.com; s=arc-20160816; b=xQikZr8A01rpyPeXmgqS4eMd3eOGLaDbNfraIGHr9/OxZ94m1YSP/lEO90rpm4xeSP 4iNOylIAsWMQf1b0//4HJ4IXAXyVIALnLkMCarGobDErxFbFMie+9D/kWyCjoXAOLEmW p2k6BpzQz9jALKmPO2CCqMfAQ8tsoK0OTeFZaajcRt2XHhBsTzHD0Hei+TR4sxUkU3zp +fLR/vPtdUyRAAfLpq244ndg96GSx3kL0SA69cA5PsUuY732zPpA1/LPYWx8AfDuMLUf vp7vmVlG/4xhpS1+i50R/FJjhpD2AAVwrSR3aUcqPHw4KEcEivEGJatJaPfttbFB9yu/ DQLA== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=lQHCibV4pjcd9Rz8FkZoXVN8R/XpA68Q491EE8qbq+U=; b=Y0ZQcpgh/Jsia9iPBeIXvcQoDYz/b9eCDlZ3zEBqw2o65jNkWa3FHLbSCp+g7xyjzT nCXBw6RmvEAo+FYBU/acSkznqyy+/l4EC3IxbAXAv1EOS6NgSX3OWKAd0xuNf5Cj70UJ W4IV51MY1MpiArhxvFDm3aVnqw2HGWu8Fy+D3SAXCazWk4+2Mbll8zJMoVQAI2lJfTNd RQnr1q8AF+lU65br1AmtnO1s6e5+NUiMaEP48Ew+wzBJ9Vr7JpfnXmfOmbvSKqxrQvQm dv4dG2Fa1+2cKFU6u+DBcPCoHX9ZrlbVbHPCkBToZ28TKf/JrzOJhE/Cv4L1LgenObZX zdlw== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f1si16894499pff.158.2019.04.23.09.07.11; Tue, 23 Apr 2019 09:07:28 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728534AbfDWQFs convert rfc822-to-8bit (ORCPT + 99 others); Tue, 23 Apr 2019 12:05:48 -0400 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:57891 "EHLO relay9-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726655AbfDWQFs (ORCPT ); Tue, 23 Apr 2019 12:05:48 -0400 X-Originating-IP: 90.89.68.76 Received: from localhost (lfbn-1-10718-76.w90-89.abo.wanadoo.fr [90.89.68.76]) (Authenticated sender: maxime.ripard@bootlin.com) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id D06DBFF811; Tue, 23 Apr 2019 16:05:45 +0000 (UTC) Date: Tue, 23 Apr 2019 18:05:45 +0200 From: Maxime Ripard To: =?utf-8?B?Q2zDqW1lbnQgUMOpcm9u?= Cc: Rob Herring , Chen-Yu Tsai , Icenowy Zheng , devicetree , linux-kernel , linux-arm-kernel , linux-sunxi Subject: Re: [PATCH v2 2/3] arm64: dts: allwinner: h6: add r_watchog node Message-ID: <20190423160545.muolantrdppz35rz@flea> References: <20190411154534.25563-1-peron.clem@gmail.com> <20190411154534.25563-3-peron.clem@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 19, 2019 at 09:00:42PM +0200, Cl?ment P?ron wrote: > Hi, > > On Thu, 11 Apr 2019 at 17:34, Cl?ment P?ron wrote: > > > > Allwinner H6 has a r_watchdog similar to A64. > > > > Declare it in the device-tree. > > > > Signed-off-by: Cl?ment P?ron > > --- > > arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 7 +++++++ > > 1 file changed, 7 insertions(+) > > > > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi > > index 5c2f5451227b..66dc684a378e 100644 > > --- a/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi > > +++ b/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi > > @@ -622,6 +622,13 @@ > > #reset-cells = <1>; > > }; > > > > + r_watchdog: watchdog@7020400 { > > + compatible = "allwinner,sun50i-a64-wdt", > > + "allwinner,sun6i-a31-wdt"; > > + reg = <0x07020400 0x20>; > > + interrupts = ; > > + }; > > I have set the same compatible as A64 because regarding the User > Manual they have exactly the same memory mapping. > However we don't know really if it's the same IP version, maybe there > will be an errata one day. > So I would like to know if it's better to define the h6-wdt also > compatible = "allwinner,sun50i-h6-wdt", "allwinner,sun50i-a64-wdt", > "allwinner,sun6i-a31-wdt"; > > I would say Yes, but with this logic we would have to had a new > compatible each time there is a new SoC. Why not just having the A31 compatible? Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com