Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp1068118imm; Fri, 12 Oct 2018 11:10:39 -0700 (PDT) X-Google-Smtp-Source: ACcGV62KKtfrHPEmlnkaBjdQn1G84K850ppsXcIaPgdZ2fq7A/+Tv8AnKzppvFZ7BnTl62R3t/an X-Received: by 2002:a63:a80c:: with SMTP id o12-v6mr6528194pgf.271.1539367839612; Fri, 12 Oct 2018 11:10:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539367839; cv=none; d=google.com; s=arc-20160816; b=cVIp9FPUz9AfeK7eRvOzkuvSZXL0rItUJLrQ4k44T2ekbgAwcTOaxB55G15NmwOutY zurUhPUeSJd6Wf8rxgDfj35Uh0+Tp7R5Zmc8XeQk+OLPh29xgfcMLG5MENWM5cWKE9PX K3DB/0px7H70baghSK7Xl2KUXHnHdBftyvUkuYIGhwyx1EhAYGqCOwB5eUMianl6Frgh rTqE1Fqihc6vvxuah8F+ZqKWL5PNE3RI8O78RpE4h3fkTkOnhrvJsMHOOPrVFsleSBVS Ib6uf5KNYoXSTT7GiEcFYScsuQOHM/87/Pyr1YyQod7t/f3k30eoH6PfvSAYKYvM5wOg pr/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dmarc-filter :dkim-signature:dkim-signature; bh=dTh55tyefDzZqbMhMzi0i8AhMJY1JaZpPiDN2qTIzCA=; b=lglLa1kaDOpqd7xgYGgyMV8pRQ6cd0ivz04p43YoxwJ3m3KCQBG7pHmTibQMjqOdTN azNlgSS/72JUhYB0yOXxgf/GywN+HWnxKBmKkIgwF+Vti02ZZ++nXY8nzTtjFpbAgU62 7IXoU1czDhfmi5kW5XDGPOr8hZ9Oh8CpYPeeSI7OW35YLxXSVinbbDCf9OLkTU+uymPG 6cTKWm+kROaq6VRny2ZPz43c6QeFl3W+rttHvzXdnKNa2w+fvxk8Z8jdxAStKtXi+y9F hJxQEv8LKzW6ZNUGIeoFvi5Y4k2TRpByqDKgqNJZlN6a73JxD+BPXCrVmfhNQePPsSTu qIjg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=JKfM5iF+; dkim=pass header.i=@codeaurora.org header.s=default header.b=LKsAwFSU; 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 v126-v6si1886239pgv.10.2018.10.12.11.10.24; Fri, 12 Oct 2018 11:10:39 -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=JKfM5iF+; dkim=pass header.i=@codeaurora.org header.s=default header.b=LKsAwFSU; 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 S1726979AbeJMBmM (ORCPT + 99 others); Fri, 12 Oct 2018 21:42:12 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:38906 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726530AbeJMBmM (ORCPT ); Fri, 12 Oct 2018 21:42:12 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 873B760BFE; Fri, 12 Oct 2018 18:08:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1539367708; bh=HPaRH2SCTiuRQ6MypohP49lkHMdsk9FCdVfJ1WNK8FE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=JKfM5iF+9iFGSkiQfGDR+gow3yM+09+6HLhFJyv4232y1ZiDLBHt6ACdnSbdyRPNf +nItG7N3lcXzSM7WT6HCDHGAgDSrPFHjIZ6p27GqftIroa1vrw2VndlFv4g95BZT3o w0h8b8MlrG5cg0KR7k68r81mZaSD6bZijS+Qf/p4= 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.2 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_INVALID,DKIM_SIGNED,FROM_LOCAL_NOVOWEL autolearn=no autolearn_force=no version=3.4.0 Received: from [192.168.1.3] (unknown [183.83.77.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: rplsssn@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 7229A6060A; Fri, 12 Oct 2018 18:08:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1539367707; bh=HPaRH2SCTiuRQ6MypohP49lkHMdsk9FCdVfJ1WNK8FE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=LKsAwFSUd6oIqBrI7U/q8RGGSZBq/sYZzpTMOj2xh/5LgF8mv1MrLlFcBKDAfwvSt HBbsySTfNQAeP9M5I68EmOd5xKRFT1dN+EmZICswxFFsw/gv+fT3FCRziGSd/f3UKt PmlRvCsW1imsyfU6V9srLWelw/avV79eql70gp6E= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 7229A6060A 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=rplsssn@codeaurora.org Subject: Re: [PATCH RFC v1 5/8] dt-bindings: introduce cpu power domain bindings for Qualcomm SoCs To: Sudeep Holla Cc: andy.gross@linaro.org, david.brown@linaro.org, rjw@rjwysocki.net, ulf.hansson@linaro.org, khilman@kernel.org, linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, rnayak@codeaurora.org, bjorn.andersson@linaro.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, devicetree@vger.kernel.org, sboyd@kernel.org, evgreen@chromium.org, dianders@chromium.org, mka@chromium.org, ilina@codeaurora.org, Lorenzo Pieralisi References: <1539206455-29342-1-git-send-email-rplsssn@codeaurora.org> <1539206455-29342-6-git-send-email-rplsssn@codeaurora.org> <20181011110849.GA32752@e107155-lin> From: Raju P L S S S N Message-ID: Date: Fri, 12 Oct 2018 23:38:11 +0530 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20181011110849.GA32752@e107155-lin> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/11/2018 4:38 PM, Sudeep Holla wrote: > On Thu, Oct 11, 2018 at 02:50:52AM +0530, Raju P.L.S.S.S.N wrote: >> Add device binding documentation for Qualcomm Technology Inc's cpu >> domain driver. The driver is used for managing system sleep activities >> that are required when application processor is going to deepest low >> power mode. >> > > So either we are not using PSCI or the binding is not so clear on > how this co-exist with PSCI power domains. Could you provide details ? > >> Cc: devicetree@vger.kernel.org >> Signed-off-by: Raju P.L.S.S.S.N >> --- >> .../bindings/soc/qcom/cpu_power_domain.txt | 39 ++++++++++++++++++++++ >> 1 file changed, 39 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/soc/qcom/cpu_power_domain.txt >> >> diff --git a/Documentation/devicetree/bindings/soc/qcom/cpu_power_domain.txt b/Documentation/devicetree/bindings/soc/qcom/cpu_power_domain.txt >> new file mode 100644 >> index 0000000..1c8fe69 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/soc/qcom/cpu_power_domain.txt >> @@ -0,0 +1,39 @@ >> +Qualcomm Technologies cpu power domain >> +----------------------------------------- >> + >> +CPU power domain handles the tasks that need to be performed during >> +application processor deeper low power mode entry for QCOM SoCs which >> +have hardened IP blocks combinedly called as RPMH (Resource Power Manager >> +Hardened) for shared resource management. Flushing the buffered requests >> +to TCS (Triggered Command Set) in RSC (Resource State Coordinator) and >> +programming the wakeup timer in PDC (Power Domain Controller) for timer >> +based wakeup are handled as part of domain power down. >> + > > And which is this not hidden as part of PSCI CPU_SUSPEND ? > >> +The bindings for cpu power domain is specified in the RSC section in >> +devicetree. >> + >> +Properties: >> +- compatible: >> + Usage: required >> + Value type: >> + Definition: must be "qcom,cpu-pm-domain". >> + > > NACK until details on how this can co-exist with PSCI is provided. Platform coordinated mode is used on this SoC. So they both can co-exist. I hope with the discussion on other thread, the details are clear. > > -- > Regards, > Sudeep >