Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3780195imu; Mon, 14 Jan 2019 08:55:43 -0800 (PST) X-Google-Smtp-Source: ALg8bN6xNYahHBYqnuBEfFgSCs/GwaEWkpbSFcyrw+HqSamupaP7WeKMCRnvwTe+ml2ctFjCREHi X-Received: by 2002:a17:902:292b:: with SMTP id g40mr26548519plb.82.1547484943668; Mon, 14 Jan 2019 08:55:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547484943; cv=none; d=google.com; s=arc-20160816; b=nm3QfKKF6BYM1ni1uHYT02XlZuI0WFLK5CsT5A/Fkdr0OvQ9qVz3lvDDaFfu0uFq2K UaeIaqPH5efcuD7+xj45FPUjRpu9veg1SRDevAkHLY3CUNLQkdb8wz55G89ufcC8GLGK pkK8N10h1/V2r09f3L2M3S+1iW79LBV9m6KzB7X9A2EGQKzy3Z1nvApx0ErnoOBiLDj+ ixWNOdCambicWvSNH6vi5FmnOOtavboGepV6F88UDpJ7J136gnRVUcdbm1Pxe2lfKMee AzAoXZ4q5l4taO2KkOC64F9uuyG4N5VRD4aliwMJOftMplfb/LvQ82fgG568lTHHk0Fg Y04Q== 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=+tUttfEcOxtLxbzMjVC+wuWOy2MPi+P43KgBXi8LdE4=; b=ovvhVyoAXtn9/L1AZy3G8HVLj+vPmc+WMSuJOt1vdnnA0/WYJA98w+uNoBXsiUMFOQ McKXzc8O8n13gs/VDuoS1DtIqxytLD78Qxw0OC+dfKhoYEXxfgKnY363SQLbRjgx8gTj G/9N6NkcAEv6QsBQyqlHk28TePQ8iLJXFVc8Ewgy4t3oc0GerTzNLQlE4gQIc+3RCPlV fx6Vfy1Hoj5kxsVADBZyfahog/t+yxxsbv1zLtHTcJC3QlFyHX7oJ3EVlqDRM0IAdPnn kfOCHU7cU2WR6ZEoWHE+in8gigwT0QEOWWXbpTxsiX2MYS1IvSvUya28FrCCgIAQyWUW 5w9Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Ib3tAHyV; 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 q14si693005pgq.197.2019.01.14.08.55.28; Mon, 14 Jan 2019 08:55:43 -0800 (PST) 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=Ib3tAHyV; 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 S1726767AbfANQxH (ORCPT + 99 others); Mon, 14 Jan 2019 11:53:07 -0500 Received: from mail-vk1-f193.google.com ([209.85.221.193]:32792 "EHLO mail-vk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726674AbfANQxH (ORCPT ); Mon, 14 Jan 2019 11:53:07 -0500 Received: by mail-vk1-f193.google.com with SMTP id d201so5027566vka.0 for ; Mon, 14 Jan 2019 08:53:05 -0800 (PST) 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=+tUttfEcOxtLxbzMjVC+wuWOy2MPi+P43KgBXi8LdE4=; b=Ib3tAHyViiKppL7q5i1Whj2NqOK04EE8ggruqMru05Ly7C21BjrJIdyvJ61mRvebSs KwLETgmPLqFKX5qVa8cCHuVPcx4d/qN3qPumWVTkByoFjwbhHDS8BzZhaGWjGueD9aNe Evg0bR9kD1qdkEPJH4o5Of3pXL4xcmOD0FTzk= 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=+tUttfEcOxtLxbzMjVC+wuWOy2MPi+P43KgBXi8LdE4=; b=eNPn6JUU9v0CSatcwzTr/RRsL174rdbnML0YohNwqac5kHq8BRf/d3T2uMQwGrcQUk P4pAV+j774T3b6iwyQgoznF0Tvr7scneXYH2yVLb2s5Ry1z9a/ZTpmE74j83YMUV2uZi UiRmq5bDwgBjOycot1NomRYepyLV7ke16QLR4px8GYqaRLbgZjYLU5oMmyo+nMaMtz/F bauyo+R1wSZOmrPrP4covQSMUuofci9GXfN6XarEYs78iky0Rf8k+tZquCye77tHRxXJ 4xGWmsjEqMIVn3hEoCrgFiDhCXceS9tMNKLGSUKW3PFzl3sN07ZB4MZ6Ydly6E2Hv/iX g5Cg== X-Gm-Message-State: AJcUukciVquOECDGpveTEl8AouqcvKy+uhXPqKqrj5EmPrXhKfiw3fcd U0G5cjix7NWFpoy/A3t6bnFNkavMciEu245UzXUp7g== X-Received: by 2002:a1f:9ec9:: with SMTP id h192mr10097312vke.68.1547484785252; Mon, 14 Jan 2019 08:53:05 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Amit Kucheria Date: Mon, 14 Jan 2019 22:22:54 +0530 Message-ID: Subject: Re: [PATCH v2 0/9] Thermal throttling for SDM845 To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , linux-arm-msm , Bjorn Andersson , Viresh Kumar , Eduardo Valentin , Andy Gross , Taniya Das , Stephen Boyd , Doug Anderson , Matthias Kaehlcke , "Rafael J. Wysocki" , Daniel Lezcano , David Brown , Javi Merino , Mark Rutland , Rob Herring , Zhang Rui , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "open list:CPU FREQUENCY DRIVERS" 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 Mon, Jan 14, 2019 at 4:04 PM Amit Kucheria wrote: > > On Mon, Jan 14, 2019 at 3:57 PM Rafael J. Wysocki wrote: > > > > On Mon, Jan 14, 2019 at 11:22 AM Amit Kucheria wrote: > > > > > > Add support for thermal throttling on SDM845. > > > > > > We introduce a generic flag to be used by cpufreq drivers to tell the > > > cpufreq core to auto-register a thermal cooling device. > > > > > > There are a few miscellaneous fixes to keep checkpatch happy. > > > > > > If this approach is acceptable I can send a series converting other cpufreq > > > drivers to use this flag and get rid of driver code. > > > > > > Amit Kucheria (9): > > > [ALREADY QUEUED] cpufreq: qcom-hw: Move to device_initcall > > > drivers: thermal: of-thermal: Print name of device node with error > > > drivers: cpufreq: Add thermal_cooling_device pointer to struct > > > cpufreq_policy > > > cpufreq: Add a flag to auto-register a cooling device > > > cpufreq: Replace open-coded << with BIT() > > > cpufreq: qcom-hw: Register as a cpufreq cooling device > > > arm64: dts: sdm845: Increase alert trip point to 95 degrees > > > arm64: dts: sdm845: wireup the thermal trip points to cpufreq > > > thermal: cpu_cooling: Clarify error message > > > > > > arch/arm64/boot/dts/qcom/sdm845.dtsi | 193 +++++++++++++++++++++++---- > > > drivers/cpufreq/cpufreq.c | 13 ++ > > > drivers/cpufreq/qcom-cpufreq-hw.c | 5 +- > > > drivers/thermal/cpu_cooling.c | 2 +- > > > drivers/thermal/of-thermal.c | 4 +- > > > include/linux/cpufreq.h | 34 +++-- > > > 6 files changed, 210 insertions(+), 41 deletions(-) > > > > Would it be possible to split this series so as to put the cpufreq > > patches separately? > > Sure, will send out another version. I've now sent out a separate series just tackling the auto-registration feature of a cooling device[1]. So the only bits in this series needing separate review are patches 2, 7,8 and 9. I'll wait couple of days to get some review on the other series before sending out another version of the remaining patches listed above. Feel free to comment on them in this thread, in the meanwhile. Thanks. [1] https://lore.kernel.org/patchwork/cover/1031909/