Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2093347yba; Fri, 19 Apr 2019 12:00:54 -0700 (PDT) X-Google-Smtp-Source: APXvYqxqI1s8+UzZlezpNn2zPLkr7HjV8ngzvUthbWMq0W3KySfbdxTvQbXvHsFeFonme8KZP0Pz X-Received: by 2002:a63:be02:: with SMTP id l2mr5481648pgf.48.1555700454057; Fri, 19 Apr 2019 12:00:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555700454; cv=none; d=google.com; s=arc-20160816; b=de9QN6RAWKi9lj+BulubGYl32rHo34HYITuf/ddCg258iWp2ZO3qrJfQ8Z0JpA0QDX DLsDOwwQ0LNyhpQ7XDJiuMRwFhfClHc7H+RkFZRf4lYYrX166etpKuex06hPDrXLHQ4h BsjLF9ymM/B8Hsdz29sqb+5i6EjIMG4PuRga33GhrSjqL7MayRPd4wYGnOR042fgct5z 3Ovo7AJRIXQchr/0IbYA/0k9gbEx+FhveknGOY24SfwCvLQ/keDCRScMF6xglaTWLch1 aXBkUmKf6FiX4Sw/VSl1ynh+Jjh0ldjeB+QWGBieuixIsLv3tQYuNE1cn6IWMAetF5xJ 1tUA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=4khKcbPHbyYmHxfaGSQOC6E3MogU3rXvT1zdzGYqzyQ=; b=OPbTYhSUJHa4Zyq60md8fQGzx12BAT7pn8In4pMoM2x174d59j+qZj4LndDRFWVzPu MmnUGQkFmlWpow8lQo3ZwoLzSQSGvfu+8wyW4DE106Cf33HNxMDWXuG2ZzUuNi+NnG8E /iJan2siQIV4lX35E3Jcso7vwp3o3QOU2ERoo3vfs00MXIBOmD0H8UXTQpT+17b9OuG7 Z6HDPlgiLGWSnBsgoLUtURVisOy9275fKKWY3wcadZfJsCemG2gsvZYgW3ZJocNIWmIV Ij/uCznNk+0MDUSdHtDaiuJi9aR2MbLB3xNvrj8e/0BmN2Qg263Qbjfftz/QChW5uNFF 9rVw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=GSHSNKKL; 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 a5si6089550pff.39.2019.04.19.12.00.37; Fri, 19 Apr 2019 12:00:54 -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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=GSHSNKKL; 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 S1727992AbfDSS6X (ORCPT + 99 others); Fri, 19 Apr 2019 14:58:23 -0400 Received: from mail-yw1-f66.google.com ([209.85.161.66]:46139 "EHLO mail-yw1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728080AbfDSS6W (ORCPT ); Fri, 19 Apr 2019 14:58:22 -0400 Received: by mail-yw1-f66.google.com with SMTP id u3so1707496ywa.13; Fri, 19 Apr 2019 11:58:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=4khKcbPHbyYmHxfaGSQOC6E3MogU3rXvT1zdzGYqzyQ=; b=GSHSNKKLkKCvhgOu+BiCf5EWjajcbAZACGOUVS7wVUI3xuW/zap6QkBSpO62OJXgmc xmj8u/L6zLZ51n3S+HCOxXSXB3M/lgVyR9puo5iaAP39xoQSkQc5nXj/05fp0viQxMQa 0Z/JBcVPJLihLBY6O1Eee5o1iIJLZNTe4Fft+FxUoWSxgkfcR9lCxZ16HqS9NSBytOCl zjoNMY7xn1muS3HTGdnF/bH9b3Bq/QCuXBMuigH00bXIvPBKpOYzb9x8INmKPKM3sKBl vUoqFzBKAM+RkE1mrGbreoKLJVf51iPoWrl4uQacKrflTSxArr4XK/X6dXUQrqr+9mz9 Kjdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=4khKcbPHbyYmHxfaGSQOC6E3MogU3rXvT1zdzGYqzyQ=; b=EoFakf3s0RUP9kuNNXlYruS2U/+mjDKY/eoGhydKNaG7sKSTPt8HuwT/73LQUTWspN krfm83Cv3QpeEwhD/yLW4omPxbAAgLmdyX323qSLhCcZVmUrt/071XZs2TnB91AB8Evl jZnUJWuOFMzowM5pHtnj3gKUnMmf+15DEfWJSFP4rV4wUPVN6FvbAj4F5aQUjJokEHYz ynclXULtDa5LGox38RUbQGRvsZqnPVfnM1vdJN2e+NcGA9F4+P96AErzzf2es+EJq666 Z/YiEWh9157FYv1xmQdQwyjZG5cvvsG/A1jnAH4vuHjcZsd9eCdt3sPsv+uzZJy1BBsm dc+g== X-Gm-Message-State: APjAAAW9rRQibYnxyc7K4KsTOm3+Npv4aM+tJCwFLRHzUG8cHF9MVdlG ic1ZklsVi7C2RgwOKerk76qikfnta0QHKk29TA0= X-Received: by 2002:a81:a6c5:: with SMTP id d188mr4406292ywh.46.1555700301010; Fri, 19 Apr 2019 11:58:21 -0700 (PDT) MIME-Version: 1.0 References: <20190411154534.25563-1-peron.clem@gmail.com> <20190411154534.25563-3-peron.clem@gmail.com> In-Reply-To: <20190411154534.25563-3-peron.clem@gmail.com> From: =?UTF-8?B?Q2zDqW1lbnQgUMOpcm9u?= Date: Fri, 19 Apr 2019 21:00:42 +0200 Message-ID: Subject: Re: [PATCH v2 2/3] arm64: dts: allwinner: h6: add r_watchog node To: Rob Herring , Maxime Ripard , Chen-Yu Tsai , Icenowy Zheng Cc: devicetree , linux-kernel , linux-arm-kernel , linux-sunxi Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Thu, 11 Apr 2019 at 17:34, Cl=C3=A9ment P=C3=A9ron wrote: > > Allwinner H6 has a r_watchdog similar to A64. > > Declare it in the device-tree. > > Signed-off-by: Cl=C3=A9ment P=C3=A9ron > --- > 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/bo= ot/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 =3D <1>; > }; > > + r_watchdog: watchdog@7020400 { > + compatible =3D "allwinner,sun50i-a64-wdt", > + "allwinner,sun6i-a31-wdt"; > + reg =3D <0x07020400 0x20>; > + interrupts =3D ; > + }; 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 =3D "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. Thanks, Clement > + > r_intc: interrupt-controller@7021000 { > compatible =3D "allwinner,sun50i-h6-r-intc", > "allwinner,sun6i-a31-r-intc"; > -- > 2.17.1 >