centos man page for device_schedule_callback_owner

Query: device_schedule_callback_owner

OS: centos

Section: 9

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

DEVICE_SCHEDULE_CALL(9) 				   Device drivers infrastructure				   DEVICE_SCHEDULE_CALL(9)

NAME
device_schedule_callback_owner - helper to schedule a callback for a device
SYNOPSIS
int device_schedule_callback_owner(struct device * dev, void (*func) (struct device *), struct module * owner);
ARGUMENTS
dev device. func callback function to invoke later. owner module owning the callback routine
DESCRIPTION
Attribute methods must not unregister themselves or their parent device (which would amount to the same thing). Attempts to do so will deadlock, since unregistration is mutually exclusive with driver callbacks. Instead methods can call this routine, which will attempt to allocate and schedule a workqueue request to call back func with dev as its argument in the workqueue's process context. dev will be pinned until func returns. This routine is usually called via the inline device_schedule_callback, which automatically sets owner to THIS_MODULE. Returns 0 if the request was submitted, -ENOMEM if storage could not be allocated, -ENODEV if a reference to owner isn't available.
NOTE
This routine won't work if CONFIG_SYSFS isn't set! It uses an underlying sysfs routine (since it is intended for use by attribute methods), and if sysfs isn't available you'll get nothing but -ENOSYS.
COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 DEVICE_SCHEDULE_CALL(9)
Related Man Pages
device_create(9) - centos
device_create_with_groups(9) - centos
struct_bus_type(9) - centos
struct_device_driver(9) - centos
workqueue(9) - netbsd
Similar Topics in the Unix Linux Community
deleting file that isn't really there
involuntary context switching