| /linux/rust/kernel/irq/ |
| H A D | request.rs | 55 /// Proves the device is bound at registration time and ties `'a` to the device's bound
81 /// A registration of an IRQ handler for a given IRQ line. in drop()
133 /// let registration = unsafe {
144 /// let registration = KBox::pin_init(registration, GFP_KERNEL)?;
146 /// registration.handler().completion.wait_for_completion();
148 /// Ok(registration)
246 let registration = unsafe { &*ptr }; in try_synchronize()
248 T::handle(®istration.handler) as c_uint in try_synchronize()
285 /// A registration o
268 let registration = unsafe { &*(ptr as *const Registration<T>) }; handle_irq_callback() localVariable
489 let registration = unsafe { &*(ptr as *const ThreadedRegistration<T>) }; handle_threaded_irq_callback() localVariable
505 let registration = unsafe { &*(ptr as *const ThreadedRegistration<T>) }; thread_fn_callback() localVariable
[all...] |
| /linux/drivers/staging/media/sunxi/cedrus/ |
| H A D | TODO | 8 v4l2 and m2m devices registration;
9 - proc, with video device registration and related operations;
|
| /linux/drivers/md/bcache/ |
| H A D | Kconfig | 24 bool "Asynchronous device registration"
29 registration work is handled in kernel work queue in asynchronous
|
| /linux/Documentation/driver-api/thermal/ |
| H A D | cpu-cooling-api.rst | 14 The generic cpu cooling(freq clipping) provides registration/unregistration APIs
16 the user. The registration APIs returns the cooling device pointer.
21 1.1 cpufreq registration/unregistration APIs
61 The power API registration functions provide a simple power model for
|
| /linux/Documentation/driver-api/usb/ |
| H A D | typec.rst | 15 class. In a normal case the registration will be done by a USB Type-C or PD PHY
81 registration. The class offers the following API for registering/unregistering
87 The class will provide a handle to struct typec_partner if the registration was
111 followed by registration of the cable plugs. The cable will be the parent device
114 the details during registration. The class offers the following API for
121 the registration is successful, or NULL if it isn't.
172 own functions, but the registration will always return a handle to struct
|
| /linux/Documentation/crypto/ |
| H A D | devel-algos.rst | 7 There are three distinct types of registration functions in the Crypto
17 The generic registration functions can be found in
38 The registration functions return 0 on success, or a negative errno
60 The registration of [CIPHER] algorithm is specific in that struct
111 The registration of multi-block cipher algorithms is one of the most
|
| /linux/Documentation/driver-api/80211/ |
| H A D | cfg80211.rst | 8 Device registration
12 :doc: Device registration
|
| /linux/Documentation/driver-api/surface_aggregator/clients/ |
| H A D | san.rst | 22 registration and notifier-block registration.
|
| /linux/Documentation/ABI/testing/ |
| H A D | configfs-usb-gadget-phonet | 8 network device registration.
|
| H A D | sysfs-edac-scrub | 15 device driver during registration.
|
| /linux/Documentation/i2c/muxes/ |
| H A D | i2c-mux-gpio.rst | 69 If you don't know the absolute GPIO pin numbers at registration time,
85 GPIO pin numbers at registration time, this is even the only option.
|
| /linux/Documentation/leds/ |
| H A D | leds-blinkm.rst | 21 The registration follows the scheme::
43 The registration follows the scheme::
|
| H A D | ledtrig-transient.rst | 25 triggers it supports and a default trigger. During registration, activation
26 routine for the default trigger gets called. During registration of an led
45 trigger registration, for each led class device that specifies this trigger
47 registration, the LED state does not change, unless there is another trigger
|
| /linux/Documentation/trace/ |
| H A D | user_events.rst | 23 tools that can read trace_events (such as ftrace and perf). The registration
25 enabled the event and data should be written. The registration will give back
113 Upon successful registration the following is set.
117 descriptor that was used for the registration. See writing data for details.
174 to request deletes than the one used for registration due to this.
|
| H A D | kprobes.rst | 44 registration function such as register_kprobe() specifies where
49 registration/unregistration of a group of ``*probes``. These functions
159 private data object can be specified at kretprobe registration time by
387 specified, kprobe registration will fail with -EINVAL.
481 error occurs during registration, all probes in the array, up to
575 registration and unregistration.
603 on the x86_64 version of __switch_to(); the registration functions
|
| /linux/Documentation/networking/ |
| H A D | netdevices.rst | 39 In that case the struct net_device registration is done using
79 registration.
160 netdev state after allocating it and before registration.
169 or when register_netdevice() fails. Parts of netdev (de)registration process
180 registration and de-registration, under ``rtnl_lock``. Drivers can use
|
| /linux/Documentation/driver-api/acpi/ |
| H A D | scan_handlers.rst | 31 bridge, its registration should cause the PCI bus under that bridge to be
51 executed, respectively, after registration of new device nodes and before
|
| /linux/include/linux/ |
| H A D | hp_sdc.h | 293 #error No support for device registration on this arch yet.
|
| /linux/Documentation/translations/zh_CN/infiniband/ |
| H A D | user_mad.rst | 108 mad->hdr.id = my_agent; /* req.id from agent registration */
|
| /linux/Documentation/driver-api/ |
| H A D | regulator.rst | 133 :c:type:`regulator_consumer_supply`. This is done at driver registration
146 This is done at driver registration time` by providing a
|
| H A D | vfio-mediated-device.rst | 79 The mediated core driver provides the following types of registration
88 The registration interface for a mediated device driver provides the following
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A D | tps6507x.txt | 17 Missing of these properties can cause the regulator registration
|
| /linux/Documentation/locking/ |
| H A D | pi-futex.rst | 8 (or any other PI complexity) at all. No registration, no extra kernel
114 there is no prior 'registration' of a PI-futex. [which is not quite
|
| /linux/Documentation/networking/devlink/ |
| H A D | index.rst | 13 in devlink core, but don't allow registration of most sub-objects once
|
| /linux/drivers/md/dm-vdo/ |
| H A D | vdo.c | 109 list_for_each_entry(vdo, ®istry.links, registration) { in filter_vdos_locked()
428 INIT_LIST_HEAD(&vdo->registration); in register_vdo()
429 list_add_tail(&vdo->registration, ®istry.links); in register_vdo()
741 list_del_init(&vdo->registration); in unregister_vdo()
|