From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754160AbbG3Ohg (ORCPT ); Thu, 30 Jul 2015 10:37:36 -0400 Received: from mail.kernel.org ([198.145.29.136]:60557 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752901AbbG3Ohe (ORCPT ); Thu, 30 Jul 2015 10:37:34 -0400 Message-ID: <55BA36A7.3050107@kernel.org> Date: Thu, 30 Jul 2015 23:37:27 +0900 From: Kukjin Kim User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Lightning/1.0b3pre Thunderbird/3.1.16 MIME-Version: 1.0 To: Bartlomiej Zolnierkiewicz CC: Viresh Kumar , 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 Subject: Re: [PATCH v2 2/7] cpufreq: opp: fix handling of turbo modes References: <1436456621-29839-1-git-send-email-b.zolnierkie@samsung.com> <3141301.RS9TLygaba@amdc1976> <20150727113641.GB10181@linux> <2681271.3UazeZ9PAQ@amdc1976> In-Reply-To: <2681271.3UazeZ9PAQ@amdc1976> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/27/15 20:47, Bartlomiej Zolnierkiewicz wrote: > On Monday, July 27, 2015 05:06:41 PM Viresh Kumar wrote: >> On 27-07-15, 13:14, Bartlomiej Zolnierkiewicz wrote: >>> Sorry but you don't seem to understand the issue. >> >> :) >> >> No, I did. I understand that if someone uses opp bindings today with >> some entries as turbo OPPs, cpufreq will use them as normal >> frequencies. And that may harm the board. >> >> BUT, opp-v2 code isn't ready to be used yet. And platforms should see >> what all is implemented before trying to use them. > > OK. > >> All I was saying is, this isn't a FIX as we haven't introduced the >> feature yet. Otherwise I had no issues with the patch. > > I will update the description for the next patchset revision. > Hi Bart, When will you re-post v3? Because I have a plan to send a pull-request to arm-soc until this weekend... - Kukjin