Lines Matching full:subsystem

50 subsystems.  Once a client subsystem is loaded, it will appear as a
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
132 A subsystem is the top level of a client module.  During initialization,
133 the client module registers the subsystem with configfs, the subsystem
135 subsystem is also a config_group, and can do everything a config_group
162 structure that actually represents what the subsystem is doing.  The
176 Usually a subsystem wants the item to display and/or store attributes,
301 mkdir(2) in the group's directory.  The subsystem allocates a new
306 If the subsystem wants the child to be a group itself, the subsystem
313 The subsystem must config_item_put() the reference that was initialized
314 upon item allocation.  If a subsystem has no work to do, it may omit
316 config_item_put() on the item on behalf of the subsystem.
321    (assuming that it has no children to keep it busy).  The subsystem is
322    responsible for responding to this.  If the subsystem has references to
324    for the item to actually disappear from the subsystem's usage.  But it
330 teardown happens, the subsystem can implement the
345 A subsystem must register itself, usually at module_init time.  This
346 tells configfs to make the subsystem appear in the file tree::
356 A subsystem consists of a toplevel config_group and a mutex.
357 The group is where child config_items are created.  For a subsystem,
359 configfs_register_subsystem(), the subsystem must have initialized the
363 When the register call returns, the subsystem is live, and it
365 the subsystem must be ready for it.
371 subsystem/group and the simple_child item in
376 Hierarchy Navigation and the Subsystem Mutex
381 appear in a filesystem.  A subsystem is NEVER to touch the filesystem
382 parts, but the subsystem might be interested in this hierarchy.  For
386 A subsystem can navigate the cg_children list and the ci_parent pointer
387 to see the tree created by the subsystem.  This can race with configfs'
388 management of the hierarchy, so configfs uses the subsystem mutex to
389 protect modifications.  Whenever a subsystem wants to navigate the
390 hierarchy, it must do so under the protection of the subsystem
393 A subsystem will be prevented from acquiring the mutex while a newly
399 a subsystem to trust ci_parent and cg_children while they hold the
420 in its own subsystem).
424 this is a void function and cannot return failure.  The subsystem is
450 A configfs subsystem specifies default groups by adding them using the
455 method call notifies the subsystem the parent group is going away, it
499 after which the subsystem can start whatever entity this item
503 a target device, the subsystem has no idea what block device to import.
504 The simple example assumes that the subsystem merely waits until all the
510 Far better would be an explicit action notifying the subsystem that the
512 the subsystem to provide feedback as to whether the attributes are
528 directory.  At this point, the subsystem receives the ->commit_item()
534 time from the "live" directory back to the "pending" one.  The subsystem