From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752866AbbG0Kfd (ORCPT ); Mon, 27 Jul 2015 06:35:33 -0400 Received: from mail-pa0-f47.google.com ([209.85.220.47]:35487 "EHLO mail-pa0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752461AbbG0Kf2 (ORCPT ); Mon, 27 Jul 2015 06:35:28 -0400 Date: Mon, 27 Jul 2015 16:05:21 +0530 From: Viresh Kumar To: Bartlomiej Zolnierkiewicz 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 Subject: Re: [PATCH v2 2/7] cpufreq: opp: fix handling of turbo modes Message-ID: <20150727103521.GA4103@linux> References: <1436456621-29839-1-git-send-email-b.zolnierkie@samsung.com> <1436456621-29839-3-git-send-email-b.zolnierkie@samsung.com> <20150727083531.GC31611@linux> <1595601.YD6UTxy5Qg@amdc1976> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1595601.YD6UTxy5Qg@amdc1976> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 27-07-15, 12:24, Bartlomiej Zolnierkiewicz wrote: > Have you read my explanation of the issue? > > With your OPP-v2 patches cpufreq-dt picks turbo frequencies and uses > them as normal ones. > > (More at: http://www.spinics.net/lists/arm-kernel/msg430397.html) Yes I did. I understand that the turbo frequencies are not considered as such by OPP/cpufreq core and it requires your changes to get it working. But its not an issue or bug we are fixing, the problem is that the code for opp-v2 isn't complete yet and your patches is putting things in place. So, we are still doing the bring up here and not fixing a bug really. -- viresh