From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: Nishanth Menon <nm@ti.com>, Len Brown <len.brown@intel.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
Greg KH <gregkh@suse.de>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-pm@lists.linux-foundation.org
Subject: Re: [RFC PATCH] PM: Introduce generic DVFS framework with device-specific OPPs
Date: Wed, 27 Apr 2011 15:49:28 +0200 [thread overview]
Message-ID: <201104271549.28802.rjw@sisk.pl> (raw)
In-Reply-To: <BANLkTik=zr7cHCFnAyyDmDLcrUjhYpuGtA@mail.gmail.com>
On Wednesday, April 27, 2011, MyungJoo Ham wrote:
> On Wed, Apr 27, 2011 at 5:54 AM, Greg KH <gregkh@suse.de> wrote:
> > On Tue, Apr 26, 2011 at 10:45:18PM +0800, Jiejing.Zhang wrote:
> >> Hi Greg,
> >>
> >> I think DVFS here means “Dynamic voltage and frequency scaling”, refering the
> >> first google's result:
> >
> > Ok, if so, please spell it out.
>
> Yes, will do so.
>
> >
> > Also, don't use 'dvfs' as a prefix in the kernel, too many other people
> > will think it is a filesystem. How about "dynvolt"?
> >
> > Or anything else, just no 'fs' in the name otherwise confusion will
> > reign.
>
> Um... ok... I'll avoid using fs as postfix and think about the name again.
> "oppfreq", "devfreq", "dvfscale", "oppscale", "devscale", "ddp
> (dynamic device power)", or "dfvs" (switched frequency and voltage to
> avoid confusion with file systems).
I think devfreq is the best one of the above. At least it will make everyone
think that the feature is analogous to cpufreq, which is correct.
Thanks,
Rafael
_______________________________________________
linux-pm mailing list
linux-pm@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/linux-pm
next prev parent reply other threads:[~2011-04-27 13:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 8:43 [RFC PATCH] PM: Introduce generic DVFS framework with device-specific OPPs MyungJoo Ham
2011-04-26 11:09 ` Rafael J. Wysocki
2011-04-27 5:22 ` MyungJoo Ham
2011-04-27 13:46 ` Rafael J. Wysocki
2011-04-28 6:54 ` MyungJoo Ham
2011-04-28 19:19 ` Rafael J. Wysocki
2011-04-27 17:49 ` Colin Cross
2011-04-27 18:07 ` Menon, Nishanth
[not found] ` <BANLkTin4rrniJpOheLH=JE0jq7vFpdDbrA@mail.gmail.com>
2011-04-27 18:29 ` Colin Cross
[not found] ` <BANLkTi=WWASxk3Fz83324k40Lbq+ccAPeA@mail.gmail.com>
2011-04-27 18:37 ` Colin Cross
2011-04-27 18:48 ` Menon, Nishanth
[not found] ` <BANLkTikEtTDp3Cpj0D5z34wA0_G_DWwKFg@mail.gmail.com>
2011-04-27 18:54 ` Colin Cross
2011-04-27 19:26 ` Thomas Gleixner
[not found] ` <alpine.LFD.2.02.1104272104390.3323@ionos>
2011-04-27 20:48 ` Colin Cross
[not found] ` <BANLkTinWD0ktYKzR_jnQSE76AuW+Z1PSLw@mail.gmail.com>
2011-04-28 6:12 ` MyungJoo Ham
[not found] ` <BANLkTi=Be3DrAUoPmgHpjhAVmN-Pi5Au7g@mail.gmail.com>
2011-04-28 6:44 ` Colin Cross
[not found] ` <BANLkTiniJUgTTDh7SF8yNMeSMa+JYM21wA@mail.gmail.com>
2011-04-28 6:50 ` MyungJoo Ham
[not found] ` <BANLkTimzWyvcBV2ymxaMf=HmRhGYBboB1w@mail.gmail.com>
2011-04-28 7:06 ` Colin Cross
[not found] ` <BANLkTik6L8HkJ0YjQYjh_3eEmbffyk1kRA@mail.gmail.com>
2011-04-28 7:34 ` MyungJoo Ham
2011-04-28 12:19 ` Mark Brown
[not found] ` <BANLkTinP0_qpF3sp8CzDy42i24wqqo7ohw@mail.gmail.com>
2011-04-28 5:59 ` MyungJoo Ham
[not found] ` <BANLkTin-OMyrz=McN6X4TAZrvv3ehVBGew@mail.gmail.com>
2011-04-28 6:43 ` Colin Cross
[not found] ` <BANLkTikVHs1n8fXEAZh6Q4io39eD9PG14w@mail.gmail.com>
2011-04-28 7:16 ` MyungJoo Ham
2011-04-27 19:00 ` Thomas Gleixner
2011-04-27 18:34 ` Mark Brown
2011-04-27 18:45 ` Colin Cross
2011-04-27 18:58 ` Mark Brown
2011-04-26 13:22 ` Greg KH
2011-04-26 14:45 ` Jiejing.Zhang
2011-04-26 20:54 ` Greg KH
2011-04-27 5:33 ` MyungJoo Ham
2011-04-27 13:49 ` Rafael J. Wysocki [this message]
2011-04-27 13:36 ` Mark Brown
2011-04-26 19:45 ` Pavel Machek
2011-04-26 15:07 ` Mark Brown
2011-04-27 5:24 ` MyungJoo Ham
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=201104271549.28802.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=gregkh@suse.de \
--cc=khilman@deeprootsystems.com \
--cc=kyungmin.park@samsung.com \
--cc=len.brown@intel.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
/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