/kernel/linux/linux-5.10/drivers/misc/sgi-xp/ |
D | xp_main.c | 137 struct xpc_registration *registration; in xpc_connect() local 147 registration = &xpc_registrations[ch_number]; in xpc_connect() 149 if (mutex_lock_interruptible(®istration->mutex) != 0) in xpc_connect() 153 if (registration->func != NULL) { in xpc_connect() 154 mutex_unlock(®istration->mutex); in xpc_connect() 159 registration->entry_size = XPC_MSG_SIZE(payload_size); in xpc_connect() 160 registration->nentries = nentries; in xpc_connect() 161 registration->assigned_limit = assigned_limit; in xpc_connect() 162 registration->idle_limit = idle_limit; in xpc_connect() 163 registration->key = key; in xpc_connect() [all …]
|
D | xpc_channel.c | 468 struct xpc_registration *registration = &xpc_registrations[ch->number]; in xpc_connect_channel() local 470 if (mutex_trylock(®istration->mutex) == 0) in xpc_connect_channel() 474 mutex_unlock(®istration->mutex); in xpc_connect_channel() 485 mutex_unlock(®istration->mutex); in xpc_connect_channel() 491 ch->kthreads_assigned_limit = registration->assigned_limit; in xpc_connect_channel() 492 ch->kthreads_idle_limit = registration->idle_limit; in xpc_connect_channel() 497 ch->func = registration->func; in xpc_connect_channel() 498 DBUG_ON(registration->func == NULL); in xpc_connect_channel() 499 ch->key = registration->key; in xpc_connect_channel() 501 ch->local_nentries = registration->nentries; in xpc_connect_channel() [all …]
|
/kernel/linux/linux-5.10/drivers/md/bcache/ |
D | Kconfig | 31 bool "Asynchronous device registration (EXPERIMENTAL)" 36 registration work is handled in kernel work queue in asynchronous
|
/kernel/linux/linux-5.10/Documentation/driver-api/thermal/ |
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
|
/kernel/linux/linux-5.10/Documentation/infiniband/ |
D | user_mad.rst | 18 descriptor for the appropriate device file. If the registration 34 a new registration ioctl is now provided which allows additional 35 fields to be provided during registration. 36 Users of this registration call are implicitly setting the use of 100 mad->hdr.id = my_agent; /* req.id from agent registration */
|
/kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
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
|
/kernel/linux/linux-5.10/Documentation/driver-api/80211/ |
D | cfg80211.rst | 8 Device registration 12 :doc: Device registration
|
/kernel/linux/linux-5.10/Documentation/crypto/ |
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
|
/kernel/linux/linux-5.10/Documentation/ABI/testing/ |
D | configfs-usb-gadget-phonet | 8 network device registration.
|
/kernel/linux/linux-5.10/Documentation/i2c/muxes/ |
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.
|
/kernel/linux/linux-5.10/Documentation/leds/ |
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
|
D | leds-blinkm.rst | 21 The registration follows the scheme::
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/ |
D | i2c-omap.txt | 23 from omap hwmod data base during device registration.
|
/kernel/linux/linux-5.10/Documentation/isdn/ |
D | interface_capi.rst | 18 application registration to an available device, forwarding it to the 34 driver. The registration can be revoked by calling the function 51 Kernel CAPI forwards registration requests from applications (calls to CAPI 90 driver. After registration via the attach_capi_ctr() function it is passed to 133 pointers to callback function for registration of
|
/kernel/linux/linux-5.10/Documentation/gpu/ |
D | drm-internals.rst | 65 used for IRQ registration and passed to userspace through 150 A number of functions are provided to help with device registration. The 223 legacy shadow-attach driver registration functions. New driver should
|
/kernel/linux/linux-5.10/Documentation/driver-api/acpi/ |
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
|
/kernel/linux/linux-5.10/Documentation/core-api/ |
D | cpu_hotplug.rst | 171 will be invoked during registration on all online CPUs. If an error 174 After registration completed, the *Y_online* callback will be invoked 179 registration process. Otherwise a positive value is returned which 217 Usually it is handy to invoke setup and teardown callbacks on registration or 220 each registration and removal function is also available with a ``_nocalls``
|
/kernel/linux/linux-5.10/include/linux/ |
D | hp_sdc.h | 293 #error No support for device registration on this arch yet.
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/can/ |
D | c_can.txt | 33 resources from TI, omap hwmod data base during device registration.
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/ |
D | slg51000.txt | 8 An absence of these properties can cause the regulator registration to fail.
|
/kernel/linux/linux-5.10/Documentation/filesystems/caching/ |
D | netfs-api.rst | 29 (4) Network filesystem (un)registration 31 (6) Index registration 32 (7) Data file registration 33 (8) Miscellaneous object registration 59 This first two fields should be filled in before registration, and the third 60 will be filled in by the registration function; any other fields should just be 72 another parameter passed into the registration function. 240 Network Filesystem (Un)registration 247 The registration function is:: 254 For kAFS, registration is done as follows::
|
/kernel/linux/linux-5.10/Documentation/driver-api/ |
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
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
D | tps6507x.txt | 17 Missing of these properties can cause the regulator registration
|
/kernel/linux/linux-5.10/Documentation/driver-api/driver-model/ |
D | platform.rst | 217 The architecture code may optionally force registration of all early 224 4. Early platform driver registration 241 when it comes to memory allocation and interrupt registration. The code
|
/kernel/linux/linux-5.10/Documentation/locking/ |
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
|