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=-3.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_GIT autolearn=no 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 21E0BFA3735 for ; Thu, 17 Oct 2019 12:27:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DEE3E21835 for ; Thu, 17 Oct 2019 12:27:45 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="e5vaYirq" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2406042AbfJQM1p (ORCPT ); Thu, 17 Oct 2019 08:27:45 -0400 Received: from mail-pf1-f194.google.com ([209.85.210.194]:41081 "EHLO mail-pf1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2406212AbfJQM1p (ORCPT ); Thu, 17 Oct 2019 08:27:45 -0400 Received: by mail-pf1-f194.google.com with SMTP id q7so1560194pfh.8 for ; Thu, 17 Oct 2019 05:27:44 -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; bh=xXhwH1GxOvSRaIU9bxiCbTTSTX9/U+uLuT7KdF8P4CM=; b=e5vaYirqBd7rd5gjNOfLQGnvgXImhmAvNARYpjIdWHGASWHw0wjASMXczXxCHszFi2 3MXKT6fzXK7e2X2AssVRAaZD431e8zPVVNYDOhlm8uy6duNfEXFaLTyp4+7zVEIWbGEU x1eUOLGL4M+uPER1/2PgNcKqx/XeurVzaU/bIWELbvOcpQA4GHpTKESFHiZ/bd2Q1ugo ecubimKIgw/orjyVxBxwoIgtI6L07rDyU9VgqAG9c2ekfWCO2gTfp0F5H4adpNLst/UZ uh4ArkLfiYCHdFaUPfyHQmUEAyTl2ap8ocOeNSiV7BTDcPZfNsYHVRA/nMSnEMjV6+vx SAOg== 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; bh=xXhwH1GxOvSRaIU9bxiCbTTSTX9/U+uLuT7KdF8P4CM=; b=nubR/9aA3SxxBr15+HvxprFomtkQeRYF+NTKaPn+YiIWerp7Aws/e+cHWKzUtVGra/ mkgTL+Y9kkxmiANSKL1Wpz9a4DxoCapaPxeWALLRK9m/MOiVdyfGjLxooxX+2L9Rt54y eD2fVRuZs+BR7P9LhK5//ItrmpNztRO2vKSuCIg67quSKgLjAxxlLzvv8US3OG1CMcaK yfLKbC82oEEn1edNsNWwasDhAFQNf3cmMTC6xl9QEOdaep0QHJLTEC7Lb5Y1brCwmhM+ Yxh5X5X9ZMwbHe2RkJaviYCKCXFJTxE0EmhyuWpz48i1q026tNq0epQaC3idL/QmLBH3 jnZQ== X-Gm-Message-State: APjAAAXf3qevluYaKChbooPJXU5FCUaj/dZWDMVmglv23UdxgVdx52wt UYfGp4U7OFGzMQZXbncIJjlOlQ== X-Google-Smtp-Source: APXvYqwrbDVTljiTae+qiRKHjetQf9tZw02mbcbYDsSUdv32aHy+VpABwoL4ZWvfAIZW85NEPPclAg== X-Received: by 2002:aa7:9acb:: with SMTP id x11mr3558307pfp.249.1571315264027; Thu, 17 Oct 2019 05:27:44 -0700 (PDT) Received: from localhost ([49.248.54.231]) by smtp.gmail.com with ESMTPSA id h2sm4838518pfq.108.2019.10.17.05.27.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 17 Oct 2019 05:27:43 -0700 (PDT) From: Amit Kucheria To: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, daniel.lezcano@linaro.org, viresh.kumar@linaro.org, sudeep.holla@arm.com, bjorn.andersson@linaro.org, edubezval@gmail.com, agross@kernel.org, tdas@codeaurora.org, swboyd@chromium.org, ilina@codeaurora.org, "Rafael J. Wysocki" , Amit Kucheria , Zhang Rui Cc: linux-clk@vger.kernel.org, linux-doc@vger.kernel.org, linux-pm@vger.kernel.org Subject: [PATCH v3 0/6] Initialise thermal framework and cpufreq earlier during boot Date: Thu, 17 Oct 2019 17:57:32 +0530 Message-Id: X-Mailer: git-send-email 2.17.1 Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org Changes since v2: - Missed one patch when posting v2. Respinning. Changes since v1: - Completely get rid of netlink support in the thermal framework. - This changes the early init patch to a single line - change to core_initcall. Changed authorship of patch since it is nothing like the original. Lina, let me know if you feel otherwise. - I've tested to make sure that the qcom-cpufreq-hw driver continues to work correctly as a module so this won't impact Android's GKI plans. - Collected Acks Device boot needs to be as fast as possible while keeping under the thermal envelope. Now that thermal framework is built-in to the kernel, we can initialize it earlier to enable thermal mitigation during boot. We also need the cpufreq HW drivers to be initialised earlier to act as the cooling devices. This series only converts over the qcom-hw driver to initialize earlier but can be extended to other platforms as well. Amit Kucheria (6): thermal: Remove netlink support thermal: Initialize thermal subsystem earlier cpufreq: Initialise the governors in core_initcall cpufreq: Initialize cpufreq-dt driver earlier clk: qcom: Initialise clock drivers earlier cpufreq: qcom-hw: Move driver initialisation earlier .../driver-api/thermal/sysfs-api.rst | 26 +---- drivers/clk/qcom/clk-rpmh.c | 2 +- drivers/clk/qcom/gcc-qcs404.c | 2 +- drivers/clk/qcom/gcc-sdm845.c | 2 +- drivers/cpufreq/cpufreq-dt-platdev.c | 2 +- drivers/cpufreq/cpufreq_conservative.c | 2 +- drivers/cpufreq/cpufreq_ondemand.c | 2 +- drivers/cpufreq/cpufreq_performance.c | 2 +- drivers/cpufreq/cpufreq_powersave.c | 2 +- drivers/cpufreq/cpufreq_userspace.c | 2 +- drivers/cpufreq/qcom-cpufreq-hw.c | 2 +- drivers/thermal/thermal_core.c | 110 +----------------- include/linux/thermal.h | 11 -- 13 files changed, 22 insertions(+), 145 deletions(-) -- 2.17.1