Lines Matching refs:subsystem

47 subsystems.  Once a client subsystem is loaded, it will appear as a
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
115 A subsystem is the top level of a client module.  During initialization,
116 the client module registers the subsystem with configfs, the subsystem
118 subsystem is also a config_group, and can do everything a config_group
142 structure that actually represents what the subsystem is doing.  The
156 Usually a subsystem wants the item to display and/or store attributes,
242 …vided, this method is called from mkdir(2) in the group's directory.  The subsystem allocates a new
247 If the subsystem wants the child to be a group itself, the subsystem
254 The subsystem must config_item_put() the reference that was initialized
255 upon item allocation.  If a subsystem has no work to do, it may omit
257 config_item_put() on the item on behalf of the subsystem.
261 (assuming that it has no children to keep it busy).  The subsystem is
262 responsible for responding to this.  If the subsystem has references to
264 for the item to actually disappear from the subsystem's usage.  But it
270 teardown happens, the subsystem can implement the
284 A subsystem must register itself, usually at module_init time.  This
285 tells configfs to make the subsystem appear in the file tree.
295 	A subsystem consists of a toplevel config_group and a mutex.
296 The group is where child config_items are created.  For a subsystem,
298 configfs_register_subsystem(), the subsystem must have initialized the
301 	When the register call returns, the subsystem is live, and it
303 the subsystem must be ready for it.
308 subsystem/group and the simple_child item in
317 appear in a filesystem.  A subsystem is NEVER to touch the filesystem
318 parts, but the subsystem might be interested in this hierarchy.  For
322 A subsystem can navigate the cg_children list and the ci_parent pointer
323 to see the tree created by the subsystem.  This can race with configfs'
324 management of the hierarchy, so configfs uses the subsystem mutex to
325 protect modifications.  Whenever a subsystem wants to navigate the
326 hierarchy, it must do so under the protection of the subsystem
329 A subsystem will be prevented from acquiring the mutex while a newly
335 a subsystem to trust ci_parent and cg_children while they hold the
355 in its own subsystem).
359 this is a void function and cannot return failure.  The subsystem is
384 A configfs subsystem specifies default groups by filling in the
389 method call notifies the subsystem the parent group is going away, it
430 after which the subsystem can start whatever entity this item
434 a target device, the subsystem has no idea what block device to import.
435 The simple example assumes that the subsystem merely waits until all the
441 Far better would be an explicit action notifying the subsystem that the
443 the subsystem to provide feedback as to whether the attributes are
459 directory.  At this point, the subsystem receives the ->commit_item()
465 time from the "live" directory back to the "pending" one.  The subsystem