Skip to contentSkip to conversation

sysfs - which driver for a device?

DISCUSSION Jon Smirl 3 participants 3 messages Sep 24, 2003 – Sep 25, 2003 Driver core

lore
Share & tools
lore

Jon Smirl

author
#0 lore raw

In sysfs it is easy to see which devices a driver is supporting. For example /sys/bus/pci/drivers/e1000 links to 0000:02:0c.0 in my system.

But how do you go the other way; starting from 0000:02:0c.0 to determine the driver? Is the best solution to loop though the drivers directories searching for the device? Or would it be better to change sysfs to add an attribute to each device containing the driver name?

In /proc/bus/pci/devices the driver name is the last field.

=====
Jon Smirl
[email protected]

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

#1 lore raw

Hi,

Quoted 9 lines · Jon Smirl

In sysfs it is easy to see which devices a driver is supporting. For example /sys/bus/pci/drivers/e1000 links to 0000:02:0c.0 in my system.

But how do you go the other way; starting from 0000:02:0c.0 to determine the driver? Is the best solution to loop though the drivers directories searching for the device? Or would it be better to change sysfs to add an attribute to each device containing the driver name?

In /proc/bus/pci/devices the driver name is the last field.

Have you looked at libsysfs? You can query for a sysfs_device, which includes the name of the driver. Libsysfs' goal is to provide an easy interface for retrieving such information. The library should also reduce the need for adding extra references or attributes in the kernel.

Libsysfs is included in the sysfsutils package that also contains systool, a command to view system information exposed through sysfs.

Sysfsutils can be found at:

http://linux-diag.sourceforge.net/

Thanks,

Dan

Quoted 13 lines

=====
Jon Smirl
[email protected]

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#2 lore raw
In reply to Jon Smirl
Quoted 8 lines

In sysfs it is easy to see which devices a driver is supporting. For example /sys/bus/pci/drivers/e1000 links to 0000:02:0c.0 in my system.

But how do you go the other way; starting from 0000:02:0c.0 to determine the driver? Is the best solution to loop though the drivers directories searching for the device? Or would it be better to change sysfs to add an attribute to each device containing the driver name?

Well, one could use a script to ascertain the driver name for a given device. Or, you could use the patch below, which will insert a 'driver' symlink that points to the device driver's directory.

Pat

===== drivers/base/bus.c 1.51 vs edited =====

drivers/base/bus.c +2 -0
@@ -243,6 +243,7 @@
 	list_add_tail(&dev->driver_list,&dev->driver->devices);
 	sysfs_create_link(&dev->driver->kobj,&dev->kobj,
 			  kobject_name(&dev->kobj));
+	sysfs_create_link(&dev->kobj,&dev->driver->kobj,"driver");
 }
 
 
@@ -365,6 +366,7 @@
 	struct device_driver * drv = dev->driver;
 	if (drv) {
 		sysfs_remove_link(&drv->kobj,kobject_name(&dev->kobj));
+		sysfs_remove_link(&dev->kobj,"driver");
 		list_del_init(&dev->driver_list);
 		device_detach_shutdown(dev);
 		if (drv->remove)