Received: by 10.223.185.116 with SMTP id b49csp4876616wrg; Wed, 7 Mar 2018 02:33:21 -0800 (PST) X-Google-Smtp-Source: AG47ELtRqDWyJaUosoIBo+f1/LEWDi+pSh4G9bhdmo6gRc1mX6l76SAMzG/QC0nPUsJoF49oiyL/ X-Received: by 2002:a17:902:5401:: with SMTP id d1-v6mr20167382pli.176.1520418801255; Wed, 07 Mar 2018 02:33:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520418801; cv=none; d=google.com; s=arc-20160816; b=Xlv/fZKWPn7i1CSqY398gPlyk4NYGuUgqXrger649okbBZ9UnoSLK87L2HyahdW9+U /iPjJfkb7yZrzyBvhlglIqHvrM+cDpuEB6kvCxOUzIgNanNZj8B1qofdVOtXbcsLAo8U 3sp9XIyh8+F4TzhxWsnnyI5jgeJet/mid9v0+5+cuDSK4qk4lEAYggl3kvqE0v6tDwyb FkfjyXE//TK4O8cEzPm6C4oEzwum4vyOsnBy381C+D6lYNhCMP0UP148c6CFJ4nl/fH/ 8x9ECBR0vkLB0RzrxkTOVEt8RMZIeUORaghNrD3lfMq2If4vkNtR+KzDzNDvkTP2u62K 5d3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=tXFSgcbM5GVvXgnLOfRc8T/E5ZFMWhEVyAu5+oKBUD8=; b=Hx92cwngesmP3yRA88u/t6v8MyEeEUVuxg7tw9CF9B4wyUau9S+tNgIxhhwzX/R5bI e+VAoEgD3+8wIFr5ovSPW8E2vlb+fUt5BcGrKxrup3CGFMWEa+H1K2QFL9KL44O0yal6 tKv2u5WSJSBhvNOKbzO8iUbRXlsMGwnUjfu7+zkVSsKvkPGAa+ikAKTxRbO6fLArCdBo lmftPb7fJyvYPQ+2AQWr2E4IuYheCzZEkpULU6jDDhsf976dC+2eesh0kmZTCVztNzH5 BOnTC0Up01oUdzoz7r7D7Tvr4YBst58eH7fUmIz/+g2gxD6T3abn3lNLuPn3gc6DGDzI 7jLg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ndhJZR2X; 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 l85si13709065pfg.104.2018.03.07.02.33.05; Wed, 07 Mar 2018 02:33:21 -0800 (PST) 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=ndhJZR2X; 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 S1751244AbeCGKao (ORCPT + 99 others); Wed, 7 Mar 2018 05:30:44 -0500 Received: from mail-it0-f65.google.com ([209.85.214.65]:56100 "EHLO mail-it0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751132AbeCGKai (ORCPT ); Wed, 7 Mar 2018 05:30:38 -0500 Received: by mail-it0-f65.google.com with SMTP id n136so208818itg.5; Wed, 07 Mar 2018 02:30:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tXFSgcbM5GVvXgnLOfRc8T/E5ZFMWhEVyAu5+oKBUD8=; b=ndhJZR2XxZyX53kx3Bg1orb4UYqWjW93fFE2ATFQSDJJ4wXS/rohmrBlg2lpflYE7J /gem1yWeQKx19IxXh2Dr7u/GfBV8IZSYZAxr9DnAZ1fGJH7GGwcznq9axq3MwSj2bsJx uTTsmEIFbK01DhizjUO7F8O/PAve1qLCJPc8kMzFAKu+4/qWtQUtGWM5qR6XGYQSSQDY z33/8vUKug49jqzTj/2Ssep3OIbCkX7jwWj2jNTqpMC+A7wOe5KxDDe8z0WFzNVy4JdM auT2G6RC+sQMP3qdMyLlfRYzE6o4eeyzjU6U67ioK6l1i3Ze6O/7NZ546Vfsjv3l8DaE //Qw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tXFSgcbM5GVvXgnLOfRc8T/E5ZFMWhEVyAu5+oKBUD8=; b=qjXftrYV7V0tJ6dHz4TrAHNGYSQohcHnnYNleP3v4OR2pU+ByMIFuQc3lXMjHeVdCn LF+ZhRvEjKbTDxJfjpa9iY0KqkeM8c1KYbzjlJ7CuOSY5CjHH5s848+geq6gRmCQJmYN mLS6ueqU7rmHrkxhGcbqHbP4JHZ0w9mQxP0rHkZnlRo3cFYgy6bsVEff7xxGjmRrQaB+ at9pJpK+K7bKo1gV5LfOZxMZZMiyzddQHi7c84rp4t+hCF73o30tHzTxeF0S/YuFxKtG s2IyqRr/bi7nnafPvIQYR7i1gqvQkVojDF2F4q32kE/FRWj3w7TKMu1Q8OhptuM3Xzuh JiRQ== X-Gm-Message-State: AElRT7HFDMx/0Sb0o7VV5DkX0nFpptSNbFUs0xnUlCUY6JBbXWoYtqkN Sv0N/ybfwl/lxc5uU9DXuMtqLae28egvi/W1vQc= X-Received: by 10.36.77.143 with SMTP id l137mr23331762itb.118.1520418637697; Wed, 07 Mar 2018 02:30:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.183.17 with HTTP; Wed, 7 Mar 2018 02:30:37 -0800 (PST) In-Reply-To: References: <1519655769-25836-1-git-send-email-tmaimon77@gmail.com> <1519655769-25836-2-git-send-email-tmaimon77@gmail.com> From: Tomer Maimon Date: Wed, 7 Mar 2018 12:30:37 +0200 Message-ID: Subject: Re: [PATCH v4 1/2] dt-binding: timer: document NPCM7xx timer DT bindings To: Joel Stanley Cc: Rob Herring , Mark Rutland , Daniel Lezcano , Thomas Gleixner , Avi Fishman , Brendan Higgins , devicetree , Linux Kernel Mailing List , OpenBMC Maillist Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sorry for the late response On 2 March 2018 at 03:51, Joel Stanley wrote: > Hi Tomer, > > On Tue, Feb 27, 2018 at 1:06 AM, Tomer Maimon wrote: >> Added device tree binding documentation for Nuvoton NPCM7xx timer. >> >> Signed-off-by: Tomer Maimon >> Acked-by: Rob Herring >> Reviewed-by: Brendan Higgins >> --- >> .../bindings/timer/nuvoton,npcm7xx-timer.txt | 25 ++++++++++++++++++++++ >> 1 file changed, 25 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/timer/nuvoton,npcm7xx-timer.txt >> >> diff --git a/Documentation/devicetree/bindings/timer/nuvoton,npcm7xx-timer.txt b/Documentation/devicetree/bindings/timer/nuvoton,npcm7xx-timer.txt >> new file mode 100644 >> index 000000000000..c5150522e618 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/timer/nuvoton,npcm7xx-timer.txt >> @@ -0,0 +1,25 @@ >> +Nuvoton NPCM7xx timer > > Would it make more sense to all this Nuvoton NPCM Timer? This way the > name stays generic for when you add other systems. > we cant promise the timer will stay the same in the next generation, I will leave this for NPCM7xx >> + >> +Nuvoton NPCM7xx have three timer modules, each timer module provides five 24-bit >> +timer counters. > > > I notice the timer has a register in the middle of it that is used for > the watchdog. Should we describe this in the same binding? Even if we > just add some text that adds > > ... and one watchdog register. > I'm not sure, because the binding is only for the timer I dont think I need to describe what is the register contains >> + >> +Required properties: >> +- compatible : "nuvoton,npcm750-timer" for Poleg NPCM750. >> +- reg : Offset and length of the register set for the device. >> +- interrupts : Contain the timer interrupt with flags for >> + falling edge. >> + >> +Required clocking property, have to be one of: >> +- clocks : phandle of timer reference clock. >> +- clock-frequency : The frequency in Hz of the clock that drives the NPCM7xx >> + timer (usually 25000000). >> + >> +Example: >> + >> +timer@f0008000 { >> + compatible = "nuvoton,npcm750-timer"; >> + interrupts = ; >> + reg = <0xf0008000 0x1000>; > > This can probably be <0xf0008000 0x50>, as tthe timer hardware only > has registers up to base + 0x50. Thanks, I will modify it in the next version, waiting fro more comments. > >> + clocks = <&clk NPCM7XX_CLK_TIMER>; >> +}; >> + >> -- >> 2.14.1 >> Cheers, Tomer