From patchwork Fri Mar 8 11:29:35 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bastian Hecht X-Patchwork-Id: 2236851 Return-Path: X-Original-To: patchwork-linux-sh@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork1.kernel.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by patchwork1.kernel.org (Postfix) with ESMTP id 1658A4006E for ; Fri, 8 Mar 2013 11:29:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752809Ab3CHL3r (ORCPT ); Fri, 8 Mar 2013 06:29:47 -0500 Received: from mail-ee0-f52.google.com ([74.125.83.52]:41334 "EHLO mail-ee0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752522Ab3CHL3r (ORCPT ); Fri, 8 Mar 2013 06:29:47 -0500 Received: by mail-ee0-f52.google.com with SMTP id b15so901721eek.25 for ; Fri, 08 Mar 2013 03:29:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:x-mailer:in-reply-to :references; bh=gWdajM41L/KSA4bXAJTI3qkZCOvr074/WMZxHcO3s+c=; b=k1qfVfUq2QDFWh72yhhtpmO+PLjNvhG3LftSpqdsQvTyGHgXUdLNbcb8kb0+NjkuTj CfQ+4RodYz94spyDl++Y1Td68cb8/bop7J3/r1y/R4KYz2RXX/OBRVWEbAaWL8x2Jgps xXUa2R8aGpMiFePRht5XHpQUSn/ydh5S5urZJk2l0zvL4am9onk/bxeY4B1ycuQ539qf EEgIEjJOAROFOOePEqvP6aNrEfCIMQWQgYG2e/Uj9ykjlRiSfHoIg7qiyNDVVC65BBEJ 3HrOC5OYs6Lk41dj0kl0jQgVSmoWzrulk5orroYDlTYartECdkUw1t/eV13OndhoQoNS ejFA== X-Received: by 10.14.202.71 with SMTP id c47mr4430418eeo.39.1362742185871; Fri, 08 Mar 2013 03:29:45 -0800 (PST) Received: from localhost.localdomain (p4FD23A77.dip.t-dialin.net. [79.210.58.119]) by mx.google.com with ESMTPS id q42sm7197626eem.14.2013.03.08.03.29.44 (version=TLSv1.1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Mar 2013 03:29:45 -0800 (PST) From: Bastian Hecht To: linux-sh@vger.kernel.org Cc: Magnus Damm , Paul Mundt , linux-arm-kernel@lists.infradead.org, Mark Rutland , Sergei Shtylyov Subject: [PATCH v2 1/7] ARM: shmobile: Define DT bindings for timer devices Date: Fri, 8 Mar 2013 12:29:35 +0100 Message-Id: <1362742181-19111-2-git-send-email-hechtb+renesas@gmail.com> X-Mailer: git-send-email 1.7.9.5 In-Reply-To: <1362742181-19111-1-git-send-email-hechtb+renesas@gmail.com> References: <1362742181-19111-1-git-send-email-hechtb+renesas@gmail.com> Sender: linux-sh-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-sh@vger.kernel.org The SH mobile series currently features 3 timer devices in the kernel: Compare Match Timer (CMT), Timer Unit (TMU) and MTU2. These devices share register layout characteristics amongst each that enable us to define common DT bindings for them. Signed-off-by: Bastian Hecht --- v2: - Split the bindings into an extra patch - Renamed the linux specific clocksource-rating and added an explanation why it is in the bindings - Using the postfix -timer in the compatible string .../devicetree/bindings/timer/renesas,timer.txt | 45 ++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 Documentation/devicetree/bindings/timer/renesas,timer.txt diff --git a/Documentation/devicetree/bindings/timer/renesas,timer.txt b/Documentation/devicetree/bindings/timer/renesas,timer.txt new file mode 100644 index 0000000..2c001bf --- /dev/null +++ b/Documentation/devicetree/bindings/timer/renesas,timer.txt @@ -0,0 +1,45 @@ +* Renesas SH Mobile Timer + +Bindings for several timer devices from Renesas including CMT, TMU and MTU2. + +Required properties: +- compatible : Should be "renesas,{device}-timer", + whereas device is "cmt", "tmu" or "mtu2". +- reg : Address and length of the register set for the device +- interrupts : Timer interrupt +- renesas,device-id : The ID of the timer device +- renesas,channel-id : The channel ID of the timer device +- renesas,source-quality : The viability to use this device as a free + running clock. From 0 (do not use) to 10 (best possible clock). +- renesas,event-quality : The viability to use this device as an event + generator. From 0 (do not use) to 10 (best possible clock). + +The properties renesas,{source,event}-quality reflect the situation that the +usability of the timer devices depend on the location within their SoCs. E.g. +the power domain affinty affects power management, some mux-ed lines might be +preferred to be assigned to other functions and other constraints. + +Example for CMT1 channel 0 on the R8A7740 SoC: + + timer@e6138010 { + compatible = "renesas,cmt-timer"; + interrupt-parent = <&intca>; + reg = <0xe6138010 0xc>; + interrupts = <0x0b00>; + renesas,device-id = <1>; + renesas,channel-id = <0>; + renesas,source-quality = <3>; + renesas,event-quality = <3>; + }; + +Example for TMU0 channel 1 on the SH7372 SoC: + timer@fff60014 { + compatible = "renesas,tmu-timer"; + interrupt-parent = <&intcs>; + reg = <0xfff60014 0xc>; + interrupts = <0xea0>; + renesas,device-id = <0>; + renesas,channel-id = <1>; + renesas,source-quality = <4>; + renesas,event-quality = <0>; + };