Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp1206875ybg; Fri, 18 Oct 2019 13:48:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqxjkJEanxuxvyYT2AKuobzD6NyjiwXh73HVJzHm6+WgfzPRPJs/XGOvIjbFYLTHh5J1aJ+N X-Received: by 2002:a17:906:7e17:: with SMTP id e23mr10914240ejr.205.1571431716224; Fri, 18 Oct 2019 13:48:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571431716; cv=none; d=google.com; s=arc-20160816; b=dOkBWfigbuCsLEVrn0PeU2FaQyTtjXUyENgcuYQ9ozTiBcul6iQDMLiH4iPlxVtHWf +GqXd4mM0rJ7Vf9S2MDRyWnbsNuQWIv1LZLtHJEDzL7Hir6uO7h/TbG/wHYHNAnu4hN6 f5wnNTAe8a7M9BIZASYa6FohDE96YRc0Uf8515zhGOF9GJ7uGiva6lGUL+vcEfIBK4mL ZDzUZXKjHVgZqlyHvaa9ssbEKdzCONOlQWVebRtHcoFIdjfLf7TFAEA/H6xtT4l0bfun ChH7vRQgQ6FMI6gFqd3vzQnz6Z/HAS6zf4K1vmXbl25PimiD5EPqKfqre+BWnge7+tZb KsiQ== 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:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject:dkim-signature; bh=Ny/2VRd+nYPZUv6lS3IfSjlpgoq8xpi9csSapod3I6s=; b=Vg9EvBl4PerCXLc1XS1gpNql8QSduM2POtGGAv6CTRHwm2XnSEG3O+Ntdg+HNN8qLC GV4cZxC9CO3++OiAMsLoAkTp2gIA+Jv9DdjHUSDYi22SBLoBvrQyUujFnhCrOIlfFpUD gPoHO98hO4Q4Rau9Ue/G0Jyz9AF2X9PmTNj4ahXZdps6P9/Qxd25PHTM8btQ+qMJypqf UAPWUi5fk0Qm5/Gave4oZESNO1SG02Pf1sEkfxZanB/FlSViRtXrhm0jGWSkyPuLJX5B kqOolOxYA90NTPDz+p+kHvS7cy4TV+4bXCBCz8+J8cj8K59xl8pF/zhgGZWUwIsBzkpv 9adw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=l6pUbq9Z; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b14si4097115eju.187.2019.10.18.13.48.13; Fri, 18 Oct 2019 13:48:36 -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=@linaro.org header.s=google header.b=l6pUbq9Z; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2440398AbfJQQKU (ORCPT + 99 others); Thu, 17 Oct 2019 12:10:20 -0400 Received: from mail-qt1-f196.google.com ([209.85.160.196]:40732 "EHLO mail-qt1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2440007AbfJQQKU (ORCPT ); Thu, 17 Oct 2019 12:10:20 -0400 Received: by mail-qt1-f196.google.com with SMTP id m61so4361276qte.7 for ; Thu, 17 Oct 2019 09:10:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Ny/2VRd+nYPZUv6lS3IfSjlpgoq8xpi9csSapod3I6s=; b=l6pUbq9ZGqeQIvaa+cnqcCYOZi3/jNJwbPMtbnUlqNj5QrnM7UA5gdH8mg31AIVZw7 xbDPlG5/P/SVpJ9MZJuRe5wCTxjXPIoTALKfEwdgVOUU2bOqWVeNWrb4KMd+gwGckI0w wsFgaQ19vhES8njgHStqgeVRteJmqB8m7rfbo9PPz3Ntl/JoqGDsLYq31epfCFEonk/4 bU0kmkmCDnUxhGPOcmSg4klgOzFoTMIWpdzpvFEzAU+h0INKwg9Gz8Gj5GpjqKVf66VF 5j+Su/AzFBvV1tpBywTqzx7NbzMKjLHaKwZuDVUyNBAPtDB8/d2ze4SAhyy+Zr4/57kn mtJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Ny/2VRd+nYPZUv6lS3IfSjlpgoq8xpi9csSapod3I6s=; b=XKNwAzrxWLjFnxshmbQkjErXs5KPXzDveENCqx63PzQp/zV0W7r4qJ+S/yOUHUNPRA FjvjxWRsZGQ5cKLIj4CrGA+AYSXMSx1H9Ajy5VKpCB0XE0qk/kZJYfpvBKRz++KfGQy4 HbPJsJBF1NclbxCYxlOf00P8SybjnYHOoVr5uuap/0Ak1TaEqkfjmoVOuJuXUhihqk+X 3rAmW55BlOrUEMJG6gLmW5iijozvuNNlcG4K1ciGi0zJt/Npk+li1NksnvIkcdDwsU0u CWa+oR0NtEbH+qSI/j9zAKT0d8QQFv06Ap9xC+biG7zI7sNnyozm6OKsquUQlKlBS8nr S4pw== X-Gm-Message-State: APjAAAVyVPeN9aEVYQtIke2J4YtsoW176FzH2G0oIFiV04kA7OuhrgJA 4Lvoe7161iBL3I01pcbrhjoxt/zuKCoh2A== X-Received: by 2002:ac8:3ac6:: with SMTP id x64mr4619046qte.51.1571328618066; Thu, 17 Oct 2019 09:10:18 -0700 (PDT) Received: from [192.168.1.169] (pool-71-255-246-27.washdc.fios.verizon.net. [71.255.246.27]) by smtp.gmail.com with ESMTPSA id m15sm984714qka.104.2019.10.17.09.10.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Oct 2019 09:10:16 -0700 (PDT) Subject: Re: [PATCH v3 6/7] dt-bindings: soc: qcom: Extend RPMh power controller binding to describe thermal warming device To: Ulf Hansson References: <1571254641-13626-1-git-send-email-thara.gopinath@linaro.org> <1571254641-13626-7-git-send-email-thara.gopinath@linaro.org> <5DA88892.5000408@linaro.org> Cc: Eduardo Valentin , Zhang Rui , Daniel Lezcano , Bjorn Andersson , Andy Gross , amit.kucheria@verdurent.com, Mark Rutland , "Rafael J. Wysocki" , Linux PM , DTML , linux-arm-msm , Linux Kernel Mailing List From: Thara Gopinath Message-ID: <5DA89267.30806@linaro.org> Date: Thu, 17 Oct 2019 12:10:15 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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/17/2019 11:43 AM, Ulf Hansson wrote: > On Thu, 17 Oct 2019 at 17:28, Thara Gopinath wrote: >> >> Hello Ulf, >> Thanks for the review! >> >> On 10/17/2019 05:04 AM, Ulf Hansson wrote: >>> On Wed, 16 Oct 2019 at 21:37, Thara Gopinath wrote: >>>> >>>> RPMh power controller hosts mx domain that can be used as thermal >>>> warming device. Add a sub-node to specify this. >>>> >>>> Signed-off-by: Thara Gopinath >>>> --- >>>> Documentation/devicetree/bindings/power/qcom,rpmpd.txt | 10 ++++++++++ >>>> 1 file changed, 10 insertions(+) >>>> >>>> diff --git a/Documentation/devicetree/bindings/power/qcom,rpmpd.txt b/Documentation/devicetree/bindings/power/qcom,rpmpd.txt >>>> index eb35b22..fff695d 100644 >>>> --- a/Documentation/devicetree/bindings/power/qcom,rpmpd.txt >>>> +++ b/Documentation/devicetree/bindings/power/qcom,rpmpd.txt >>>> @@ -18,6 +18,16 @@ Required Properties: >>>> Refer to for the level values for >>>> various OPPs for different platforms as well as Power domain indexes >>>> >>>> += SUBNODES >>>> +RPMh alsp hosts power domains that can behave as thermal warming device. >>>> +These are expressed as subnodes of the RPMh. The name of the node is used >>>> +to identify the power domain and must therefor be "mx". >>>> + >>>> +- #cooling-cells: >>>> + Usage: optional >>>> + Value type: >>>> + Definition: must be 2 >>>> + >>> >>> Just wanted to express a minor thought about this. In general we use >>> subnodes of PM domain providers to represent the topology of PM >>> domains (subdomains), this is something different, which I guess is >>> fine. >>> >>> I assume the #cooling-cells is here tells us this is not a PM domain >>> provider, but a "cooling device provider"? >> Yep. >>> >>> Also, I wonder if it would be fine to specify "power-domains" here, >>> rather than using "name" as I think that is kind of awkward!? >> Do you mean "power-domain-names" ? I am using this to match against the >> genpd names defined in the provider driver. > > No. If you are using "power-domains" it means that you allow to > describe the specifier for the provider. Yep. But won't this look funny in DT ? The provider node will have a sub node with a power domain referencing to itself Like below: Is this ok ? rpmhpd: power-controller { compatible = "qcom,sdm845-rpmhpd"; #power-domain-cells = <1>; ... ... mx_cdev: mx { #cooling-cells = <2>; power-domains = <&rpmhpd SDM845_MX>; }; > > From Linux point of view, it means you can use dev_pm_domain_attach() > to hook up the corresponding device with the PM domain. Yes. Only the thermal framework does not populate cdev->dev->of_node. But it should be a trivial thing to fix it. Also if I end up creating a separate device, it should not matter. > > Using "power-domain-names" is just to allow to specify a name rather > than an index, which makes sense if there is more than one index. > Perhaps you can state that the "power-domain-names" should be there > anyway, to be a little bit future proof if ever multiple index > (multiple PM domains). > > Kind regards > Uffe > -- Warm Regards Thara