Lines Matching refs:with

13 place. Dealing with kobjects requires understanding a few different types,
15 easier, we'll take a multi-pass approach, starting with vague terms and
17 some terms we will be working with.
51 It is rare for kernel code to create a standalone kobject, with one major
62 (As an aside, for those familiar with the kernel linked list implementation,
68 defines the memory region associated with a uio device:
76 just a matter of using the kobj member.  Code that works with kobjects will
93 *containing* uio_map structure with:
109 question.  That macro is subsequently invoked with:
117 of the internal fields are setup with a (mandatory) call to kobject_init():
123 register the kobject with sysfs, the function kobject_add() must be called:
128 properly.  If the kobject is to be associated with a specific kset,
130 associated with a kobject, then the parent for the kobject can be set to
165 After a kobject has been registered with the kobject core, you need to
166 announce to the world that it has been created.  This can be done with a
214 in the sysfs hierarchy, and not have to mess with the whole complication of
223 associated with this kobject, use:
229 Both types of attributes used here, with a kobject that has been created
230 with the kobject_create_and_add(), can be of type kobj_attribute, so no
283 instead, it is associated with the ktype. So let us introduce struct
305 automatically created for any kobject that is registered with this ktype.
310 A kset is merely a collection of kobjects that want to be associated with
320    with the kset can show up.  Every kset contains a kobject which can be
343 When you are finished with the kset, call:
354 associated with it, it can use the struct kset_uevent_ops to handle it:
384 before the kobject is added, the kobject is registered with the kset, but
390 After a kobject has been registered with the kobject core successfully, it
391 must be cleaned up when the code is finished with it.  To do that, call
402 the cleanup of the memory associated with the kobject.
407 with an explicit call to kobject_del(), so that a release functions will be