From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 891EAFC6197 for ; Fri, 8 Nov 2019 21:29:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5FDBB218AE for ; Fri, 8 Nov 2019 21:29:36 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="nKl15u10" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731657AbfKHV3d (ORCPT ); Fri, 8 Nov 2019 16:29:33 -0500 Received: from mail-il1-f194.google.com ([209.85.166.194]:42958 "EHLO mail-il1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731335AbfKHV3d (ORCPT ); Fri, 8 Nov 2019 16:29:33 -0500 Received: by mail-il1-f194.google.com with SMTP id n18so6380957ilt.9 for ; Fri, 08 Nov 2019 13:29:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mRmwhSGnJWcbro1I2NsU98mvkk0pcwQPiXBcJRg/O6I=; b=nKl15u10ItYfNUfRdfrOlRLJn71C4ibsqBZ/3P+B+74i1afpRcQqn+q6zc8jpdWfF/ 4TlxJXWMVA2CzKaTu4/TkkDz/vWRfcJCJh6ToAyHjyRSfJH2cy+7BAFBE4bUdTXhkVpa +vhUPS0fXQBcgMO/mJWo4oLl/GXv8laDO3g2E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mRmwhSGnJWcbro1I2NsU98mvkk0pcwQPiXBcJRg/O6I=; b=qsaBSLszEtuD0ySkcAJB+x4CyNqNnN6NXOWGk5XGyaaWP4VVVYtf5vXX05RJjHmuk+ Rd3Jv37C4Kc1HDYmmok/xyhUbMy+lLuCu/Oq0rh8WagJy1DBdcyLgRw6B0UobPzTg1Kd noq1JAaAqW8KF6tMjZT+uPbJgEK1GQ6WsiHODPNQtSboHmSGKn/og2xstXXNjuK3Mycy OS7NUDeAcHmr67LFB7za7L3NU6Npq/4u0q8zZ1ezlUntv/US2guGW2bNdJy1veZqkpqI 4BwUjSpAwu1N4AzMG0urFkKGlD750QMgoIXRt4P+gp5zKVmuQKIT5LzA8vGlf0oPcY7Q 94AA== X-Gm-Message-State: APjAAAXgvAyAh0bH4RkJZ6UjFOOs9nUHaG506YgUV2jBZmDU5NLWefQO Nnt6pbmaGX27N3xkmkt31/YyG7h2ps0= X-Google-Smtp-Source: APXvYqz0ikp3c2RBkm8rybmn7xCZ67PQbe//2+kDb3aIquHSpTLqt65YodnB5JO/uUodo0aHxRJHow== X-Received: by 2002:a92:6912:: with SMTP id e18mr13989253ilc.134.1573248571089; Fri, 08 Nov 2019 13:29:31 -0800 (PST) Received: from mail-io1-f49.google.com (mail-io1-f49.google.com. [209.85.166.49]) by smtp.gmail.com with ESMTPSA id h14sm926086ilc.87.2019.11.08.13.29.30 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 08 Nov 2019 13:29:30 -0800 (PST) Received: by mail-io1-f49.google.com with SMTP id j20so7635606ioo.11 for ; Fri, 08 Nov 2019 13:29:30 -0800 (PST) X-Received: by 2002:a5e:c642:: with SMTP id s2mr914619ioo.218.1573248569668; Fri, 08 Nov 2019 13:29:29 -0800 (PST) MIME-Version: 1.0 References: <1568411962-1022-1-git-send-email-ilina@codeaurora.org> <1568411962-1022-6-git-send-email-ilina@codeaurora.org> In-Reply-To: <1568411962-1022-6-git-send-email-ilina@codeaurora.org> From: Doug Anderson Date: Fri, 8 Nov 2019 13:29:17 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH RFC v2 05/14] of: irq: document properties for wakeup interrupt parent To: Lina Iyer Cc: Stephen Boyd , Evan Green , maz@kernel.org, LinusW , LKML , linux-arm-msm , Bjorn Andersson , mkshah@codeaurora.org, "open list:GPIO SUBSYSTEM" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" Content-Type: text/plain; charset="UTF-8" Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org Hi, On Fri, Sep 13, 2019 at 3:00 PM Lina Iyer wrote: > > 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>; > + nit: git flags the above line as whitespace damage. Please remove if/when you spin. Thanks! -Doug