From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: [PATCH v5 0/3] DEVFREQ, DVFS Framework for Non-CPU Devices. Date: Mon, 8 Aug 2011 14:35:20 -0700 Message-ID: <20110808213520.GA9803@suse.de> References: <1312794188-9823-1-git-send-email-myungjoo.ham@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: MyungJoo Ham Cc: Len Brown , Kyungmin Park , linux-pm@lists.linux-foundation.org, Thomas Gleixner List-Id: linux-pm@vger.kernel.org On Mon, Aug 08, 2011 at 06:53:31PM +0900, MyungJoo Ham wrote: > Hello all, > > > I've got one issue requesting some comments: whether to create devfreq > directory or not. > > For now, we only have four basic governors and one not-yet-posted > devfreq user for DEVFREQ; thus, it seems not necessary for just now. > > However, like CPUFREQ, DEVFREQ may have several users later and we may > want to gather these files to one location: /drivers/devfreq or > somewhere else in /drivers/*. For example, Exynos4210 Memory DEVFREQ > user is located at arch/arm/mach-exynos4/devfreq_bus.c and with a > separated directory, we may have it at > drivers/devfreq/exynos4_memory_bus.c. > > How do you think about separating DEVFREQ directory? Should I do so or > wait until we have several DEVFREQ users? A new subdir is fine, it's not an issue, and seems to make sense here, as you point out. greg k-h