Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753594AbbHGFTG (ORCPT ); Fri, 7 Aug 2015 01:19:06 -0400 Received: from mail-pa0-f51.google.com ([209.85.220.51]:35860 "EHLO mail-pa0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752808AbbHGFTC (ORCPT ); Fri, 7 Aug 2015 01:19:02 -0400 Date: Fri, 7 Aug 2015 10:48:26 +0530 From: Viresh Kumar To: Krzysztof Kozlowski Cc: Kukjin Kim , "Rafael J. Wysocki" , Olof Johansson , Arnd Bergmann , "'Bartlomiej Zolnierkiewicz'" , "'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 Message-ID: <20150807051826.GJ6325@linux> References: <1438868514-8814-1-git-send-email-b.zolnierkie@samsung.com> <015301d0d0a3$1396c900$3ac45b00$@kernel.org> <20150807035018.GF6325@linux> <20150807035156.GG6325@linux> <55C43085.8090506@samsung.com> <20150807043037.GH6325@linux> <55C43971.5010504@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55C43971.5010504@samsung.com> 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 Content-Length: 1110 Lines: 32 On 07-08-15, 13:52, Krzysztof Kozlowski wrote: > Thanks for explanation. As fair as I understand, Bartlomiej wanted to > merge this in a way which would avoid loosing the boost mode. Kukjin > prepared topic branches for previous cpu-freq/clk stuff so maybe > everything could go through PM? We aren't loosing anything at all. There can be two cases here: 1. Patch 1/6 and 6/6 make it to 4.3 (with suggested changes) via PM tree: - All will work fine in this case, no issues at all.. 2. They don't make it: - Even in this case, nothing will break. Users can just enable a config option and that's all.. So, no need to divert things into another tree this late. Over that, Rafael will not be around for 2 weeks now (Plumbers and other stuff) .. So, just target the cpufreq core changes via PM tree.. rest is just fine. I hope that makes sense :) -- viresh -- 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/