currently writing an extensive tutorial on kobjects and ksets and
sysfs and stuff like that, and was reading the content under
Doc/driver-model/, and read this in class.txt:
Device classes are registered and unregistered with the core using:
int devclass_register(struct device_class * cls);
void devclass_unregister(struct device_class * cls);
and a lot of other stuff related to this "devclass" thingy, but i see
little in the kernel source related to that. references to that go
all the way back to the original git check-in of the source.
there's more "devclass" stuff in binding.txt:
"Upon the successful completion of probe, the device is registered
with the class to which it belongs. Device drivers belong to one and
only one class, and that is set in the driver's devclass field.
devclass_add_device is called to enumerate the device within the class
and actually register it with the class, which happens with the
class's register_dev callback."
so it's pretty clear that there is no actual "devclass" stuff:
$ grep -rw devclass_attribute *
Documentation/driver-model/class.txt:struct devclass_attribute {
Documentation/driver-model/class.txt:static devclass_attribute devclass_attr_debug;
Documentation/driver-model/class.txt:int devclass_create_file(struct device_class *, struct devclass_attribute *);
Documentation/driver-model/class.txt:void devclass_remove_file(struct device_class *, struct devclass_attribute *);
$
can all those references be removed/updated?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
