From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: myungjoo.ham@gmail.com
Cc: Greg KH <gregkh@suse.de>,
linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, Mark Brown <broonie@sirena.org.uk>,
Jiejing Zhang <kzjeef@gmail.com>, Pavel Machek <pavel@ucw.cz>,
Colin Cross <ccross@google.com>, Nishanth Menon <nm@ti.com>,
Thomas Gleixner <tglx@linutronix.de>,
Len Brown <len.brown@intel.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH v2 3/3] PM / DEVFREQ: add sysfs interface (including user tickling)
Date: Wed, 18 May 2011 00:41:57 +0200 [thread overview]
Message-ID: <201105180041.57723.rjw@sisk.pl> (raw)
In-Reply-To: <BANLkTik__9G-DuSsT_kAc69d+5g8xcVyFg@mail.gmail.com>
On Tuesday, May 17, 2011, MyungJoo Ham wrote:
> On Thu, May 12, 2011 at 7:55 AM, Greg KH <gregkh@suse.de> wrote:
> > On Wed, May 11, 2011 at 04:58:43PM +0900, MyungJoo Ham wrote:
> >> 1. System-wide sysfs interface
> >> - tickle_all R: number of tickle_all execution
> >> W: tickle all devfreq devices
> >> - min_interval R: devfreq monitoring base interval in ms
> >> - monitoring R: shows whether devfreq monitoring is active or
> >> not.
> >>
> >> 2. Device specific sysfs interface
> >> - tickle R: number of tickle execution for the device
> >> W: tickle the device
> >
> > Any sysfs file change/addition/removal needs to have a
> > Documentation/ABI/ entry as well. Please add that to this patch instead
> > of burying it in the changelog entry, where no one will be able to find
> > it in the future.
> >
> > thanks,
> >
> > greg k-h
> >
>
> Sure, I'll add Documentation/ABI/testing/* entries.
>
> However, would it be appropriate for "1. System-wide sysfs interface"
> to be in "sysfs-class-power" and for "2. Device specific sysfs
> interface" to be in "sysfs-devices-devfreq"?
>
> System-wide sysfs interface is in /sys/class/power/devfreq/* and
Hmm. Why not to use /sys/power/ that's already there?
> Device specific sysfs interface is in /sys/...DEVICE.../devfreq/* .
Thanks,
Rafael
next prev parent reply other threads:[~2011-05-17 22:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 7:58 [PATCH v2 1/3] PM: Introduce DEVFREQ: generic DVFS framework with device-specific OPPs MyungJoo Ham
2011-05-11 7:58 ` [PATCH v2 2/3] PM / DEVFREQ: add example governors MyungJoo Ham
2011-05-17 22:39 ` Rafael J. Wysocki
2011-05-18 0:48 ` MyungJoo Ham
2011-05-18 19:46 ` Rafael J. Wysocki
2011-05-27 4:42 ` MyungJoo Ham
2011-05-11 7:58 ` [PATCH v2 3/3] PM / DEVFREQ: add sysfs interface (including user tickling) MyungJoo Ham
2011-05-11 22:55 ` Greg KH
2011-05-17 5:04 ` MyungJoo Ham
2011-05-17 18:32 ` Greg KH
2011-05-17 22:41 ` Rafael J. Wysocki [this message]
2011-05-18 0:43 ` MyungJoo Ham
2011-05-17 22:36 ` [PATCH v2 1/3] PM: Introduce DEVFREQ: generic DVFS framework with device-specific OPPs Rafael J. Wysocki
2011-05-18 8:22 ` MyungJoo Ham
2011-05-18 20:02 ` Rafael J. Wysocki
2011-05-18 20:21 ` Pavel Machek
2011-05-18 20:29 ` Rafael J. Wysocki
2011-05-20 5:36 ` 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=201105180041.57723.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=broonie@sirena.org.uk \
--cc=ccross@google.com \
--cc=gregkh@suse.de \
--cc=kyungmin.park@samsung.com \
--cc=kzjeef@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=myungjoo.ham@gmail.com \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--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
Powered by JetHome