Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp551662ybm; Mon, 20 May 2019 22:40:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqxUo8M+uu7l+MEQWi203wFuAcP3LV7zJPdYWyYX6Jy1nbp9ErQlWx+QOznknZUi0qeuoJpQ X-Received: by 2002:a17:902:b58f:: with SMTP id a15mr36735986pls.201.1558417240671; Mon, 20 May 2019 22:40:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558417240; cv=none; d=google.com; s=arc-20160816; b=Clkomtt5kl39nu0ml8d4jrEkWrRhQXRVMAnwCEcs+Q6JHirPpI/vb7qH5cbRDE4BGn fIOjyRiXQMXcjsKKELkRR3XFXQnmd4z7V0vvRPKmW6bUMAg3ojqWdOQ9IrSqijRJrYrD wo+x3cJKyX/fudyp7NgOCwN9EqHAxgxxcT5EplKJY83jxA+j4vRvleJHbkVUUQAUE+Ha m5BXdqAsQcpha/aYr5mp8JWLIZEfrFVuFTB2qxe2a0EqRxLowmvUDYyBtviEZVRlNjIY r8p40dCRCbe/Fz9QNUK2u/IcCtgyYq1CsvbBZL1XFHTYOfrWmjFqxDpao1apn8Md4OK4 vHZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=ylhlFxOQtj3eEV5EznbPBmp2z9RTytA2Ra4QbX683aw=; b=tWQrE5L+0EKmz768esPKoEs0Q2/oO7l8/fFwwg2VOgXp951YW8NvDmDu9kN8FPaDhq uVdN/FGa9i+sSDnjbkWdXB2HZ/GZZpkoGJvwfchAuoQXIy5uf6Wp4phYith+sTFmusdz TVnjW4AW/wQig0n36Q5XX/teN+g/y7fcT+FiVMdty2seMFCrMBofyGcsE1+VyBdglotc uOnbnJFaROc70+DJ4rZYwHu0Mc+wEWOUMYmiWZIiA+EdiqRRitC216vWWMZGLpUevZ9P pjqDJuWx5EZmfSgb22ImFoICWzUNYQU3i/FxUEpYkgM1eju5GQHXR5UZA99g68lTDZa8 4mZA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=pACzS81C; 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 d4si12042685plr.297.2019.05.20.22.40.25; Mon, 20 May 2019 22:40:40 -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=pACzS81C; 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 S1727841AbfEUFiW (ORCPT + 99 others); Tue, 21 May 2019 01:38:22 -0400 Received: from mail-qk1-f193.google.com ([209.85.222.193]:33246 "EHLO mail-qk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726495AbfEUFiW (ORCPT ); Tue, 21 May 2019 01:38:22 -0400 Received: by mail-qk1-f193.google.com with SMTP id p18so9755731qkk.0 for ; Mon, 20 May 2019 22:38:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ylhlFxOQtj3eEV5EznbPBmp2z9RTytA2Ra4QbX683aw=; b=pACzS81CvGQTJCH9GhT/KUwRkEs1crnUg5F/m5oHZdu+OBy/9veH3hy2qondpMgaRM A8OAdTYheYg9WhJJwfvIruNfnheKSd+itzj3fHkh6/7roccoq6+C25TAmXwuAWL8eAl0 ZGp9vk0FTqJT/JJbUG41jOtCBveAN9j0KNZZwiCgKiBlc2gRXKz/ZY0sPe88TC8yZt+v FWyzjDJuh6ulHzXzoWW3B1POzRB6emNPfMhy9BMveRQppKHPxluyIq84k/lCdLmyRggm RCkJNg3KtMX3weSI+tMNEDxiv+w3gK2nxSMlT03vGtNJX3sQMHPcika4qR4BHQ1n44Cu Fk1A== 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=ylhlFxOQtj3eEV5EznbPBmp2z9RTytA2Ra4QbX683aw=; b=uEWOrzm/F5oszaqOqQb52w+X5IwpDN6aZqpo/pGE4kBrHfrxO6PFUHO1Y84ZDcMcz/ aGEiBU8dMgweKv90/ypEQ2cdrIMtHgnOF2iOl3ihqzvI2G5W1mMowSL2Fo/QqkZGq7st uYYKJDYLQYo7XQQc1gPKqEa/OtMtPmzWZUE/lRG1ybIhRII/j3bXVe8XLPDu1dA2LkAd 5qj1MAPomn/7TABpu45fCNtEVD9ypfpfI8jI1gEKV/aF9DSoXKYeroHOwSHvcXVDxv6u UF6SUaZJtE2oZxVSQZ+EFT1coWAQm0LXEVfOTQ0syvE6k8eODLdn1Aad1wC74ymnMyoZ yrSg== X-Gm-Message-State: APjAAAXeYU6o2yoY2RjrzzcbaM3p3ianl5/BtfYOmh1dSV/M6L639VwE yATy54ycG7zw0efYxouVOWZavDnFBIx7dZZ2DpTaXwG5nw8= X-Received: by 2002:a37:8703:: with SMTP id j3mr2373239qkd.188.1558417100902; Mon, 20 May 2019 22:38:20 -0700 (PDT) MIME-Version: 1.0 References: <2a0626da4d8d5a1018c351b24b63e5e0d7a45a10.1557486950.git.amit.kucheria@linaro.org> <20190514161220.GC1824@centauri.ideon.se> <20190515130256.GA27174@centauri> In-Reply-To: <20190515130256.GA27174@centauri> From: Amit Kucheria Date: Tue, 21 May 2019 11:08:09 +0530 Message-ID: Subject: Re: [PATCHv1 4/8] arm64: dts: qcom: msm8916: Use more generic idle state names To: Niklas Cassel Cc: Linux Kernel Mailing List , linux-arm-msm , Bjorn Andersson , Andy Gross , David Brown , Li Yang , Shawn Guo , DTML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 15, 2019 at 6:33 PM Niklas Cassel wrote: > > On Wed, May 15, 2019 at 03:43:19PM +0530, Amit Kucheria wrote: > > On Tue, May 14, 2019 at 9:42 PM Niklas Cassel wrote: > > > > > > On Fri, May 10, 2019 at 04:59:42PM +0530, Amit Kucheria wrote: > > > > Instead of using Qualcomm-specific terminology, use generic node names > > > > for the idle states that are easier to understand. Move the description > > > > into the "idle-state-name" property. > > > > > > > > Signed-off-by: Amit Kucheria > > > > --- > > > > arch/arm64/boot/dts/qcom/msm8916.dtsi | 11 ++++++----- > > > > 1 file changed, 6 insertions(+), 5 deletions(-) > > > > > > > > diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi b/arch/arm64/boot/dts/qcom/msm8916.dtsi > > > > index ded1052e5693..400b609bb3fd 100644 > > > > --- a/arch/arm64/boot/dts/qcom/msm8916.dtsi > > > > +++ b/arch/arm64/boot/dts/qcom/msm8916.dtsi > > > > @@ -110,7 +110,7 @@ > > > > reg = <0x0>; > > > > next-level-cache = <&L2_0>; > > > > enable-method = "psci"; > > > > - cpu-idle-states = <&CPU_SPC>; > > > > + cpu-idle-states = <&CPU_SLEEP_0>; > > > > clocks = <&apcs>; > > > > operating-points-v2 = <&cpu_opp_table>; > > > > #cooling-cells = <2>; > > > > @@ -122,7 +122,7 @@ > > > > reg = <0x1>; > > > > next-level-cache = <&L2_0>; > > > > enable-method = "psci"; > > > > - cpu-idle-states = <&CPU_SPC>; > > > > + cpu-idle-states = <&CPU_SLEEP_0>; > > > > clocks = <&apcs>; > > > > operating-points-v2 = <&cpu_opp_table>; > > > > #cooling-cells = <2>; > > > > @@ -134,7 +134,7 @@ > > > > reg = <0x2>; > > > > next-level-cache = <&L2_0>; > > > > enable-method = "psci"; > > > > - cpu-idle-states = <&CPU_SPC>; > > > > + cpu-idle-states = <&CPU_SLEEP_0>; > > > > clocks = <&apcs>; > > > > operating-points-v2 = <&cpu_opp_table>; > > > > #cooling-cells = <2>; > > > > @@ -146,7 +146,7 @@ > > > > reg = <0x3>; > > > > next-level-cache = <&L2_0>; > > > > enable-method = "psci"; > > > > - cpu-idle-states = <&CPU_SPC>; > > > > + cpu-idle-states = <&CPU_SLEEP_0>; > > > > clocks = <&apcs>; > > > > operating-points-v2 = <&cpu_opp_table>; > > > > #cooling-cells = <2>; > > > > @@ -160,8 +160,9 @@ > > > > idle-states { > > > > entry-method="psci"; > > > > > > Please add a space before and after "=". > > > > > > > > > > > - CPU_SPC: spc { > > > > + CPU_SLEEP_0: cpu-sleep-0 { > > > > > > While I like your idea of using power state names from > > > Server Base System Architecture document (SBSA) where applicable, > > > does each qcom power state have a matching state in SBSA? > > > > > > These are the qcom power states: > > > https://source.codeaurora.org/quic/la/kernel/msm-4.4/tree/Documentation/devicetree/bindings/arm/msm/lpm-levels.txt?h=msm-4.4#n53 > > > > > > Note that qcom defines: > > > "wfi", "retention", "gdhs", "pc", "fpc" > > > while SBSA simply defines "idle_standby" (aka wfi), "idle_retention", "sleep". > > > > > > Unless you know the equivalent name for each qcom power state > > > (perhaps several qcom power states are really the same SBSA state?), > > > I think that you should omit the renaming from this patch series. > > > > That is what SLEEP_0, SLEEP_1, SLEEP_2 could be used for. > > Ok, sounds good to me. > > > > > IOW, all these qcom definitions are nicely represented in the > > state-name and we could simply stick to SLEEP_0, SLEEP_1 for the node > > names. There is wide variability in the the names of the qcom idle > > states across SoC families downstream, so I'd argue against using > > those for the node names. > > > > Just for cpu states (non-wfi) I see the use of the following names > > downstream across families. The C seems to come from x86 > > world[1]: > > > > - C4, standalone power collapse (spc) > > - C4, power collapse (fpc) > > - C2D, retention > > - C3, power collapse (pc) > > - C4, rail power collapse (rail-pc) > > > > [1] https://www.hardwaresecrets.com/everything-you-need-to-know-about-the-cpu-c-states-power-saving-modes/ > > Indeed, there seems to be mixed names used, I've also seen "fpc-def". > > So, you have convinced me. > > > Kind regards, > Niklas Can I take that as a Reviewed-by?