Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752986AbbHGLsf (ORCPT ); Fri, 7 Aug 2015 07:48:35 -0400 Received: from mailout1.samsung.com ([203.254.224.24]:53994 "EHLO mailout1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752136AbbHGLsb (ORCPT ); Fri, 7 Aug 2015 07:48:31 -0400 X-AuditID: cbfee61a-f79a06d000005c6f-cf-55c49b0cd354 From: Bartlomiej Zolnierkiewicz To: Viresh Kumar Cc: Krzysztof Kozlowski , Kukjin Kim , "Rafael J. Wysocki" , Olof Johansson , Arnd Bergmann , "'Thomas Abraham'" , "'Sylwester Nawrocki'" , "'Michael Turquette'" , "'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 v4 0/6] cpufreq: use generic cpufreq drivers for Exynos4x12 platform Date: Fri, 07 Aug 2015 13:47:26 +0200 Message-id: <2359635.Hxe4cb8zKm@amdc1976> User-Agent: KMail/4.13.3 (Linux/3.13.0-57-generic; KDE/4.13.3; x86_64; ; ) In-reply-to: <20150807113950.GG6939@linux> References: <1438868514-8814-1-git-send-email-b.zolnierkie@samsung.com> <2061119.GBaoSb4YSL@amdc1976> <20150807113950.GG6939@linux> MIME-version: 1.0 Content-transfer-encoding: 7Bit Content-type: text/plain; charset=us-ascii X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOIsWRmVeSWpSXmKPExsVy+t9jQV2e2UdCDS78MLRY2eNtcf3Lc1aL /49es1pc+z2DzeL1C0OL/sevmS2+Hl7BaPHm4WZGi02Pr7FafOy5x2pxedccNovPvUcYLWac 38dksW7jLXaLi6dcLU5d/8xmceb0JVaLw2/aWS06ljFatK3+wGqxatcfRouNXz0cxDze32hl 9/g7u5XZY+esu+wem1Z1snncubaHzWPzknqPKyeaWD3+HWP32HK1ncWjb8sqRo/t1+Yxe3ze JBfAE8Vlk5Kak1mWWqRvl8CVsf3IIaaC3dwV/dN3sjYwtnJ2MXJySAiYSMzunMMOYYtJXLi3 nq2LkYtDSGAWo8T/3ftZIJyvjBJ7r/1jBKliE7CSmNi+Csjm4BAR0JJ4eTMVpIZZ4CKbxJEr c8FqhAWiJA7d3gpmswioSlxcuRlsA6+ApsTLb7OYQGxRAS+J778amEFsTqA523duY4dY1soo MfnZNEaIBkGJH5PvsYDYzALyEvv2T2WFsLUk1u88zjSBEehOhLJZSMpmISlbwMi8ilEitSC5 oDgpPdcwL7Vcrzgxt7g0L10vOT93EyM4ep9J7WA8uMv9EKMAB6MSD2/iv8OhQqyJZcWVuYcY JTiYlUR4G6ceCRXiTUmsrEotyo8vKs1JLT7EKM3BoiTOK7thc6iQQHpiSWp2ampBahFMlomD U6qB0eTHU48nIQ6u8mzL9fnYVn81NvP8pV40xXtdesTTNM6Zzxuzb55h/vWHIVbta/afQxaa z79G/Al3rLyx+oo8g5tsR/fURrZ768L7qo8Jz5ph7sGhtF7ta9vivUubZU95xyYqLmhSmTmz 6XPhrpnJV5Pmuy99nLJQS9M47JxbQvHhgy/4E/bOVWIpzkg01GIuKk4EALlFJe7aAgAA Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1675 Lines: 42 On Friday, August 07, 2015 05:09:50 PM Viresh Kumar wrote: > On 07-08-15, 13:31, Bartlomiej Zolnierkiewicz wrote: > > Users don't need to enable the config option to get boost > > functionality working. It is only needed to get scaling_boost_freqs > > sysfs attribute visible (which lists available boost freqs) when > > using cpufreq-dt driver. Also the config option in question is not > > user visible. > > By users I meant the people who will prepare the build images for the > release. They can just enable the config option :) OK. > > The worst thing that happens if these 2 PM patches don't make it > > in time is that there will be no scaling_boost_freqs available > > when using cpufreq-dt driver. Which is not very important from > > Exynos4x12 POV as it only supports single boost freq currently. > > Right. So, now that your patch is Acked, send 1/6 and 6/6 separately > to pm-list and Rafael can get them merged himself.. > > I hope, your 6/6 patch will change a bit now ? Hmm, wait. Patch 6/6 depends on earlier changes. I cannot remove the config option in question now as it is currently used by exynos-cpufreq specific boost support. Patch 1/6 can be applied now but 6/6 needs to wait for patches 2-5 to be applied first. Actually 6/6 is trivial and can be applied later in v4.3 cycle or even in v4.4 one. 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/