From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752235AbbHDBcN (ORCPT ); Mon, 3 Aug 2015 21:32:13 -0400 Received: from mailout2.w1.samsung.com ([210.118.77.12]:39760 "EHLO mailout2.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751791AbbHDBcK (ORCPT ); Mon, 3 Aug 2015 21:32:10 -0400 X-AuditID: cbfec7f5-f794b6d000001495-1e-55c01617ba50 Message-id: <55C0160F.6080301@samsung.com> Date: Tue, 04 Aug 2015 10:31:59 +0900 From: Krzysztof Kozlowski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-version: 1.0 To: Kukjin Kim , Bartlomiej Zolnierkiewicz Cc: Viresh Kumar , Thomas Abraham , Sylwester Nawrocki , Michael Turquette , Kukjin Kim , 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> <55BA36A7.3050107@kernel.org> In-reply-to: <55BA36A7.3050107@kernel.org> Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCIsWRmVeSWpSXmKPExsVy+t/xK7riYgdCDVbO4LTYOGM9q8X1L89Z Lf4/es1qce33DDaL1y8MLXoXXGWz6H/8mtni6+EVjBZvHm5mtNj0+Bqrxceee6wWl3fNYbP4 3HuE0WLG+X1MFus23mK3uHjK1eLwm3ZWi45ljBZtqz+wWqza9YfRYuNXDwdRj/c3Wtk9/s5u ZfbYOesuu8emVZ1sHneu7WHz2Lyk3uPfMXaPvi2rGD22X5vH7PF5k1wAVxSXTUpqTmZZapG+ XQJXRsOnc4wFqzkrXv1Zw97AuI69i5GTQ0LARGJhRxcbhC0mceHeeiCbi0NIYCmjxIa3nawQ zhdGicM9i5m7GDk4eAW0JNb0gjWzCKhKrGxaANbMJmAssXn5EjBbVCBCYvnqk4wgNq+AoMSP yfdYQGwRgUiJ32cngS1gFtjPKtE1fxMrSEJYwFVi1Yu9LBDLjjJKzNp2mBkkwQm07MTxU6wg i5kF9CTuX9QCCTMLyEtsXvOWeQKjwCwkO2YhVM1CUrWAkXkVo2hqaXJBcVJ6rpFecWJucWle ul5yfu4mRkhcft3BuPSY1SFGAQ5GJR5egZf7Q4VYE8uKK3MPMUpwMCuJ8C68ARTiTUmsrEot yo8vKs1JLT7EKM3BoiTOO3PX+xAhgfTEktTs1NSC1CKYLBMHp1QDY8StinPvWRIUfU4EHGP9 Ghl5kGvF8ccGJUlOflNrC+3uZM4U/ZH2vHrmjNlnP8/ceGjruS7LaRH7T2snzjkf8fFA3ruX mUd3PXCcyfRAWEfUKfParvtSy3V/2vyVqPe4cquzccN6r5X2U6dMryzMs0hpa8h6/7ozNyfo 3OKrn7/on+Td7hfgu1OJpTgj0VCLuag4EQA1tmIixwIAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 30.07.2015 23:37, Kukjin Kim wrote: > 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... Dear Kukjin, We are already at 4.2-rc5 and you did not send the pull request before the weekend as you said. It is really late and there is no special reason for delaying the request. What happened? Best regards, Krzysztof