public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <abelay-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
To: Dominik Brodowski
	<linux-X3ehHDuj6sIIGcDfoQAp7OTW4wlIGRCZ@public.gmane.org>
Cc: linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC] Some thoughts on device drivers and sysfs
Date: Sun, 27 Mar 2005 16:27:24 -0500	[thread overview]
Message-ID: <1111958844.3503.100.camel@localhost.localdomain> (raw)
In-Reply-To: <20050327210853.GA18358-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

On Sun, 2005-03-27 at 23:08 +0200, Dominik Brodowski 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.

You're right, I should have worded this differently.

> 
> Drivers can add (e.g. in ->probe) attributes for devices using
> extern int device_create_file(struct device *device, struct device_attribute
> * entry);
> and delete them (e.g. in ->remove) using
> extern void device_remove_file(struct device * dev, struct device_attribute
> * attr);
> 
> and there's also 
> 
> extern int driver_create_file(struct device_driver *, struct
> driver_attribute *);
> extern void driver_remove_file(struct device_driver *, struct
> driver_attribute *);
> 
> 
> 	Dominik

Yes, I'm aware of these functions but they pollute the bus level
namespace.  I'm interested in reactions to this alternative approach.  I
wanted to explore the possibility of making a device driver instance a
separate component with its own individual state and relationships.

Adam



[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2005-03-27 21:27 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 [this message]
     [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

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=1111958844.3503.100.camel@localhost.localdomain \
    --to=abelay-et1tbqhtxzrqt0dzr+alfa@public.gmane.org \
    --cc=linux-X3ehHDuj6sIIGcDfoQAp7OTW4wlIGRCZ@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