From patchwork Thu Jul 25 10:41:30 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Niklas Cassel X-Patchwork-Id: 169692 Delivered-To: patch@linaro.org Received: by 2002:a92:4782:0:0:0:0:0 with SMTP id e2csp11464375ilk; Thu, 25 Jul 2019 03:42:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqzAya0h7pVh4g7qRRS2aEUDtepjPL47ZpG7KSFtop+Do5P9m2Chvw/zaG5kXyqFsjxM/1Ht X-Received: by 2002:aa7:8481:: with SMTP id u1mr15277281pfn.243.1564051321331; Thu, 25 Jul 2019 03:42:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564051321; cv=none; d=google.com; s=arc-20160816; b=dSP5IPCMplsmr1M8dFqpE6rE88T7r1slnfDBePYYX4nl7xETj+0zLxUJPDYpygTZQT yU+U8DZXl6ejZyRxH74ZN5MgGfjRHlwyWH5PZ6kOA+Abv/VRawmlbWmF3eqksXUkcsEJ HTGRM4divOtDUVcr7HRQLvcqUuV+LXeB09RSBsEWtAoyLG9X65Jnpw6o5NIuyjg3dhjm VwJ8QXHIhretj35QaXwoM0Raogbden0jptKwdZEsi0AvteY1g1XU8MXwLxytjChRfhX5 xarEqQk9YaWxJVP9I+XSTJUrYdTeWSJriyV/GYfEG5LHxN8XrIVT8L3/0hfYGzFRny66 CKWQ== 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:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=HkR5c7pg+yPuBi2NQ0G3gtI0G9f3RBJtD6x7Jmgjehc=; b=Igzs6fv4CV8H8dUjsqA/8vZNiqxB/clJ/e6pV7g7ZGo4WvqPiQlacAEFzgrNRawkjC w3sDqXHGqqu3MDptArCG9+pTng/vAmuMCQ4YCdu3oQZu8g/JU0ZuzutAzahIB9M2RSQO 3Cq3cWAiJZijsVugI9u/cM81mnqzS0xkMMw8tJUuO6QkbjXCt5sxOxb7lnxLQN/b0qgX 4GO+nEa6P+lFVS0x9c3kkTABxKl5lR3TowqQiKgTdOFV/1PgaJWrKYU5GTYAXwfXK3L0 xAck8WfP3ihW3nZnFeEXzNRU7jqyO9uR6hhh9NkgZzmHS/Pw4aNjDwiYuCVn7X28Xwt0 f0oA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=ZLmJvOdi; spf=pass (google.com: best guess record for domain of linux-pm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-pm-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 r185si15889653pgr.506.2019.07.25.03.42.01; Thu, 25 Jul 2019 03:42:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-pm-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=ZLmJvOdi; spf=pass (google.com: best guess record for domain of linux-pm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-pm-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 S2387725AbfGYKl7 (ORCPT + 11 others); Thu, 25 Jul 2019 06:41:59 -0400 Received: from mail-lj1-f194.google.com ([209.85.208.194]:37239 "EHLO mail-lj1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387919AbfGYKl6 (ORCPT ); Thu, 25 Jul 2019 06:41:58 -0400 Received: by mail-lj1-f194.google.com with SMTP id z28so47600818ljn.4 for ; Thu, 25 Jul 2019 03:41:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=HkR5c7pg+yPuBi2NQ0G3gtI0G9f3RBJtD6x7Jmgjehc=; b=ZLmJvOdiUYFEJm4i4mbuyrMY2o6mclBz5DhrFLFaBKoorOt5B6ZiY2psz1JuTtwaFZ 5kxpMa2cjNwA8rRi8P5H/op90KLl/aDbsFG69P0RY+FnENSQN1Xf2mdDymrZHkplNyRg uK5KguUErED95Wmi4b3Ok+n5HeY/cSZEjPm+UMupvLcjVs7VJadZySzkdqoJDY9DOSKA LFk5vCN6UOEQ/tjgt/gFuQQdJMvCeLuja7fHjZm8GWioL6xwxmQMzVvNPskaG9fzT/0B 85I2zrX1TaqE8klv4DrcceVpijzG3OYw4sIEM5/16ijVOGfz0sZjxMakrjAc++87GIQP EuGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=HkR5c7pg+yPuBi2NQ0G3gtI0G9f3RBJtD6x7Jmgjehc=; b=CkGfIvlhdH4HsWTyqIBahHQYqaODo7zXWpuoDyU7rGJ4DDsqYsrwxlbFK/stvaVfl2 sLNnAJMN8/KA/br6HVjvLzB4EregN+afnaFaSwOxj/lipPQiTqveYuaXIHlTgJIpbPL3 QuLEHIWVRwBOsIMSIls3MEMxyxOaqDf8pEHSIMi7sACTbhFYVRckawiwZGseiyIr0H2o IJZPdhW5BHDdDEPM0/F/VKrQ/FsC1hDgEAWY+kKjjD7coOnYzNH5h5b62Zq4+jiRZSoW qhDoEPBLj68oOIfSxzz3wakxQX4QcPG/Y9m651nv/4aGQEJ8g0BpvmebGYN4USGiEFEM OYAQ== X-Gm-Message-State: APjAAAVtBgaJr7VRPGM+xKGocPfFsuCbDhukPo1khFRqI4G0SzuxTAcW 9wzZWASgIDZkrthtTuZnGLP0PQ== X-Received: by 2002:a2e:534a:: with SMTP id t10mr8150715ljd.109.1564051317095; Thu, 25 Jul 2019 03:41:57 -0700 (PDT) Received: from localhost.localdomain (ua-83-226-44-230.bbcust.telenor.se. [83.226.44.230]) by smtp.gmail.com with ESMTPSA id b6sm8268306lfa.54.2019.07.25.03.41.56 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Thu, 25 Jul 2019 03:41:56 -0700 (PDT) From: Niklas Cassel To: Viresh Kumar , Nishanth Menon , Stephen Boyd , Andy Gross , Ilia Lin Cc: linux-arm-msm@vger.kernel.org, jorge.ramirez-ortiz@linaro.org, bjorn.andersson@linaro.org, ulf.hansson@linaro.org, Sricharan R , Niklas Cassel , Rob Herring , Rob Herring , Mark Rutland , linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 02/14] dt-bindings: cpufreq: Re-organise kryo cpufreq to use it for other nvmem based qcom socs Date: Thu, 25 Jul 2019 12:41:30 +0200 Message-Id: <20190725104144.22924-3-niklas.cassel@linaro.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190725104144.22924-1-niklas.cassel@linaro.org> References: <20190725104144.22924-1-niklas.cassel@linaro.org> MIME-Version: 1.0 Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org From: Sricharan R The kryo cpufreq driver reads the nvmem cell and uses that data to populate the opps. There are other qcom cpufreq socs like krait which does similar thing. Except for the interpretation of the read data, rest of the driver is same for both the cases. So pull the common things out for reuse. Signed-off-by: Sricharan R [niklas.cassel@linaro.org: split dt-binding into a separate patch and do not rename the compatible string.] Signed-off-by: Niklas Cassel Reviewed-by: Ilia Lin Reviewed-by: Rob Herring --- Changes since V1: -Picked up tags. .../opp/{kryo-cpufreq.txt => qcom-nvmem-cpufreq.txt} | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) rename Documentation/devicetree/bindings/opp/{kryo-cpufreq.txt => qcom-nvmem-cpufreq.txt} (98%) -- 2.21.0 diff --git a/Documentation/devicetree/bindings/opp/kryo-cpufreq.txt b/Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt similarity index 98% rename from Documentation/devicetree/bindings/opp/kryo-cpufreq.txt rename to Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt index c2127b96805a..198441e80ba8 100644 --- a/Documentation/devicetree/bindings/opp/kryo-cpufreq.txt +++ b/Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt @@ -1,13 +1,13 @@ -Qualcomm Technologies, Inc. KRYO CPUFreq and OPP bindings +Qualcomm Technologies, Inc. NVMEM CPUFreq and OPP bindings =================================== -In Certain Qualcomm Technologies, Inc. SoCs like apq8096 and msm8996 -that have KRYO processors, the CPU ferequencies subset and voltage value -of each OPP varies based on the silicon variant in use. +In Certain Qualcomm Technologies, Inc. SoCs like apq8096 and msm8996, +the CPU frequencies subset and voltage value of each OPP varies based on +the silicon variant in use. Qualcomm Technologies, Inc. Process Voltage Scaling Tables defines the voltage and frequency value based on the msm-id in SMEM and speedbin blown in the efuse combination. -The qcom-cpufreq-kryo driver reads the msm-id and efuse value from the SoC +The qcom-cpufreq-nvmem driver reads the msm-id and efuse value from the SoC to provide the OPP framework with required information (existing HW bitmap). This is used to determine the voltage and frequency value for each OPP of operating-points-v2 table when it is parsed by the OPP framework.