From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751286Ab3KREHz (ORCPT ); Sun, 17 Nov 2013 23:07:55 -0500 Received: from mail-oa0-f41.google.com ([209.85.219.41]:38877 "EHLO mail-oa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751141Ab3KREHu convert rfc822-to-8bit (ORCPT ); Sun, 17 Nov 2013 23:07:50 -0500 MIME-Version: 1.0 In-Reply-To: References: <1384515691-26299-1-git-send-email-sachin.kamat@linaro.org> Date: Mon, 18 Nov 2013 09:37:49 +0530 Message-ID: Subject: Re: [RFC v2 0/4] Add basic support for ASV From: Sachin Kamat To: MyungJoo Ham Cc: "Rafael J. Wysocki" , Linux PM list , Kukjin Kim , Tomasz Figa , linux-arm-kernel , Yadwinder Singh Brar , linux-samsung-soc , LKML Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi MyungJoo, On 18 November 2013 08:07, MyungJoo Ham wrote: > > 2013. 11. 15. 오후 8:44에 "Sachin Kamat" 님이 작성: > > >> >> Original cover letter from Yadwinder: >> This series is to add basic common infrastructure for ASV. >> Basically ASV is a technique used on samsung SoCs, which provides the >> recommended supply voltage for dvfs of arm, mif etc. For a given operating >> frequency, the voltage is recommended based on SoC's ASV group. >> ASV group gets fussed on SoCs during process of mass production. >> >> This series includes: >> - basic common infrastructue for ASV. It provides common APIs for user >> drivers >> like cpufreq & devfreq and and an interface for SoC specific drivers to >> register ASV members(instances) >> - a common platform driver to register ASV members for exynos SoCs >> - an example providing minimal support (only for ARM ASV) for exynos5250 >> chips >> >> Its just basic skelton which I wanted to get it reviewed or discussed in >> early stage, before going ahead on further development based on it. >> Presently example is based on static ASV table provided in SoC specific >> file, >> which I expects to go into DT. But exactly how and where needs to be >> discussed, >> may be in next revisions once we get through the basic skelton. >> Also the location of driver in kernel may also seem odd to someone and >> many more things :). >> >> Looking for your valuable reviews and suggestions. > > Hi, > > As I have commented on the previous thread of Yadwinder, please share the > directory woth AVS, which is conceptually a superset of ASV. > > Ultimately, it would be best if you can supply an infra that can be shared > with the current AVS, which does not have any currently. > Yadwinder has already replied to your suggestion about his concerns. Please share your comments. -- With warm regards, Sachin