Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753016AbbHCKtX (ORCPT ); Mon, 3 Aug 2015 06:49:23 -0400 Received: from mailout1.samsung.com ([203.254.224.24]:38180 "EHLO mailout1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751770AbbHCKtV (ORCPT ); Mon, 3 Aug 2015 06:49:21 -0400 X-AuditID: cbfee61b-f79706d000001b96-63-55bf471107cb From: Bartlomiej Zolnierkiewicz To: Viresh Kumar Cc: Thomas Abraham , Sylwester Nawrocki , Michael Turquette , Kukjin Kim , Kukjin Kim , Krzysztof Kozlowski , Tomasz Figa , Lukasz Majewski , Heiko Stuebner , Chanwoo Choi , Kevin Hilman , Javier Martinez Canillas , Tobias Jakobi , Anand Moon , linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Javier Martinez Canillas , Zhang Rui , Eduardo Valentin Subject: Re: [PATCH v3 3/5] ARM: Exynos: switch to using generic cpufreq driver for Exynos4x12 Date: Mon, 03 Aug 2015 12:47:57 +0200 Message-id: <2295533.OBI6Q4a3b9@amdc1976> User-Agent: KMail/4.13.3 (Linux/3.13.0-57-generic; KDE/4.13.3; x86_64; ; ) In-reply-to: <20150803104044.GB21529@linux> References: <1438368557-2352-1-git-send-email-b.zolnierkie@samsung.com> <4532306.AVvo5hem3c@amdc1976> <20150803104044.GB21529@linux> MIME-version: 1.0 Content-transfer-encoding: 7Bit Content-type: text/plain; charset=us-ascii X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBIsWRmVeSWpSXmKPExsVy+t9jAV1B9/2hBsv79C2uf3nOajH/yjVW i/+PXrNaXPs9g83izds1TBavXxha9C64ymbR//g1s8XXwysYLd483MxosekxUO3HnnusFpd3 zWGz+Nx7hNFixvl9TBbrNt5it7h4ytXiycM+NovDb9pZLTqWMVq0rf7AarFq1x9Gi41fPRzE Pd7faGX3+Du7ldlj56y77B6L97xk8ti0qpPN4861PWwem5fUe/w7xu6xpR8o17dlFaPH9mvz mD0+b5IL4InisklJzcksSy3St0vgylg2oZmtYC5HxaqZx1kaGA+wdTFycEgImEj0fWbqYuQE MsUkLtxbzwZiCwksZZRYd7ugi5ELyP7KKNHRNYkVJMEmYCUxsX0VI0iviICWxMubqSBhZoHn bBK/pieC2MICCRKXD+9mBylhEVCVmLmOHSTMK6Ap0f39BguILSrgJfH9VwMzSAmngLbEly1e EJvaGCUuz13BClEvKPFj8j0WiPHyEvv2T2WFsLUk1u88zjSBUWAWkrJZSMpmISlbwMi8ilEi tSC5oDgpPdcoL7Vcrzgxt7g0L10vOT93EyM4fp9J72A8vMv9EKMAB6MSD++HBftChVgTy4or cw8xSnAwK4nw/vgNFOJNSaysSi3Kjy8qzUktPsQozcGiJM6rb7IpVEggPbEkNTs1tSC1CCbL xMEp1cA4zXWZRF33e08xMe4762bWeFgwHAu906ty3TFP/p7Y84W2fEWe8oGNmr82zPtsLM9u q151TPE5Y9C2j1Leb2dcPDv9iUP7yTrWBWlbjxXLSfisNFX5f8dRu8hxw8Ut5SefvfX/xsjF vHDPiT2M6Toxt+8u2Nwx9dkLzRsenx/96pc1uWe/Rn+LEktxRqKhFnNRcSIA2vIlQNsCAAA= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1271 Lines: 32 On Monday, August 03, 2015 04:10:44 PM Viresh Kumar wrote: > On 03-08-15, 12:36, Bartlomiej Zolnierkiewicz wrote: > > I would really like it to be dependency not an option (+ I think > > that ideally it should be checked at runtime, IOW we should be > > checking from cpufreq-dt driver if the thermal support is enabled > > before enabling boost support). > > I don't think boost has any dependency on thermal support. Yeah, it > may be true for your platform but we can't force it. People might have > different algorithms to control boost modes, thermal is just one > option they may look at. For few, enabling boost may not be a thermal > issue, but power. So, they want to allow it only when they want, but > that wouldn't burn their chip. OK, I see your point (I have not thought about power being the boost limitation previously). > So, a platform can choose how it wants to have it. :) I'll re-do this patch. Thank you. Best regards, -- Bartlomiej Zolnierkiewicz Samsung R&D Institute Poland Samsung Electronics -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/