mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
	linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Dmitry Torokhov <dtor@chromium.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Len Brown <len.brown@intel.com>,
	open list <linux-kernel@vger.kernel.org>,
	Nishanth Menon <nm@ti.com>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH V4] PM / OPP: Add debugfs support
Date: Sat, 07 Nov 2015 02:07:42 +0100	[thread overview]
Message-ID: <3137221.AHWQu5xXpc@vostro.rjw.lan> (raw)
In-Reply-To: <6775c5c7c2e87b68f999870bdd70de3f77e8a660.1446715747.git.viresh.kumar@linaro.org>

On Thursday, November 05, 2015 03:02:50 PM Viresh Kumar wrote:
> This patch adds debugfs support to OPP layer to export OPPs and their
> properties for all the devices.
> 
> This creates a top level directory: /sys/kernel/debug/opp and then
> device specific directories (based on device names) inside it. For
> example: 'cpu0', 'cpu1', etc..
> 
> If multiple devices share the OPP table, then the real directory is
> created only for the first device. For all others, links are created to
> the real directory.
> 
> Inside the device specific directory, a separate directory is created
> for each OPP. And within that files per opp property.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> Hi Rafael,
> 
> This was applied to pm/linux-next earlier, but then we dropped it citing
> few merge conflicts with driver-core changes. i.e. debugfs_create_bool()
> and debugfs_create_ulong() changes.
> 
> All that is merged by Linus and so we can get this merged back again,
> once you are comfortable.
> 
> @Stephen: I have dropped your Reviewed by tag as there were minor
> changes here, please give it again :)

So I'll wait for the response from Stephen and then I'll queue up this one
for v4.5.

Thanks,
Rafael


  reply	other threads:[~2015-11-07  0:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05  9:32 Viresh Kumar
2015-11-07  1:07 ` Rafael J. Wysocki [this message]
2015-11-10 19:36 ` Stephen Boyd
2015-11-11  2:29   ` [PATCH V5] " Viresh Kumar
2015-11-11 21:54     ` Stephen Boyd

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=3137221.AHWQu5xXpc@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=b.zolnierkie@samsung.com \
    --cc=dtor@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=len.brown@intel.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=pavel@ucw.cz \
    --cc=sboyd@codeaurora.org \
    --cc=viresh.kumar@linaro.org \
    /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