Lines Matching refs:attributes

20 is discovered) and it is registered with sysfs.  Its attributes then
21 appear in sysfs, allowing userspace to read the attributes via
22 readdir(3)/read(2).  It may allow some attributes to be modified via
28 mkdir(2).  It is destroyed via rmdir(2).  The attributes appear at
30 As with sysfs, readdir(3) queries the list of items and/or attributes.
51 An item is created via mkdir(2).  The item's attributes will also
52 appear at this time.  readdir(3) can determine what the attributes are,
54 values.  Like sysfs, attributes should be ASCII text files, preferably
59 once.  When writing to configfs attributes, userspace processes should
105 object in the subsystem.  It has attributes that match values on that
107 and its attributes, allowing the subsystem to ignore all but the
111 collection of items that share the same attributes and operations.
156 Usually a subsystem wants the item to display and/or store attributes,
428 default values can be specified for the item's attributes such that the
429 item can do its work.  Userspace must configure one or more attributes,
436 appropriate attributes are configured, and then connects.  This will,
437 indeed, work, but now every attribute store must check if the attributes
443 the subsystem to provide feedback as to whether the attributes are
457 created in the "pending" directory.  Its attributes can be modified at
460 callback.  If all required attributes are filled to satisfaction, the