Subject: Re: [RFC] Some thoughts on device drivers and sysfs
From: Adam Belay <abelay@novell.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Greg KH <greg@kroah.com>, Patrick Mochel <mochel@digitalimplant.org>,
       linux-kernel@vger.kernel.org, linux-pm@lists.osdl.org
In-Reply-To: <20050327210853.GA18358@isilmar.linta.de>
References: <1111951499.3503.87.camel@localhost.localdomain>
	 <20050327210853.GA18358@isilmar.linta.de>
Content-Type: text/plain
Date: Sun, 27 Mar 2005 16:27:24 -0500
Message-Id: <1111958844.3503.100.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1557
Lines: 41

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/