[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1302181644260.6790-100000@netrider.rowland.org>
Date: Mon, 18 Feb 2013 16:48:06 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Felipe Balbi <balbi@...com>
cc: Greg KH <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...hat.com>, <JBottomley@...allels.com>,
<linux-scsi@...r.kernel.org>, <davem@...emloft.net>,
<netdev@...r.kernel.org>,
Doug Thompson <dougthompson@...ssion.com>,
<linux-edac@...r.kernel.org>, <rjw@...k.pl>,
<linux-pm@...r.kernel.org>
Subject: Re: SYSFS "errors"
On Mon, 18 Feb 2013, Felipe Balbi wrote:
> Hi, On Mon, Feb 18, 2013 at 09:49:16AM -0800, Greg KH wrote:
> > > Input/output error - /sys/devices/cpu/power/autosuspend_delay_ms
> >
> > The issue with this file is, if the power.use_autosuspend flag is not
> > set for the device, then it can't be read or written to. This flag
> > changes dynamically with the system state
> > (__pm_runtime_use_autosuspend() can change it), so we can't just not
> > show the file if the flag is not set properly, sorry.
> >
> > So the "error" is correct here, as is the 0644 file value.
>
> hmm... we could create the file at pm_runtime_enable() time and remove
> it on pm_runtime_disable() time, no ? Addin Rafael to Cc
In theory this could be done, although the times would be when runtime
autosuspend is turned on or off, not when pm_runtime_enable is called.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists