| /linux-4.4.14/drivers/misc/sgi-xp/ |
| D | xp_main.c | 160 struct xpc_registration *registration; in xpc_connect() local
170 registration = &xpc_registrations[ch_number]; in xpc_connect()
172 if (mutex_lock_interruptible(®istration->mutex) != 0) in xpc_connect()
176 if (registration->func != NULL) { in xpc_connect()
177 mutex_unlock(®istration->mutex); in xpc_connect()
182 registration->entry_size = XPC_MSG_SIZE(payload_size); in xpc_connect()
183 registration->nentries = nentries; in xpc_connect()
184 registration->assigned_limit = assigned_limit; in xpc_connect()
185 registration->idle_limit = idle_limit; in xpc_connect()
186 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 …]
|
| /linux-4.4.14/Documentation/ |
| D | sgi-ioc4.txt | 25 This driver also provides registration functions that the other
38 up to the ioc4 driver via the appropriate registration, probe, and
44 other than it hooks up to the ioc4 driver via the appropriate registration,
|
| D | vme_api.txt | 4 Driver registration
13 If driver registration is successful this function returns zero, if an error
17 registration function. The structure is as follows:
75 be called the number of times specified during the registration. If a match
|
| D | pi-futex.txt | 7 (or any other PI complexity) at all. No registration, no extra kernel
113 there is no prior 'registration' of a PI-futex. [which is not quite
|
| D | robust-futexes.txt | 88 registration happens at most once per thread lifetime]. At do_exit()
129 - no registration of individual locks is needed: robust mutexes dont
176 List registration is very fast: the pointer is simply stored in
|
| D | kprobes.txt | 39 registration function such as register_kprobe() specifies where
44 registration/unregistration of a group of *probes. These functions
159 private data object can be specified at kretprobe registration time by
362 specified, kprobe registration will fail with -EINVAL.
471 error occurs during registration, all probes in the array, up to
557 registration and unregistration.
586 on the x86_64 version of __switch_to(); the registration functions
|
| D | media-framework.txt | 53 registration. The following fields must be set:
83 Upon successful registration a character device named media[0-9]+ is created.
133 ID by filling the media_entity id field prior to registration, or request the
|
| D | ntb.txt | 26 registration uses the Linux Device framework, so it should feel familiar to
|
| D | clk.txt | 221 registration function. This function simply populates struct clk_foo's
|
| D | remoteproc.txt | 100 the registration of the remote processor.
|
| D | kernel-parameters.txt | 3460 security module asking for security registration will be
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | user_mad.txt | 14 descriptor for the appropriate device file. If the registration
29 2014 -- a new registration ioctl is now provided which allows additional
30 fields to be provided during registration.
31 Users of this registration call are implicitly setting the use of
91 mad->hdr.id = my_agent; /* req.id from agent registration */
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | configfs-usb-gadget-phonet | 8 network device registration.
|
| /linux-4.4.14/Documentation/i2c/muxes/ |
| D | i2c-mux-gpio | 67 If you don't know the absolute GPIO pin numbers at registration time,
83 GPIO pin numbers at registration time, this is even the only option.
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | mflash.txt | 6 3. Example of mflash platform driver registration
32 3. Example of mflash platform driver registration
|
| D | paride.txt | 169 is the parallel port base address, the 0 is the protocol registration
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | davinci-mdio.txt | 14 resources from TI, omap hwmod data base during device registration.
|
| D | cpsw.txt | 57 resources from TI, omap hwmod data base during device registration.
|
| /linux-4.4.14/drivers/gpu/drm/bridge/ |
| D | Kconfig | 5 Bridge registration and lookup framework.
|
| /linux-4.4.14/Documentation/leds/ |
| D | ledtrig-transient.txt | 30 triggers it supports and a default trigger. During registration, activation
31 routine for the default trigger gets called. During registration of an led
50 trigger registration, for each led class device that specifies this trigger
52 registration, the LED state does not change, unless there is another trigger
|
| D | leds-blinkm.txt | 17 The registration follows the scheme:
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-omap.txt | 18 from omap hwmod data base during device registration.
|
| /linux-4.4.14/Documentation/thermal/ |
| D | cpu-cooling-api.txt | 12 The generic cpu cooling(freq clipping) provides registration/unregistration APIs
14 the user. The registration APIs returns the cooling device pointer.
18 1.1 cpufreq registration/unregistration APIs
69 The power API registration functions provide a simple power model for
|
| D | sysfs-api.txt | 234 This is given by thermal zone driver as part of registration.
|
| /linux-4.4.14/Documentation/isdn/ |
| D | INTERFACE.CAPI | 16 application registration to an available device, forwarding it to the
30 registration can be revoked by calling the function unregister_capi_driver()
38 driver. The registration can be revoked by calling the function
54 Kernel CAPI forwards registration requests from applications (calls to CAPI
93 driver. After registration via the attach_capi_ctr() function it is passed to
131 pointers to callback functions for registration and deregistration of
|
| D | HiSax.cert | 79 Here are the certification registration numbers for ELSA Quickstep cards:
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/can/ |
| D | c_can.txt | 22 resources from TI, omap hwmod data base during device registration.
|
| /linux-4.4.14/Documentation/arm/ |
| D | 00-INDEX | 34 - Secure firmware registration and calling.
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | hwmon-kernel-api.txt | 43 or PTR_ERR for failure. If this registration function is used, hardware
50 device name. The registration function wil create a name sysfs attribute
|
| /linux-4.4.14/drivers/gpu/drm/panel/ |
| D | Kconfig | 5 Panel registration and lookup framework.
|
| /linux-4.4.14/Documentation/acpi/ |
| D | scan_handlers.txt | 25 bridge, its registration should cause the PCI bus under that bridge to be
45 executed, respectively, after registration of new device nodes and before
|
| /linux-4.4.14/include/linux/ |
| D | hp_sdc.h | 293 #error No support for device registration on this arch yet.
|
| /linux-4.4.14/drivers/infiniband/ |
| D | Kconfig | 48 Together with driver support this allows registration of
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | tps6507x.txt | 17 Missing of these properties can cause the regulator registration
|
| D | tps65910.txt | 30 properties can cause the regulator registration fails.
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 27 (4) Network filesystem (un)registration
29 (6) Index registration
30 (7) Data file registration
31 (8) Miscellaneous object registration
58 This first two fields should be filled in before registration, and the third
59 will be filled in by the registration function; any other fields should just be
71 another parameter passed into the registration function.
285 The registration function is:
292 For kAFS, registration is done as follows:
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | platform.txt | 215 The architecture code may optionally force registration of all early
222 4. Early platform driver registration
239 when it comes to memory allocation and interrupt registration. The code
|
| D | porting.txt | 123 - Initialize the device on registration.
329 registered with the bus at any time. When registration happens,
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | overview.txt | 20 * Basic device registration and handling. This is very similar to
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | firmware-assisted-dump.txt | 84 next firmware-assisted dump registration.
188 This is used to display the fadump registration status as well
189 as to control (start/stop) the fadump registration.
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | dnotify.txt | 24 if DN_MULTISHOT is or'ed with the event mask, then the registration will
|
| /linux-4.4.14/Documentation/wimax/ |
| D | README.wimax | 35 For usage in a driver (registration, API, etc) please refer to the
|
| /linux-4.4.14/Documentation/mic/ |
| D | scif_overview.txt | 17 5. Memory registration to pin down pages
|
| /linux-4.4.14/Documentation/ptp/ |
| D | ptp.txt | 59 registration method. Clock drivers must implement all of the
|
| /linux-4.4.14/Documentation/misc-devices/mei/ |
| D | mei-client-bus.txt | 88 pr_err(CONTACT_DRIVER_NAME ": driver registration failed\n");
|
| /linux-4.4.14/Documentation/scsi/ |
| D | libsas.txt | 15 * SCSI Host registration/unregistration,
16 * Device registration with SCSI Core (SAS) or libata
203 A sample initialization and registration function
|
| D | aacraid.txt | 124 Christoph Hellwig <hch@infradead.org> (updates for new-style PCI probing and SCSI host registration,
|
| D | scsi_mid_low_api.txt | 88 b) passing a set of function pointers to a registration function
297 registration and de-registration are (typically) tied to LLD initialization
370 scsi_add_host - perform sysfs registration and set up transport class
418 * scsi_add_host - perform sysfs registration and set up transport class
507 * Full registration (in sysfs) and a bus scan are performed later when
|
| D | ChangeLog.1992-1997 | 377 * eata_dma: Update to version 2.10i. Remove bug in the registration
|
| D | ChangeLog.lpfc | 1846 * New Linux 2.6 style of char device registration.
|
| /linux-4.4.14/Documentation/fmc/ |
| D | carrier.txt | 28 at registration time.
60 registration:
105 * nr_slots: set by the core at registration time.
|
| /linux-4.4.14/drivers/misc/mic/ |
| D | Kconfig | 64 crash events to the host and allows registration/configuration of
|
| /linux-4.4.14/Documentation/trace/ |
| D | coresight.txt | 141 a reference to a "struct coresight_device", obtained at registration time.
143 If everything goes well during the registration process the new devices will
|
| D | tracepoints.txt | 105 is done at the registration site by the compiler. Tracepoints can be
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | msr.txt | 68 write, or registration, is needed for each VCPU. The interval between
215 write, or registration, is needed for each VCPU. The interval between
|
| D | api.txt | 3256 developer registration required to access it).
|
| /linux-4.4.14/Documentation/networking/ |
| D | ieee802154.txt | 74 provides interface for drivers registration and management of slave interfaces.
|
| D | netdev-features.txt | 54 1. device's registration, after ndo_init returned success
|
| /linux-4.4.14/Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 170 Payload handling and registration is done using standard Linux mechanisms.
|
| D | spi_porting.txt | 88 the sysfs directory of the cfspi_sspi driver (before device registration).
|
| /linux-4.4.14/Documentation/arm/OMAP/ |
| D | omap_pm | 134 and the registration of OPP table should take place automatically.
|
| /linux-4.4.14/Documentation/crypto/ |
| D | api-intro.txt | 32 The idea is to make the user interface and algorithm registration API
|
| /linux-4.4.14/scripts/ |
| D | spelling.txt | 815 registraration||registration
820 reigstration||registration
|
| /linux-4.4.14/net/wireless/ |
| D | Kconfig | 133 capabilities in their registration flow.
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | v4l2-framework.txt | 348 Using one or the other registration method only affects the probing process, the
486 sub-device. After registration events can be queued as usual on the
749 video_device registration
815 If the registration failed, then you need to call video_device_release()
818 be called if the registration failed, nor should you ever attempt to
819 unregister the device if the registration failed.
|
| /linux-4.4.14/sound/pci/hda/ |
| D | Kconfig | 65 int "Digital beep registration mode (0=off, 1=on)"
|
| /linux-4.4.14/Documentation/rapidio/ |
| D | rapidio.txt | 163 device registration. For example, in a system with two RapidIO controllers
225 registration. For example for machine with single RapidIO controller, mport_ID
|
| /linux-4.4.14/drivers/mtd/chips/ |
| D | Kconfig | 222 preserves the expected registration order of MTD device nodes on
|
| /linux-4.4.14/drivers/media/usb/pwc/ |
| D | philips.txt | 175 - If a device node is already occupied, registration will fail and
|
| /linux-4.4.14/drivers/staging/fsl-mc/ |
| D | README.txt | 309 -implemeting APIs for DPAA2 driver registration and for device
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | watchdog-kernel-api.txt | 39 The watchdog subsystem includes an registration deferral mechanism,
|
| /linux-4.4.14/Documentation/arm64/ |
| D | arm-acpi.txt | 288 also be submitting registration requests and this may help smooth the
291 Once registration and review have been completed, the kernel provides an
|
| /linux-4.4.14/Documentation/timers/ |
| D | highres.txt | 117 registration interface it provides functions to schedule the next event
|
| /linux-4.4.14/Documentation/serial/ |
| D | tty.txt | 12 discipline number and the ldisc structure. At the point of registration the
|
| /linux-4.4.14/drivers/staging/unisys/Documentation/ |
| D | overview.txt | 60 devices reside. It provides a registration function named
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | Introduction | 61 a set of functions for registration of devices
|
| /linux-4.4.14/Documentation/vm/ |
| D | frontswap.txt | 155 kernel initialization; this registration indicates that this
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | provider.txt | 105 Just like any other kernel framework, the whole DMAEngine registration
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | cdrom-standard.tex | 312 registration.
340 corresponding capability flags will be cleared upon registration.
552 capability-constants that are defined in \cdromh\ at the registration
|
| /linux-4.4.14/Documentation/power/ |
| D | runtime_pm.txt | 780 initialized and before it is registered (although after device registration is
815 registration the length should be controlled by user space, using the
|
| D | devices.txt | 262 In particular, this means that a device registration may fail if the parent of
|
| /linux-4.4.14/Documentation/networking/dsa/ |
| D | dsa.txt | 378 registration to test for the presence/absence of a switch device. For MDIO
|
| /linux-4.4.14/crypto/ |
| D | Kconfig | 142 algorithm registration.
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | ALSA-Configuration.txt | 884 beep_mode - Selects the beep registration mode (0=off, 1=on); default
|