Received: by 10.223.185.116 with SMTP id b49csp3372321wrg; Tue, 13 Feb 2018 01:20:40 -0800 (PST) X-Google-Smtp-Source: AH8x2260hH6xSX/f0gVoRCEC/M/MCwRs6XTRmXQXKOAyRrhCRn5Fv+irsJinmcSxAMLfM3Syci+c X-Received: by 10.99.112.20 with SMTP id l20mr493470pgc.412.1518513639920; Tue, 13 Feb 2018 01:20:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518513639; cv=none; d=google.com; s=arc-20160816; b=pMsrGmGOIj2MECvC+Bp3Ylw/xiYBNN04gr8r8v7wUUtzODwe+kEZKADJUt6zPBEDGM DPLcdH/vIBHWiaZr1wbqC0VkMNUNIhO4VYc8RpExvlP769ymQluOdSXUAO8U4s0ZXBx3 y7EjeKEQq5VEKr9YBoZZfwokBRAcmE6jskqTStD4n4YtTJHNoUaDG98vBwOLwgvXArtr svoTbsGWHfBIzubFwUrKEET08gcDSGEpLG2nGliD/UBVElIlslNLS2QpPUoHZjwZmcWz rsoDavJByxtAc1F6PJw4DPjRQJuBgoGjxZKjpfE04ijEmAXbkAxz/XfbrO7NJF7LWQcI dS9Q== 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 :references:in-reply-to:mime-version:arc-authentication-results; bh=OT4XSM10l9TNRfInc8uLqF4AWS1H74/rLJDoeY+8PoY=; b=iwalv/UmWTLT7TUM7qYe4m4+yvMs+M6a0eD5aXnDK8Cl/26f54QEIIuXRpgo2DWAxn wPmfwzR9ggL2bdtkGKJ6r8TNjtjSlbxurPZuNrAv1M8lXPivPYTDyPPOelfgxFdF2lgP p9beaETUjcPfsp/gLYJzdOJkGZC108y6pZevXUZh39k2z1mOTC1SsOimSWiqB8sTfGpF XlWNUdh8gNSo5260/Axj9S+cLcOyiwDgCyQ7cqHSZ1lCDSLPMJSmQcBp569Hf3hSd58E QY7m3WGJBeDH3O6Wwk8jUEd8YE6kY3lpRL0LDNviMO6RmKhuTgqjhPnpiDHZBztp1x4/ 5RUQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d9si1264038pfb.104.2018.02.13.01.20.25; Tue, 13 Feb 2018 01:20:39 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934660AbeBMJTX (ORCPT + 99 others); Tue, 13 Feb 2018 04:19:23 -0500 Received: from mail-wm0-f68.google.com ([74.125.82.68]:38929 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934331AbeBMJTQ (ORCPT ); Tue, 13 Feb 2018 04:19:16 -0500 Received: by mail-wm0-f68.google.com with SMTP id b21so14705527wme.4; Tue, 13 Feb 2018 01:19:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OT4XSM10l9TNRfInc8uLqF4AWS1H74/rLJDoeY+8PoY=; b=ccLZvqBnuim7Sm4h9+n7zzZFt7/11yKp32gxi0IS8wm03Yj7bQLGt9TzCUjflZcu15 zBRoxaZREd6yWZpyPB3OdpQm10Z/EuMh8Vhmq0UTEDLOnIQ/XJf4XoGiIm8FVKL28inm 5LRrGdqSN3Bfxn6qHMlYwJ/r03NtcumHvFWCW4nl2+hY6eJxlfS5Bm6vq3bLvzsYE9a2 FQ2pNQ03WuxB63X7ws2zVTl9tfrgXLZpCkIAeam6A87Lp96HB3T4NVJciOMTAsYc8Err gea0Z04QWHStgPKm/5S6NzR12nzziVRAu6UkEuaaLTPkEMSNohh6plS9s+nNUI1D5JNm E52w== X-Gm-Message-State: APf1xPCL/EncjWxsg26ILWf6xHVIRNotdaVF720+2fKNc67p1y8OJuzL E5+IHvyKsd5lFT4gq0sQnopGEz6d X-Received: by 10.80.151.137 with SMTP id e9mr1277349edb.102.1518513554670; Tue, 13 Feb 2018 01:19:14 -0800 (PST) Received: from mail-wr0-f178.google.com (mail-wr0-f178.google.com. [209.85.128.178]) by smtp.gmail.com with ESMTPSA id d30sm6310621edd.90.2018.02.13.01.19.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Feb 2018 01:19:14 -0800 (PST) Received: by mail-wr0-f178.google.com with SMTP id s5so17896300wra.0; Tue, 13 Feb 2018 01:19:13 -0800 (PST) X-Received: by 10.223.168.46 with SMTP id l43mr626207wrc.118.1518513553079; Tue, 13 Feb 2018 01:19:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.208.197 with HTTP; Tue, 13 Feb 2018 01:18:52 -0800 (PST) In-Reply-To: <20180213091333.rq4rtvvkwppn5ypu@flea.lan> References: <4d489d040ec1fc3821d8e4bf31ffcc2eebfa41e1.1518166039.git.viresh.kumar@linaro.org> <20180213091333.rq4rtvvkwppn5ypu@flea.lan> From: Chen-Yu Tsai Date: Tue, 13 Feb 2018 17:18:52 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 04/10] ARM: dts: sun[4-7]i: Remove "cooling-{min|max}-level" for CPU nodes To: Maxime Ripard , Rob Herring , Mark Rutland Cc: Viresh Kumar , Rafael Wysocki , "open list:THERMAL" , Vincent Guittot , Eduardo Valentin , Zhang Rui , linux-arm-kernel , devicetree , Daniel Lezcano , linux-kernel 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 Tue, Feb 13, 2018 at 5:13 PM, Maxime Ripard wrote: > On Fri, Feb 09, 2018 at 02:28:04PM +0530, Viresh Kumar wrote: >> The "cooling-min-level" and "cooling-max-level" properties are not >> parsed by any part of the kernel currently and the max cooling state of >> a CPU cooling device is found by referring to the cpufreq table instead. That doesn't mean that other systems aren't using it. It's still part of the device tree binding. Last I checked, while they are optional, they aren't deprecated. Any comments from the device tree maintainers? >> >> Remove the unused properties from the CPU nodes. >> >> Signed-off-by: Viresh Kumar > > Applied, thanks! > Maxime > > -- > Maxime Ripard, Bootlin (formerly Free Electrons) > Embedded Linux and Kernel engineering > http://bootlin.com