Received: by 10.223.176.5 with SMTP id f5csp12793wra; Tue, 30 Jan 2018 07:21:38 -0800 (PST) X-Google-Smtp-Source: AH8x227NS3E3N8m85mSvLZXzlXW+Ez7c9AwQiWs1VhyO6IqFup2g2FZwxDBLUkNvS4K7nZi+dGqm X-Received: by 10.98.108.130 with SMTP id h124mr30665784pfc.33.1517325698642; Tue, 30 Jan 2018 07:21:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517325698; cv=none; d=google.com; s=arc-20160816; b=JVDamCZMfAD/S1OZUV8pgPdqcxOVCoexkBiMds/fE1jL2t3QyavfdBhWddxalG03as 6F3AA0oExwSI6+rWnzSh0wkzYKzmicNJT0GtLlOri4N426nID+miAaUebywpsc5/D73g /aPj3k/+xWIFb6p+hjqgO2925F+HD55GS0g1UxbJFQfKgANmk0aMeXKk3GeAODdigR3D snqC5rchgE4W8NO3HyDEYPEiXv50+BqYCYeulCIci1ufhV+aKZlhXyFaqC9Uyg0oTQx0 /yTC1aCjt6lCe2eok06tC6HDf+0bMdsp3F9eq+k0iMjU8PesNkGSj0jvCbxum7SDBQVL Rl7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=iR0L8rDUNJBmew78jbBUK1qsv83W+Uz891geR8M6UPU=; b=AGBsZdQ530dm5DmkpnThsdWUhffbO+aCE3f8qDteL891gOXQNmAaWBFso/7fWjUx0c iExSJqbsYgxIJi38znQhlYI9jl/SXGEhZ1G+zjF0JGFGGXYwW9XU8JNL9LV12c7iU75A cERub//vYQIW+oaw9CZxrhneyGu7NlbfTQ9DQmB6hYNiTPCXlva+TYME4nWGZX4Cbx9g zhI0Z8/X0lLgMDyTQXA/Lzs2rvJ7cHuzZF36GigRu8NhX3rmrBRMDtfbyuohdYNwC1Ps 8019qNl9Bwg1H/dDObyWXnbnTW5chiikb9Q0q8H5FC1YHFfmBLY5KycTzUnev3+GQHMV qpnA== 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 b17si1708220pfl.222.2018.01.30.07.21.23; Tue, 30 Jan 2018 07:21:38 -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; 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 S1753035AbeA3PUQ (ORCPT + 99 others); Tue, 30 Jan 2018 10:20:16 -0500 Received: from mail-oi0-f66.google.com ([209.85.218.66]:41403 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751531AbeA3PUN (ORCPT ); Tue, 30 Jan 2018 10:20:13 -0500 Received: by mail-oi0-f66.google.com with SMTP id m83so8048716oik.8; Tue, 30 Jan 2018 07:20:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=iR0L8rDUNJBmew78jbBUK1qsv83W+Uz891geR8M6UPU=; b=oDSU38+csPf3oYy6tVhVixWbN3DHHS/ZyUCQSuy9yYa62RYxgqpnE9n71V7KouVr6g GglsoeGvuSx8SGiXCNbEqpukSsusOuHYb8s3EQUt5hk1xL8/Y7Xr1KhMl4I9uyf44rrF l0IQpOxCbwObKXMPhZf2Facvv0uEt5eBKK2G3EX5BGR6TBWtuPoxy3Ajk9dAJMh/thNm JUmPnrMeuNeFFBjriJlkeTmTX2BxuqJLfebKRE6sgNaYwkW713J08jSVHLuXhRhkaOc0 TnVjsSo/3zuG0hcpjOg6y632rvYVLe9V+UJHtevnU/KVHZ24hv8Be5mobbPY4bFw0w4o RH6A== X-Gm-Message-State: AKwxytdAPk20W7dqV7BbBYsYPFCHNj8xdbIbGOaveGtBWGwZBdIT4tWv POHzRNwLjxuqorKDicoSnA== X-Received: by 10.84.68.10 with SMTP id k10mr9195208oiw.266.1517325613102; Tue, 30 Jan 2018 07:20:13 -0800 (PST) Received: from localhost (216-188-254-6.dyn.grandenetworks.net. [216.188.254.6]) by smtp.gmail.com with ESMTPSA id e20sm2477359otc.40.2018.01.30.07.20.12 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 30 Jan 2018 07:20:12 -0800 (PST) Date: Tue, 30 Jan 2018 09:20:12 -0600 From: Rob Herring To: Lina Iyer Cc: tglx@linutronix.de, jason@lakedaemon.net, marc.zyngier@arm.com, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, sboyd@codeaurora.org, rnayak@codeaurora.org, asathyak@codeaurora.org, devicetree@vger.kernel.org Subject: Re: [PATCH RFC 2/4] dt-bindings/interrupt-controller: pdc: descibe PDC device binding Message-ID: <20180130152012.ucjmaw3nlim4d4fr@rob-hp-laptop> References: <20180123175656.11942-1-ilina@codeaurora.org> <20180123175656.11942-3-ilina@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180123175656.11942-3-ilina@codeaurora.org> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 23, 2018 at 10:56:54AM -0700, Lina Iyer wrote: > 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 | 55 ++++++++++++++++++++++ > 1 file changed, 55 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..c4592bbf678d > --- /dev/null > +++ b/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.txt > @@ -0,0 +1,55 @@ > +PDC interrupt controller > + > +Qualcomm Technologies Inc. SoCs based on the RPM Hardened archicture 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. This driver only > +configures the interrupts, does not handle them. > + > +Properties: > + > +- compatible: > + Usage: required > + Value type: > + Definition: Should contain "qcom,pdc" and "qcom,pdc-" > + - "qcom,pdc-sdm845": For sdm845 pin data pin data? Convention is - Need to make the order of compatibles clear. Generally that is done with 'followed by "qcom,pdc"' after the list of compatibles. But then, do you really need a fallback. This seems like a block that would change frequently. If there's not more than 2 or 3 chips with the same block, don't do a fallback. > + > +- 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. > + Value must be 3. > + The encoding of these cells are same as described in [1]. > + > +- 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. > + > +Example: > + > + pdc: interrupt-controller@b220000 { > + compatible = "qcom,pdc", "qcom,pdc-sdm845"; This is backwards. > + reg = <0xb220000 0x30000>; > + #interrupt-cells = <3>; > + interrupt-parent = <&intc>; > + interrupt-controller; > + }; > + > +[1]. Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt > -- > The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, > a Linux Foundation Collaborative Project > > -- > To unsubscribe from this list: send the line "unsubscribe devicetree" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html