Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1498883imm; Tue, 10 Jul 2018 02:56:33 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfu8b7gq/Z1bOp92jGfjLFSNKaJ1D/DhL6GU9kGixeI/LpTecZq9xIsDBBBKS37wUGWvFOV X-Received: by 2002:a17:902:b581:: with SMTP id a1-v6mr11817179pls.338.1531216593301; Tue, 10 Jul 2018 02:56:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531216593; cv=none; d=google.com; s=arc-20160816; b=VJgBHRKPd1vEFm4IvO4BFSPPW4P3TOEkMuksF72WMmdrs5+qzN3hCpiR0yB+/aLpVa uHpYEsyPUinRFMlnOqX6ONiSjglFf0vxJYgiHM9IAK4PtfbNE/wZfXocu9cEooeEACxn QdiXxaWInQ3HyaR2HclCS2omwBlp2Aizet7g2N7XmO/ApAXHdERbmfGyhxjDNnBnsLfb F1HOdFtvrEfkRGWjRnxd86cescnent0g6CsG9MVIaFJ8nehoO5xF9J5vfuBStJbzW2mC SiiItSGr1jtgfMz8E1xI+3KvGu/dTrAHiBux+IlsFTjw8hr/eCg20drOMj5fLX3ytDFh FKbg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:mime-version:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:cc:to :from:arc-authentication-results; bh=NQTM6E+aNGPpOJ3d6IHQ8ZKkyrMdkfBQaSSmP1W+NWw=; b=yNt2Z5HIJMEM4Ms+WYI0a3l0xKI8YH3sRaNchQriqq9rvGFY/PyeplZIyeqdh9GmCK gZ8NbZgIH8Xt2WUiOUELybakyAXKGZ5Kc0hhXuDo65Zfha0gSduOHsf/0ignRvb0iLXW zjADFuGp/xxohzII5TW4dy7tveYJqE4TYoLr2a5nhwGKlw0yw1Di94C+UGuVMmuA9Aem 7nVKmE20rniHCkNOgHKQR91zXBkx/s6IegHKprpRiC4vb4EJbgBwn/uqnAWv5ywD+Fhp XFV2kUBKojuhNygjjztJtnW6rSUxtXgUzQVoakEMwqthwVS33pyWIcU/UXiP2L2ArA/W 0NZw== 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 l61-v6si16358154plb.507.2018.07.10.02.56.18; Tue, 10 Jul 2018 02:56:33 -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 S933292AbeGJJzR convert rfc822-to-8bit (ORCPT + 99 others); Tue, 10 Jul 2018 05:55:17 -0400 Received: from enterprise01.smtp.diehl.com ([193.201.238.219]:29534 "EHLO enterprise01.smtp.diehl.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932743AbeGJJyL (ORCPT ); Tue, 10 Jul 2018 05:54:11 -0400 X-$ESA-Groupmapping: true X-IronPort-AV: E=Sophos;i="5.51,334,1526335200"; d="scan'208";a="53147488" From: Denis OSTERLAND To: "mark.rutland@arm.com" , "robh+dt@kernel.org" CC: "linux-kernel@vger.kernel.org" , "alexandre.belloni@bootlin.com" , "m.grzeschik@pengutronix.de" , "devicetree@vger.kernel.org" , "a.zummo@towertech.it" , "linux-rtc@vger.kernel.org" , "kernel@pengutronix.de" , Denis OSTERLAND Subject: [PATCH v4 5/5] rtc: isl1219: add device tree docu Thread-Topic: [PATCH v4 5/5] rtc: isl1219: add device tree docu Thread-Index: AQHUGDKQQPZVuDcxn0uq52IAiz//4g== Date: Tue, 10 Jul 2018 09:44:15 +0000 Message-ID: <20180710090710.9066-6-Denis.Osterland@diehl.com> References: <20180710090710.9066-1-Denis.Osterland@diehl.com> In-Reply-To: <20180710090710.9066-1-Denis.Osterland@diehl.com> Accept-Language: de-DE, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-mailer: Evolution 3.18.5.2-0ubuntu3.2 MIME-Version: 1.0 X-TrailerSkip: 1 X-GBS-PROC: byQFdw3ukCM+zy1/poiPc2UJHLf8TT72+4rSTBxpvIGVPWTBT4fhNdyadF9C9KMn X-TNEFEvaluated: 1 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Denis Osterland The devicetree documentation for the ISL1219 device tree binding is added with an short example. It is not a trivial device, because it supports two interrupt souces. Signed-off-by: Denis Osterland --- .../devicetree/bindings/rtc/isil,isl1219.txt | 29 +++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 Documentation/devicetree/bindings/rtc/isil,isl1219.txt diff --git a/Documentation/devicetree/bindings/rtc/isil,isl1219.txt b/Documentation/devicetree/bindings/rtc/isil,isl1219.txt new file mode 100644 index 000000000000..f26f1e9d4bde --- /dev/null +++ b/Documentation/devicetree/bindings/rtc/isil,isl1219.txt @@ -0,0 +1,29 @@ +Intersil ISL1219 I2C RTC/Alarm chip with event in + +ISL1219 has additional pins EVIN and #EVDET for tamper detection. + +Required properties supported by the device: + + - "compatible": must be "isil,isl1219" + - "reg": I2C bus address of the device + +Optional properties: + + - "interrupt-names": list which may contains "irq" and "evdet" + - "interrupt-parent", "interrupts", "interrupts-extended": + for passing the interrupt line of the SoC connected to #IRQ pin + and #EVDET pin of the RTC chip. + - "isil,ev-evienb": if present bit can be set to disable event input pull-up + + +Example isl1219 node with #IRQ pin connected to SoC gpio1 pin12 + and #EVDET pin connected to SoC gpio2 pin 24: + + isl1219: rtc@68 { + compatible = "isil,isl1219"; + reg = <0x68>; + interrupt-names = "irq", "evdet"; + interrupts-extended = <&gpio1 12 IRQ_TYPE_EDGE_FALLING>, + <&gpio2 24 IRQ_TYPE_EDGE_FALLING>; + }; + -- 2.18.0 Diehl Connectivity Solutions GmbH Gesch?ftsf?hrung: Horst Leonberger Sitz der Gesellschaft: N?rnberg - Registergericht: Amtsgericht N?rnberg: HRB 32315 ___________________________________________________________________________________________________ Der Inhalt der vorstehenden E-Mail ist nicht rechtlich bindend. Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Informieren Sie uns bitte, wenn Sie diese E-Mail faelschlicherweise erhalten haben. Bitte loeschen Sie in diesem Fall die Nachricht. Jede unerlaubte Form der Reproduktion, Bekanntgabe, Aenderung, Verteilung und/oder Publikation dieser E-Mail ist strengstens untersagt. The contents of the above mentioned e-mail is not legally binding. This e-mail contains confidential and/or legally protected information. Please inform us if you have received this e-mail by mistake and delete it in such a case. Each unauthorized reproduction, disclosure, alteration, distribution and/or publication of this e-mail is strictly prohibited.