Lines Matching full:attributes

22 is discovered) and it is registered with sysfs.  Its attributes then
23 appear in sysfs, allowing userspace to read the attributes via
24 readdir(3)/read(2).  It may allow some attributes to be modified via
30 mkdir(2).  It is destroyed via rmdir(2).  The attributes appear at
32 As with sysfs, readdir(3) queries the list of items and/or attributes.
54 An item is created via mkdir(2).  The item's attributes will also
55 appear at this time.  readdir(3) can determine what the attributes are,
59 There are two types of configfs attributes:
61 * Normal attributes, which similar to sysfs attributes, are small ASCII text
65   normal configfs attributes, userspace processes should first read the entire
69 * Binary attributes, which are somewhat similar to sysfs binary attributes,
72   The write(2) calls from user space are buffered, and the attributes'
122 object in the subsystem.  It has attributes that match values on that
124 and its attributes, allowing the subsystem to ignore all but the
128 collection of items that share the same attributes and operations.
176 Usually a subsystem wants the item to display and/or store attributes,
257 single read/write will occur; the attributes' need not concern itself
497 default values can be specified for the item's attributes such that the
498 item can do its work.  Userspace must configure one or more attributes,
505 appropriate attributes are configured, and then connects.  This will,
506 indeed, work, but now every attribute store must check if the attributes
512 the subsystem to provide feedback as to whether the attributes are
526 created in the "pending" directory.  Its attributes can be modified at
529 callback.  If all required attributes are filled to satisfaction, the