Received: by 10.223.164.202 with SMTP id h10csp5472539wrb; Tue, 21 Nov 2017 10:13:25 -0800 (PST) X-Google-Smtp-Source: AGs4zMYt2IGjVdWCwzSdtZUCOdaSFYuhSnl2laNFqh2xUxMqd6USBypAUtuLD/6C66KJeFe2wFnL X-Received: by 10.98.156.81 with SMTP id f78mr8118000pfe.211.1511288004952; Tue, 21 Nov 2017 10:13:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1511288004; cv=none; d=google.com; s=arc-20160816; b=R5cA+xIgkTPbpesJeecKx+iZAymLRLv5r/98pmlWXIm5GHm5QfCNubcuKxlty5NKv/ 5OKrRGa3Cp4aCaAdBQ9DLJlgPxkoPrD4JNVEoX8Gvg6USQSzNR0+4O+i+GeH0MzkTlyV XJrrbYXJILEODLR9W+azKCDd7ouMClD7CW/WRLLUd5YoTJnw5W3vhOv2p5WgdH1LHwB/ AM6Y5lyBniE75g3O8BoHGrBiPce1BoHIjFRF7g4mveL7mp9k413/AdEwGmf830pylSRn 4zO4FacqYazJeRyAZKuR5hiAvYoMLZhfR1ObhJ7wull4hqH26TEMU29WAZxYa9Hn4Nnq tTMg== 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:dkim-signature:arc-authentication-results; bh=z7C3aGOf1cJez1jshBOnfGqSIXxEfANiw9awrT+YiLg=; b=mEIvj+oWhpnQVelYbf7NQWSGZwc0IYLFo0zxQMO4CO7YaRc5X4fvBRUrgHZBMlBj9r hXjv6KDI5Eg8872cgKuBBjelKRYM2GLXcOwPvy8yZLVCWGbeVajEJUeBuw0ALjaU3ZOB 6KO9YkHtHERgIzO61ScznthZJJX+63dQAhgY4TbkrB1z/lHQiWxxZWz/oTWWMfWjTbJe OdA53DK0pJUunF7D6wQTit2JReXCGpV1gmOj05fDuEEgFpLlvW6peJ4Lw+f2NjAazaqA D2IVIhoy6n5AuJkdxGini3HZvVRD/fACg7NksLGvYfWQhzKotWYudK/noVKWfZzU0dHn IRCA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=PVAlWxEq; 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=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h2si11149259pgn.284.2017.11.21.10.13.12; Tue, 21 Nov 2017 10:13:24 -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=@gmail.com header.s=20161025 header.b=PVAlWxEq; 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=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751327AbdKUSMb (ORCPT + 76 others); Tue, 21 Nov 2017 13:12:31 -0500 Received: from mail-pf0-f172.google.com ([209.85.192.172]:41329 "EHLO mail-pf0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751145AbdKUSM3 (ORCPT ); Tue, 21 Nov 2017 13:12:29 -0500 Received: by mail-pf0-f172.google.com with SMTP id j28so10388275pfk.8; Tue, 21 Nov 2017 10:12:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=z7C3aGOf1cJez1jshBOnfGqSIXxEfANiw9awrT+YiLg=; b=PVAlWxEqH15+pqKv6vAX2uCwpEGrrpSVOFCjb+FHOmZ3R5E2zysg03fkGQNiSvIk2X nuhY+TSvOKOYk6Ag/o9JrlrcBa5b3Xbw5qaUSOuO6PYaCGbP2AjY9ndpKEeOu5lvYL62 ZjHBlv0E7f8JC7aW+JBk54Dhy8H4LvaqPnmWMbEqsXlm2qEEP9XyKGbDE3SzfF08YKUk qvYAHzApx7Xjq67o0nms1o77H5EcgjTdTEGzCsbGYH8KK4OTbb5CX9ExgpvnffBem5If z8e+R7Veybi64+n0B68nmjfNXI1mBOPLX2STob+maNAvjiTtE29EZEg4EQzyIrReuiER h0fQ== 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=z7C3aGOf1cJez1jshBOnfGqSIXxEfANiw9awrT+YiLg=; b=n+nxdmAc55MLCalR3FPomA5yRSUZpfablI1GFc0fjv49p2MY2vTgUt73VH/Ysfn6kG kOUQLDEqLiqE8904fHhuvrlAOExWAe3t6HvuXqsORwJrfVchuMJe2dmyP7Mu2d7syE29 TuotauLE/Lo9rlhNCGHQ/KSaKRY9rzcAkVFfc+gWN+gx97AmTm/JEF43TgTNbQhIDwKC VLsYGpyjiFgOddiyBwVuRLfU23JOoQfyFVsJlosVGjh4jk/P6qkurTV62I4r+eF3bfR1 KHE9FenV899SkHCRrSAM6+Ock/lpIXvarWAHRTmAqHnDjyOTGzbKUpmZAbey8gvGHkZQ nmnA== X-Gm-Message-State: AJaThX7+7gGIFTKwlrjs50/C6vqy7+378H5klOypQwVy6YOfj1JnGfcp Skn9Q0pzgFrmnujXVKGtnuA= X-Received: by 10.84.244.129 with SMTP id h1mr18399346pll.255.1511287948733; Tue, 21 Nov 2017 10:12:28 -0800 (PST) Received: from localhost.localdomain ([2601:644:8201:32e0:7256:81ff:febd:926d]) by smtp.gmail.com with ESMTPSA id g7sm27121385pfj.13.2017.11.21.10.12.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Nov 2017 10:12:27 -0800 (PST) Date: Tue, 21 Nov 2017 10:12:24 -0800 From: Eduardo Valentin To: Javi Merino Cc: Vincent Guittot , Lukasz Luba , Daniel Lezcano , Ionela Voinescu , Punit Agrawal , "Rafael J. Wysocki" , Viresh Kumar , "Rafael J. Wysocki" , Amit Daniel Kachhap , Zhang Rui , Steven Rostedt , Ingo Molnar , Linux PM , Lukasz Luba , Linux Kernel Mailing List Subject: Re: [PATCH 4/4] cpu_cooling: Drop static-power related stuff Message-ID: <20171121181222.GA4075@localhost.localdomain> References: <20171116152058.GR3257@vireshk-i7> <2810372.fJ2vMN0cWO@aspire.rjw.lan> <20171116234422.GA6141@localhost.localdomain> <878tf5tbfj.fsf@e105922-lin.cambridge.arm.com> <35d3751d-f28d-38c2-02b2-c9980f11c52e@arm.com> <5A144CB3.50806@gmail.com> <20171121165703.GA2499@localhost.localdomain> <20171121180006.GA26638@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171121180006.GA26638@localhost> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 21, 2017 at 06:00:07PM +0000, Javi Merino wrote: > Hi, > > On Tue, Nov 21, 2017 at 08:57:06AM -0800, Eduardo Valentin wrote: > > [snip] > > > As I said before, the minimal you guys (ARM and Linaro) can do is to at > > least upstream the Juno code! as a reference. Come on guys? what is > > preventing you to upstream Juno model? > > As Ionela pointed out earlier in the thread, the cpufreq driver for Juno > was not acceptable for mainline because it used platform specific code. > When it was converted to cpufreq-dt, the static power was left behind > because it can't be represented in device tree. This is because there Or we still haven't figure what to represent. Once decided what to represent, then we can claim if is doable in DT or not. > isn't a function that works for every SoC, different process nodes > (among other things) will need different functions. So it can't be just > a bunch of coefficients in DT, we need a function. Hence the callback. Well, DT is full of vendor specific stuff. > > In a nutshell, mainline does not want platform specific code, but we > haven't figured out how to calculate static power without platform > specific code. To, that is still fine to have it as a callback, as long as you have at least one user! I still do not understand why Juno static power cannot go as platform code that register the callback to implement the static power model. > > Cheers, > Javi From 1584699928521948192@xxx Tue Nov 21 18:07:01 +0000 2017 X-GM-THRID: 1584123420538137355 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread