Lines Matching refs:subsystem

47 subsystems.  Once a client subsystem is loaded, it will appear as a
117 object in the subsystem.  It has attributes that match values on that
119 and its attributes, allowing the subsystem to ignore all but the
127 A subsystem is the top level of a client module.  During initialization,
128 the client module registers the subsystem with configfs, the subsystem
130 subsystem is also a config_group, and can do everything a config_group
154 structure that actually represents what the subsystem is doing.  The
168 Usually a subsystem wants the item to display and/or store attributes,
282 …vided, this method is called from mkdir(2) in the group's directory.  The subsystem allocates a new
287 If the subsystem wants the child to be a group itself, the subsystem
294 The subsystem must config_item_put() the reference that was initialized
295 upon item allocation.  If a subsystem has no work to do, it may omit
297 config_item_put() on the item on behalf of the subsystem.
301 (assuming that it has no children to keep it busy).  The subsystem is
302 responsible for responding to this.  If the subsystem has references to
304 for the item to actually disappear from the subsystem's usage.  But it
310 teardown happens, the subsystem can implement the
324 A subsystem must register itself, usually at module_init time.  This
325 tells configfs to make the subsystem appear in the file tree.
335 	A subsystem consists of a toplevel config_group and a mutex.
336 The group is where child config_items are created.  For a subsystem,
338 configfs_register_subsystem(), the subsystem must have initialized the
341 	When the register call returns, the subsystem is live, and it
343 the subsystem must be ready for it.
348 subsystem/group and the simple_child item in
357 appear in a filesystem.  A subsystem is NEVER to touch the filesystem
358 parts, but the subsystem might be interested in this hierarchy.  For
362 A subsystem can navigate the cg_children list and the ci_parent pointer
363 to see the tree created by the subsystem.  This can race with configfs'
364 management of the hierarchy, so configfs uses the subsystem mutex to
365 protect modifications.  Whenever a subsystem wants to navigate the
366 hierarchy, it must do so under the protection of the subsystem
369 A subsystem will be prevented from acquiring the mutex while a newly
375 a subsystem to trust ci_parent and cg_children while they hold the
395 in its own subsystem).
399 this is a void function and cannot return failure.  The subsystem is
424 A configfs subsystem specifies default groups by adding them using the
429 method call notifies the subsystem the parent group is going away, it
470 after which the subsystem can start whatever entity this item
474 a target device, the subsystem has no idea what block device to import.
475 The simple example assumes that the subsystem merely waits until all the
481 Far better would be an explicit action notifying the subsystem that the
483 the subsystem to provide feedback as to whether the attributes are
499 directory.  At this point, the subsystem receives the ->commit_item()
505 time from the "live" directory back to the "pending" one.  The subsystem