From: Dmitry Torokhov <dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
To: linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Cc: Adam Belay <abelay-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Re: [RFC] Some thoughts on device drivers and sysfs
Date: Tue, 29 Mar 2005 01:33:58 -0500 [thread overview]
Message-ID: <200503290133.59002.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050329050345.GB7937-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
On Tuesday 29 March 2005 00:03, Greg KH wrote:
> On Sun, Mar 27, 2005 at 02:24:59PM -0500, Adam Belay wrote:
> > One of the original design goals of sysfs was to provide a standardized
> > location to keep driver configuration attributes. Although sysfs
> > handles this very well for bus devices and class devices, there isn't
> > currently a method to export attributes for device drivers and their
> > specific bound device instances to userspace.
>
> Hm, what's device_create_file(), device_remove_file(), and DEVICE_ATTR()
> for? A number of drivers use these functions today to add their own
> driver specific attributes to a device they control.
>
> Then, userspace can just do a simple:
> ls /sys/bus/pci/drivers/my_foo_driver/
> to see all devices on the PCI bus that are controlled by that driver.
> Then it can go into those directories and cat out the specific
> information if needed.
It probably would be nice if all driver-specific device attributes would be
grouped under /sys/devices/.../<blah_device>/drvattr/* so their names would
not clash with names of driver core attributes.
Unfortunately that would mean we are breaking userspace again...
--
Dmitry
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2005-03-29 6:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 19:24 [RFC] Some thoughts on device drivers and sysfs Adam Belay
[not found] ` <1111951499.3503.87.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-03-27 20:53 ` Arioch
2005-03-27 21:08 ` Dominik Brodowski
[not found] ` <20050327210853.GA18358-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
2005-03-27 21:27 ` Adam Belay
[not found] ` <1111958844.3503.100.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-03-27 21:43 ` Dominik Brodowski
[not found] ` <20050327214309.GA18745-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
2005-03-27 22:18 ` Adam Belay
2005-03-27 21:25 ` Jon Smirl
2005-03-29 5:03 ` Greg KH
[not found] ` <20050329050345.GB7937-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2005-03-29 6:33 ` Dmitry Torokhov [this message]
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=200503290133.59002.dtor_core@ameritech.net \
--to=dtor_core-ywtbtysyrb+lz21kgmrzwg@public.gmane.org \
--cc=abelay-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.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