From patchwork Fri Feb 9 08:58:10 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Viresh Kumar X-Patchwork-Id: 871250 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=devicetree-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=linaro.org header.i=@linaro.org header.b="Yj02JJzr"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 3zd8Bg4S8gz9s72 for ; Fri, 9 Feb 2018 19:59:23 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752317AbeBII7M (ORCPT ); Fri, 9 Feb 2018 03:59:12 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:43138 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752261AbeBII7H (ORCPT ); Fri, 9 Feb 2018 03:59:07 -0500 Received: by mail-pg0-f68.google.com with SMTP id f6so3198256pgs.10 for ; Fri, 09 Feb 2018 00:59:07 -0800 (PST) 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 :in-reply-to:references; bh=ONKnLCAaG0t+JU6W7X7N6p1epEJROvhwPld3UMfebkQ=; b=Yj02JJzr9V5Q7l9HHeazPdrrB+1DuYns4If7CrFSNUHlwsDrFUsO5fV8oUWQCE3Evs zg5EMM92HoIU1J8Y/S+x3LNPhSUDZsoCExtI2yEcv0Gfg2J7xOD45BMIpYe0Y2Fe5BOK ifjio2dAPjGdWUMFh74SirDnvW82rLguFkNBs= 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:in-reply-to:references; bh=ONKnLCAaG0t+JU6W7X7N6p1epEJROvhwPld3UMfebkQ=; b=CuiurkQMvbzNjtRLvp1o7/d6rgsm14Wb7OwQTQJ8q3rS0gvo6qxJiee0XLYgq2XaCN ZpnJQ8Iy5fLpeCdm/Y4iWgmX7zXEGsIrSG6+yg5APbbvavazIF3KlbE42jITFTwsSlGT vo76sBOmaNtqYIHZWMoUQuXNcZwfHVE4+UbyuN0Lco0XnDGC4hgU6awcRx8ri/Podzo8 OeKcLPZd/aKUhx9/uTiQmk1oICip6tc9v5cxDs2/ezburUSh7p/qyMFisg6nq7FflFKy gqJeHKCDQhcix20ImuLJ74nwEs5YbxXkpYOrNrtHqpuiM2GQe5k2cnmhp/Cw3uzRcBMB js7A== X-Gm-Message-State: APf1xPB9eENaxR7A9pwOu9KWsHGd5kORX57ywvvsH5NcYwLwv/y56OXR 5+9Jcu0S/eD0AQAbt9FWbyWZNA== X-Google-Smtp-Source: AH8x225hu7i2Y7PNK4xsdM3oynTs6AU2HMZiDprESJ/gSERxMzUE//0ESq9nMrXL0WsvqLNBabHRfA== X-Received: by 10.98.107.71 with SMTP id g68mr2065426pfc.96.1518166746878; Fri, 09 Feb 2018 00:59:06 -0800 (PST) Received: from localhost ([122.172.61.199]) by smtp.gmail.com with ESMTPSA id h69sm4490875pfe.20.2018.02.09.00.59.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Feb 2018 00:59:06 -0800 (PST) From: Viresh Kumar To: Rafael Wysocki , Zhang Rui , Eduardo Valentin Cc: Viresh Kumar , linux-pm@vger.kernel.org, Vincent Guittot , Mark Rutland , Rob Herring , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org Subject: [PATCH 10/10] dt-bindings: thermal: Remove "cooling-{min|max}-level" properties Date: Fri, 9 Feb 2018 14:28:10 +0530 Message-Id: <0ec53640f1a09e6e0d7aa1a21d1a3266c3c209c7.1518166039.git.viresh.kumar@linaro.org> X-Mailer: git-send-email 2.15.0.194.g9af6a3dea062 In-Reply-To: References: In-Reply-To: References: Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org The "cooling-min-level" and "cooling-max-level" properties are not parsed by any part of kernel currently and the max cooling state of a CPU cooling device is found by referring to the cpufreq table instead. Remove the unused bindings. Signed-off-by: Viresh Kumar Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/thermal/thermal.txt | 16 +--------------- 1 file changed, 1 insertion(+), 15 deletions(-) diff --git a/Documentation/devicetree/bindings/thermal/thermal.txt b/Documentation/devicetree/bindings/thermal/thermal.txt index 1719d47a5e2f..cc553f0952c5 100644 --- a/Documentation/devicetree/bindings/thermal/thermal.txt +++ b/Documentation/devicetree/bindings/thermal/thermal.txt @@ -55,8 +55,7 @@ of heat dissipation). For example a fan's cooling states correspond to the different fan speeds possible. Cooling states are referred to by single unsigned integers, where larger numbers mean greater heat dissipation. The precise set of cooling states associated with a device -(as referred to by the cooling-min-level and cooling-max-level -properties) should be defined in a particular device's binding. +should be defined in a particular device's binding. For more examples of cooling devices, refer to the example sections below. Required properties: @@ -69,15 +68,6 @@ For more examples of cooling devices, refer to the example sections below. See Cooling device maps section below for more details on how consumers refer to cooling devices. -Optional properties: -- cooling-min-level: An integer indicating the smallest - Type: unsigned cooling state accepted. Typically 0. - Size: one cell - -- cooling-max-level: An integer indicating the largest - Type: unsigned cooling state accepted. - Size: one cell - * Trip points The trip node is a node to describe a point in the temperature domain @@ -226,8 +216,6 @@ cpus { 396000 950000 198000 850000 >; - cooling-min-level = <0>; - cooling-max-level = <3>; #cooling-cells = <2>; /* min followed by max */ }; ... @@ -241,8 +229,6 @@ cpus { */ fan0: fan@48 { ... - cooling-min-level = <0>; - cooling-max-level = <9>; #cooling-cells = <2>; /* min followed by max */ }; };