Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1340838ybe; Fri, 13 Sep 2019 15:06:11 -0700 (PDT) X-Google-Smtp-Source: APXvYqxj/Mn5satJoj8XJdCHYvw5xTcIJcJH4+9j6SqvXTH2OeOCTGzB0yZJ45MSFnChC6RY7h+4 X-Received: by 2002:a17:906:31c3:: with SMTP id f3mr42089805ejf.296.1568412371721; Fri, 13 Sep 2019 15:06:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568412371; cv=none; d=google.com; s=arc-20160816; b=oohcT7mFbbK0sjWeKP39F1wV+74TMM7e+5WLHVS2viuC8mW4/yeFfr0JaGDoZSSw/J mqQhOr79qMXSLhdXSzhJOD+UiPTVEZDbalmQdbRN/ya+uw5vfC7QbZ8n1uZ1HRAg7i/M MpEj6ttjbtwyU75sTiVJlVu87HzjgOdeSpLbynY9gnpMaVf9vNgYjJlS6KE9zsoODZyY wFEiOYGcHswkffZwNHneJo40jSBD1UlWKPSrmP6rf4IeRdbqxT1qQz+6PcRW1eCArJC0 JbyAnqvnftoLFtRHkWL3UW6Sf2HB4MhDMZaxKabXWksNBOLZlnQBon4VqWbuHH/9jkxK PRZg== 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; bh=KQjX1nB+WbklxUbTPA0Nawty2zigiPPZ4XXD3JTVSnE=; b=mUkT59/svoyj3r7zdmYCCbNLgSGtFli+vW0d+IsNYWR4Pli3T4UbsqWiJmRwkls/AJ ROSfvZmMJW52SAWBJ/Yce98m0aqLpuBm7rf7vxIGE6PARVY2V6fMZvar2ETEaPnCggqF ynHjiXymIzopLNjtZjcyES2nu1DnoJDPjRB4fC0PXz0uW/krEFoMPqmdtJYubdLFB5Ol 2wxErEidpgQXoVLTMmg8lNT62WGjbvPckGM3YTf+6H8OHw/nb+L4OfXBZzUbvOuYSz6e uZlRKAbemutDl3AbJW4wkOpIuCU350cEykvJgOU1CR1xRr5Pvy93JRVOqM3aAoe8hL+G G7LQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=cxphENNd; dkim=pass header.i=@codeaurora.org header.s=default header.b=cxphENNd; 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 y27si17626552edd.249.2019.09.13.15.05.47; Fri, 13 Sep 2019 15:06:11 -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; dkim=pass header.i=@codeaurora.org header.s=default header.b=cxphENNd; dkim=pass header.i=@codeaurora.org header.s=default header.b=cxphENNd; 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 S2390376AbfIMV7s (ORCPT + 99 others); Fri, 13 Sep 2019 17:59:48 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:59698 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390268AbfIMV7r (ORCPT ); Fri, 13 Sep 2019 17:59:47 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id A686B60A60; Fri, 13 Sep 2019 21:59:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1568411986; bh=Nma9mWXyYVp2E0wi8Zqshh5FM0cWL4gvjEG+g+1UyeA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=cxphENNdwsUDWvQuIOiqIc4JWPFSWkaGsuRImOb9XIuVtKg/Fs7xzokdrGyS74xnV MXJr57gCG6whBnAjGq5pvgiVejWJXwqvT9iRk7hLQzPjML3JtneFCtSjeb1IWxQTob D3G/VePO0vz3G6VZi1BTrHhqn1wsNe3JdTORylxA= 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.7 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_INVALID,DKIM_SIGNED,SPF_NONE 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 6DF0560C72; Fri, 13 Sep 2019 21:59:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1568411986; bh=Nma9mWXyYVp2E0wi8Zqshh5FM0cWL4gvjEG+g+1UyeA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=cxphENNdwsUDWvQuIOiqIc4JWPFSWkaGsuRImOb9XIuVtKg/Fs7xzokdrGyS74xnV MXJr57gCG6whBnAjGq5pvgiVejWJXwqvT9iRk7hLQzPjML3JtneFCtSjeb1IWxQTob D3G/VePO0vz3G6VZi1BTrHhqn1wsNe3JdTORylxA= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 6DF0560C72 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: swboyd@chromium.org, evgreen@chromium.org, maz@kernel.org, linus.walleij@linaro.org Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, bjorn.andersson@linaro.org, mkshah@codeaurora.org, linux-gpio@vger.kernel.org, Lina Iyer , devicetree@vger.kernel.org Subject: [PATCH RFC v2 05/14] of: irq: document properties for wakeup interrupt parent Date: Fri, 13 Sep 2019 15:59:13 -0600 Message-Id: <1568411962-1022-6-git-send-email-ilina@codeaurora.org> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1568411962-1022-1-git-send-email-ilina@codeaurora.org> References: <1568411962-1022-1-git-send-email-ilina@codeaurora.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Some interrupt controllers in a SoC, are always powered on and have a select interrupts routed to them, so that they can wakeup the SoC from suspend. Add wakeup-parent DT property to refer to these interrupt controllers. Cc: devicetree@vger.kernel.org Signed-off-by: Lina Iyer Reviewed-by: Rob Herring --- .../devicetree/bindings/interrupt-controller/interrupts.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/Documentation/devicetree/bindings/interrupt-controller/interrupts.txt b/Documentation/devicetree/bindings/interrupt-controller/interrupts.txt index 8a3c408..c10e310 100644 --- a/Documentation/devicetree/bindings/interrupt-controller/interrupts.txt +++ b/Documentation/devicetree/bindings/interrupt-controller/interrupts.txt @@ -108,3 +108,16 @@ commonly used: sensitivity = <7>; }; }; + +3) Interrupt wakeup parent +-------------------------- + +Some interrupt controllers in a SoC, are always powered on and have a select +interrupts routed to them, so that they can wakeup the SoC from suspend. These +interrupt controllers do not fall into the category of a parent interrupt +controller and can be specified by the "wakeup-parent" property and contain a +single phandle referring to the wakeup capable interrupt controller. + + Example: + wakeup-parent = <&pdc_intc>; + -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project