Received: by 10.223.185.116 with SMTP id b49csp940985wrg; Fri, 16 Feb 2018 09:36:57 -0800 (PST) X-Google-Smtp-Source: AH8x227NPtkTVJzbgj75s1xl9Q8YTAnzSWXbkDjN2QapgU8OWeidO0CkfMMI0FId2SjL1WtsdN1m X-Received: by 10.98.54.197 with SMTP id d188mr2723835pfa.234.1518802616951; Fri, 16 Feb 2018 09:36:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518802616; cv=none; d=google.com; s=arc-20160816; b=nzyjKCADjcyQ1KKx2nIQ2F1bLClm89d7gDtio6+bSL0BajsLakAxYokup2oyJPiNrq MlXWysEYh3VTz12Y3u88MvyyLyelmvITMocWKw5X8qBdBRosKTsi+uTXqK0Unjau2cZW 3s5JtZrNNrkQuewDvxFiS6+tqJDBWThDn4DtSUcLYElWFeZlta4C4T3kK/NiziWWogQa c2gMEDzdKX+imcRJdGM2eb4YOEPoAmtlNm66QXoaJgyivl36jOuWSe+yJOOXpgDppxuD IJC6c5Xdeeq12GRRtma0kQrDfQr+slcU/6Re3MsJ8dipKMCl7s2oMNBuLC+b4ow2W2pj lVBw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dmarc-filter:dkim-signature:dkim-signature :arc-authentication-results; bh=z8AKurLSPhMtKvNPfNep2sm3TzsiSZsLeI1TBKWDPAw=; b=zGeGJbTn6IhqcIQf3l8hCL/tyxNKlLlT4o/5J3n3zazK23Ha3AydwJ0kskLu0TGBf4 9n5HlSo2zJAJtfejvU3wbtNgq23dT1n0MfnDaKzkbnFDuxD6CjiqDViN56ulTzOPKT32 gPMe5h2XY/iCP+TBL/IyaK+xPCsAOuueDJxh24BsJnjpwOwJQtPxvlhfG60swXURZty1 A7+IZHC7JD7q0K+bgcdx+AMKNmmV/OLYccltGoqQkw4WTsdwN4GmiI0dF+kBu7xhXCim uqCIMnqlGZHt+I2brO4hdzuyiwIRqyg6o+QFqDR2af+oGwdoJaJYqKx8k75QDVQli0IU Z14A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=eYZyF8LL; dkim=pass header.i=@codeaurora.org header.s=default header.b=A++aWWK3; 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 x189si3026147pgb.216.2018.02.16.09.36.42; Fri, 16 Feb 2018 09:36:56 -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=@codeaurora.org header.s=default header.b=eYZyF8LL; dkim=pass header.i=@codeaurora.org header.s=default header.b=A++aWWK3; 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 S1756020AbeBOV15 (ORCPT + 99 others); Thu, 15 Feb 2018 16:27:57 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:37666 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755992AbeBOV1v (ORCPT ); Thu, 15 Feb 2018 16:27:51 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id F341F60D81; Thu, 15 Feb 2018 21:27:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1518730071; bh=6qg26uLj5NziFLniHpDBIcYJleg2+WhTdkgjp33oLU0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=eYZyF8LLh480kJxM5T0mynV2L01SoFUD55Obz/Ol8oGSSXNRbzRITxjjeVIHOBlsc PENkRzA5So4QBez4rcO771RG2dA096WQLRCWGRTBTGuuikrgQwvZ+sIMqhm6/UtuiS /PWL55ItxFyU0PLy62ciqoM4TSYEfNXkzpa+thhs= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from codeaurora.org (i-global254.qualcomm.com [199.106.103.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: ilina@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 7587A60F72; Thu, 15 Feb 2018 21:27:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1518730070; bh=6qg26uLj5NziFLniHpDBIcYJleg2+WhTdkgjp33oLU0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=A++aWWK3w10ftov/gXAePcjqOECI7m8YlduhiYAWAcGjq3RPRGd5CTvgqHZowXUQ0 hFetGJhizF1HjETTvyQNQ7y+bJA+rRn1s8k8rfhuneMpVrw+LkyCvNNlA5PSp320o9 EO7WJze4maBVkQItUKrACDh6ueApplKyl1JS4s8k= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 7587A60F72 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=ilina@codeaurora.org From: Lina Iyer To: tglx@linutronix.de, jason@lakedaemon.net, marc.zyngier@arm.com Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, rnayak@codeaurora.org, asathyak@codeaurora.org, Lina Iyer , devicetree@vger.kernel.org Subject: [PATCH v7 2/2] dt-bindings/interrupt-controller: pdc: describe PDC device binding Date: Thu, 15 Feb 2018 14:27:42 -0700 Message-Id: <20180215212742.4675-3-ilina@codeaurora.org> X-Mailer: git-send-email 2.16.1 In-Reply-To: <20180215212742.4675-1-ilina@codeaurora.org> References: <20180215212742.4675-1-ilina@codeaurora.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Archana Sathyakumar Add device binding documentation for the PDC Interrupt controller on QCOM SoC's like the SDM845. The interrupt-controller can be used to sense edge low interrupts and wakeup interrupts when the GIC is non-operational. Cc: devicetree@vger.kernel.org Signed-off-by: Archana Sathyakumar Signed-off-by: Lina Iyer --- .../bindings/interrupt-controller/qcom,pdc.txt | 78 ++++++++++++++++++++++ 1 file changed, 78 insertions(+) create mode 100644 Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.txt diff --git a/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.txt b/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.txt new file mode 100644 index 000000000000..0b2c97ddb520 --- /dev/null +++ b/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.txt @@ -0,0 +1,78 @@ +PDC interrupt controller + +Qualcomm Technologies Inc. SoCs based on the RPM Hardened architecture have a +Power Domain Controller (PDC) that is on always-on domain. In addition to +providing power control for the power domains, the hardware also has an +interrupt controller that can be used to help detect edge low interrupts as +well detect interrupts when the GIC is non-operational. + +GIC is parent interrupt controller at the highest level. Platform interrupt +controller PDC is next in hierarchy, followed by others. Drivers requiring +wakeup capabilities of their device interrupts routed through the PDC, must +specify PDC as their interrupt controller and request the PDC port associated +with the GIC interrupt. See example below. + +Properties: + +- compatible: + Usage: required + Value type: + Definition: Should contain "qcom,-pdc" + - "qcom,sdm845-pdc": For SDM845 + +- reg: + Usage: required + Value type: + Definition: Specifies the base physical address for PDC hardware. + +- interrupt-cells: + Usage: required + Value type: + Definition: Specifies the number of cells needed to encode an interrupt + source. + Must be 2. + The first element of the tuple is the PDC pin for the + interrupt. + The second element is the trigger type. + +- interrupt-parent: + Usage: required + Value type: + Definition: Specifies the interrupt parent necessary for hierarchical + domain to operate. + +- interrupt-controller: + Usage: required + Value type: + Definition: Identifies the node as an interrupt controller. + +- qcom,pdc-ranges: + Usage: required + Value type: + Definition: Specifies the PDC pin offset and the number of PDC ports. + The tuples indicates the valid mapping of valid PDC ports + and their hwirq mapping. + The first element of the tuple is the starting PDC port. + The second element is the GIC hwirq number for the PDC port. + The third element is the number of interrupts in sequence. + +Example: + + pdc: interrupt-controller@b220000 { + compatible = "qcom,sdm845-pdc"; + reg = <0xb220000 0x30000>; + qcom,pdc-ranges = <0 512 94>, <94 641 15>, <115 662 7>; + #interrupt-cells = <2>; + interrupt-parent = <&intc>; + interrupt-controller; + }; + +DT binding of a device that wants to use the GIC SPI 514 as a wakeup +interrupt, must do - + + wake-device { + interrupts-extended = <&pdc 2 IRQ_TYPE_LEVEL_HIGH>; + }; + +In this case interrupt 514 would be mapped to port 2 on the PDC as defined by +the qcom,pdc-ranges property. -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project