linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: MyungJoo Ham <myungjoo.ham@gmail.com>
Cc: Len Brown <len.brown@intel.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	linux-pm@lists.linux-foundation.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v5 0/3] DEVFREQ, DVFS Framework for Non-CPU Devices.
Date: Mon, 8 Aug 2011 14:35:20 -0700	[thread overview]
Message-ID: <20110808213520.GA9803@suse.de> (raw)
In-Reply-To: <CAJ0PZbSgVujLSW9Ea_iWHZVbq2_H3EWGJg_1Zh5rUfvG3sxgsw@mail.gmail.com>

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

  reply	other threads:[~2011-08-08 21:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08  9:03 [PATCH v5 0/3] DEVFREQ, DVFS Framework for Non-CPU Devices MyungJoo Ham
2011-08-08  9:03 ` [PATCH v5 1/3] PM: Introduce DEVFREQ: generic DVFS framework with device-specific OPPs MyungJoo Ham
2011-08-11  1:00   ` Turquette, Mike
2011-08-17  9:40     ` MyungJoo Ham
2011-08-08  9:03 ` [PATCH v5 2/3] PM / DEVFREQ: add basic governors MyungJoo Ham
2011-08-11  1:35   ` Turquette, Mike
2011-08-16  8:52     ` MyungJoo Ham
2011-08-16 18:11       ` Turquette, Mike
2011-08-17  7:32         ` MyungJoo Ham
2011-08-08  9:03 ` [PATCH v5 3/3] PM / DEVFREQ: add sysfs interface MyungJoo Ham
2011-08-08  9:53 ` [PATCH v5 0/3] DEVFREQ, DVFS Framework for Non-CPU Devices MyungJoo Ham
2011-08-08 21:35   ` Greg KH [this message]
2011-08-10 21:09 ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110808213520.GA9803@suse.de \
    --to=gregkh@suse.de \
    --cc=kyungmin.park@samsung.com \
    --cc=len.brown@intel.com \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=myungjoo.ham@gmail.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).