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=-8.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 2CE36C3A5A3 for ; Tue, 27 Aug 2019 22:32:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F3AFF217F5 for ; Tue, 27 Aug 2019 22:32:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566945176; bh=BZBaTFGssajv3IlbgzTXiqQlRe3Vi4EfJMlUKefgSJI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=p2ZpQUqDcWGcsOAYLJtbL3urueSzSNAaNvRTzQimASd8OIdeSAJM1H683O568loip XhMNNlGoc5FUoMlicfwdkFiSZq79ErU4/EYYvjGzcPp2nelAlIJYrIRLboEd1hNo6x 1JAgug5IZ3xrOfiv6efgGMX8RHB/PlhvMC+nDakw= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726092AbfH0Wcz (ORCPT ); Tue, 27 Aug 2019 18:32:55 -0400 Received: from mail-ot1-f65.google.com ([209.85.210.65]:43238 "EHLO mail-ot1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726025AbfH0Wcz (ORCPT ); Tue, 27 Aug 2019 18:32:55 -0400 Received: by mail-ot1-f65.google.com with SMTP id e12so762450otp.10; Tue, 27 Aug 2019 15:32:54 -0700 (PDT) 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=bG9bAPsPgtk0aXT02g27VLf1Saty2/UhvB2P1PQFez4=; b=lFh0XojkxV22fnbW+8yeuTFoncb0V58PwmV6D1R0gHbEE8Fnl/sk3qJJbNsDFEem9S IJgRLxQQenYX8WZAaUxPsCZHrsog3v12vAM+W6kzbyYl7/SRL6K4byR2nc0wa4AeBQsa 3+4DI+hppspWCQljpfstzZROzPbfC45xcc06SdhrATNNYp7cY5h7lVpXPWltFmHVX/0x LCpyitPHpzTv1Zhk8bNEZINSOoNKRYT0FDW3A7a68cM+WSRFzCBRSbel8WrVkrXtejPj +ARLIqx4jVTYuTfKRaeo5uL6cpwyKsp3tr3thFyLP2hmyZkg9DpoWHtWZT5yaGQe2AiY Xzig== X-Gm-Message-State: APjAAAUHLRa46OaVpnGKiPC+BaXrntNieNfbix5rma9DDcQd4sfoUbRq oW+qTEbiMXpYqTz3eXxSZUgLgo+FRw== X-Google-Smtp-Source: APXvYqxrYCEbW6Lei7IWDJP4LIXpA5Q0iwBYIAzLRZXOMhYN8gHCCf8NUNNEpuif/S+KC2JZ8UZZfg== X-Received: by 2002:a9d:6e93:: with SMTP id a19mr819140otr.29.1566945174143; Tue, 27 Aug 2019 15:32:54 -0700 (PDT) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id e27sm186531oig.53.2019.08.27.15.32.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 27 Aug 2019 15:32:53 -0700 (PDT) Date: Tue, 27 Aug 2019 17:32:52 -0500 From: Rob Herring To: Maulik Shah Cc: swboyd@chromium.org, agross@kernel.org, david.brown@linaro.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, bjorn.andersson@linaro.org, evgreen@chromium.org, dianders@chromium.org, rnayak@codeaurora.org, ilina@codeaurora.org, lsrao@codeaurora.org, ulf.hansson@linaro.org, devicetree@vger.kernel.org Subject: Re: [PATCH v2 3/6] dt-bindings: soc: qcom: Add RSC power domain specifier Message-ID: <20190827223252.GA26039@bogus> References: <20190823081703.17325-1-mkshah@codeaurora.org> <20190823081703.17325-4-mkshah@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190823081703.17325-4-mkshah@codeaurora.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On Fri, Aug 23, 2019 at 01:47:00PM +0530, Maulik Shah wrote: > In addition to transmitting resource state requests to the remote > processor, the RSC is responsible for powering off/lowering the > requirements from CPUs subsystem for the associated hardware like > buses, clocks, and regulators when all CPUs and cluster is powered down. > > The power domain is configured to a low power state and when all the > CPUs are powered down, the RSC can lower resource state requirements > and power down the rails that power the CPUs. > > Add PM domain specifier property for RSC controller. > > Cc: devicetree@vger.kernel.org > Signed-off-by: Maulik Shah > Reviewed-by: Stephen Boyd > --- > Documentation/devicetree/bindings/soc/qcom/rpmh-rsc.txt | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/Documentation/devicetree/bindings/soc/qcom/rpmh-rsc.txt b/Documentation/devicetree/bindings/soc/qcom/rpmh-rsc.txt > index 9b86d1eff219..d0ab6e9b6745 100644 > --- a/Documentation/devicetree/bindings/soc/qcom/rpmh-rsc.txt > +++ b/Documentation/devicetree/bindings/soc/qcom/rpmh-rsc.txt > @@ -83,6 +83,13 @@ Properties: > Value type: > Definition: Name for the RSC. The name would be used in trace logs. > > +- #power-domain-cells: > + Usage: optional > + Value type: > + Definition: Number of cells in power domain specifier. Optional for > + controllers that may be in 'solver' state where they can > + be in autonomous mode executing low power modes. What's the value? It's always 0? > + > Drivers that want to use the RSC to communicate with RPMH must specify their > bindings as child nodes of the RSC controllers they wish to communicate with. > > @@ -112,6 +119,7 @@ TCS-OFFSET: 0xD00 > , > , > ; > + #power-domain-cells = <0>; > }; > > Example 2: > -- > QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation. >