Received: by 10.223.185.116 with SMTP id b49csp4041487wrg; Mon, 19 Feb 2018 10:02:22 -0800 (PST) X-Google-Smtp-Source: AH8x224+EEoDEdNg0geLkZ0mpvgszHHfTOff1V9t1g45ofIiHBfHbxZKzir/3Uwe97BJsAgvqCfn X-Received: by 10.98.141.208 with SMTP id p77mr15234820pfk.5.1519063342413; Mon, 19 Feb 2018 10:02:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519063342; cv=none; d=google.com; s=arc-20160816; b=vDfFK2muONFN41pmvodzkyO/5/NYMVU9QKrnC5PdBtSeOS0VdKdH+zouc74p0FE/Vp h3HmdFAd+9HZjt7vAe62cqsUNA19twJxPFi2QdBuoMm3aKJFrK9aLE7+ejOdQswfz11G 1TEIG+AV6IeATZk+okLp+9oI9Rr+uq0S8/hByVBODhmS/EB3WyFDBbsnElgp5CvFcn2U nJAu2qK4Qln17QX9XAm6zW2sYNYbPeXUtAEfpRkVPF/Vqyu2hRyNlzWbXGAgOLggTqOa 7+9/HnrlqliXD/fp3V4MkSAOrlfg6CPtqv4Nbfxjlc3rsgfSBF7yANWdIjvkBGKCBND0 Vrgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=nXTiDVSGp81He1Cr5hPKmlgofOXvIjQsYYxZ/aDpDCg=; b=JkKH6srsKhsVSJS95FasEpVuvBEIq0ITheYWBeiP3kShd8ASTv8dTklVsQ4n7vz40i TODHtXUM/2qfgQyOD8wEh+KLgNZT6hk1Z7ZFnteb+fcLC/eVenHNHGhKDNvhHq/AfH5e zXdBgCohTQVUwhcgC/5SGwdbZThWqG/Vg2fOIiNIJP5mUAjs388r6DrBlhf8nkokSQhp eJ7tjA6Ii4gWS97VpDUJebsqUgz/bPvp5p97sv8osZExcZ8IVslNNCq3fpjRFp0dEA4m tLHhFyVRAR3GZe1btK8Cj1wUOFtcRug91OnVLaCdx+5huLZ1ZO8J/HGxPh/S5yKWhmzo giKQ== 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 f9-v6si4002631pln.211.2018.02.19.10.02.05; Mon, 19 Feb 2018 10:02:22 -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 S1753375AbeBSSB2 (ORCPT + 99 others); Mon, 19 Feb 2018 13:01:28 -0500 Received: from mail-ot0-f171.google.com ([74.125.82.171]:35405 "EHLO mail-ot0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753185AbeBSSB0 (ORCPT ); Mon, 19 Feb 2018 13:01:26 -0500 Received: by mail-ot0-f171.google.com with SMTP id p8so6359254otf.2; Mon, 19 Feb 2018 10:01:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=nXTiDVSGp81He1Cr5hPKmlgofOXvIjQsYYxZ/aDpDCg=; b=BzohhyqunYygTYBF4FFpaqHKJ/G0LtcDkhcbRfX/PGZgfRwDayVrG7JQV/TJLuHcHd OCj1FSuU4UUqeRyQISEUn3W3Ji/63zars/5uL2zpJAIGOkl+coHcsq5MzL3R8ACJxkFj XshjYwuji5hy8SBbhVClJBkbf8cUScw5pIpw3sgEBjqUl5V+PIiyYGZdioZNMO9tk0Q1 PtpxB6e7pLZXQ6FSwgYT1we7nRE+hx/BLNZLg3ImpciEzby4buYVoQ9/E2vbC+Kk74uA VKoqewB8C8gIipAol13oYl8gHrhGxLrofsJgiZEw1ot1nlS2x07TDO2vTXQASL/A4A// u3gQ== X-Gm-Message-State: APf1xPBNASa2j7xD8feLr9yjeBF6kccM6zpPrYg8Yo2Djhdd/rZnsaQL OLK8qgA4a7lq59jtRpCgtg== X-Received: by 10.157.27.140 with SMTP id z12mr10846047otd.357.1519063285811; Mon, 19 Feb 2018 10:01:25 -0800 (PST) Received: from localhost (216-188-254-6.dyn.grandenetworks.net. [216.188.254.6]) by smtp.gmail.com with ESMTPSA id l4sm6160621otf.81.2018.02.19.10.01.25 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 19 Feb 2018 10:01:25 -0800 (PST) Date: Mon, 19 Feb 2018 12:01:24 -0600 From: Rob Herring To: Viresh Kumar Cc: Rafael Wysocki , Zhang Rui , Eduardo Valentin , linux-pm@vger.kernel.org, Vincent Guittot , Mark Rutland , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 10/10] dt-bindings: thermal: Remove "cooling-{min|max}-level" properties Message-ID: <20180219180124.22rcnjoyvv3qw3cl@rob-hp-laptop> References: <0ec53640f1a09e6e0d7aa1a21d1a3266c3c209c7.1518166039.git.viresh.kumar@linaro.org> <20180218232906.jkpymin3a4qxjhnc@rob-hp-laptop> <20180219034338.GI28462@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180219034338.GI28462@vireshk-i7> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 19, 2018 at 09:13:38AM +0530, Viresh Kumar wrote: > On 18-02-18, 17:29, Rob Herring wrote: > > On Fri, Feb 09, 2018 at 02:28:10PM +0530, Viresh Kumar wrote: > > > 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. > > > > What about non-CPU devices? A fan for example. > > Even they aren't using these properties. The gpio-fan binding[1] for > example uses the "gpio-fan,speed-map" property instead to find the > number of states it supports. Okay. Reviewed-by: Rob Herring