Searched full:binding (Results 1 – 25 of 264) sorted by relevance
1234567891011
/linux-3.3/include/net/ |
D | mip6.h | 44 #define IP6_MH_TYPE_BRR 0 /* Binding Refresh Request */ 49 #define IP6_MH_TYPE_BU 5 /* Binding Update */ 50 #define IP6_MH_TYPE_BACK 6 /* Binding ACK */ 51 #define IP6_MH_TYPE_BERROR 7 /* Binding Error */
|
/linux-3.3/Documentation/devicetree/bindings/ |
D | open-pic.txt | 1 * Open PIC Binding 3 This binding specifies what properties must be available in the device tree 4 representation of an Open PIC compliant interrupt controller. This binding is 5 based on the binding defined for Open PIC in [1] and is a superset of that 6 binding.
|
D | vendor-prefixes.txt | 1 Device tree binding vendor prefix registry. Keep list in alphabetical order. 25 linux Linux-specific binding
|
/linux-3.3/drivers/char/ |
D | raw.c | 29 struct block_device *binding; member 69 bdev = raw_devices[minor].binding; in raw_open() 106 bdev = raw_devices[minor].binding; in raw_release() 164 if (rawdev->binding) { in bind_set() 165 bdput(rawdev->binding); in bind_set() 170 rawdev->binding = NULL; in bind_set() 173 rawdev->binding = bdget(dev); in bind_set() 174 if (rawdev->binding == NULL) { in bind_set() 199 bdev = rawdev->binding; in bind_get()
|
/linux-3.3/Documentation/console/ |
D | console.txt | 73 driver takes over the consoles vacated by the driver. Binding, on the other 77 NOTE1: Binding and unbinding must be selected in Kconfig. It's under: 79 Device Drivers -> Character devices -> Support for binding and unbinding 82 NOTE2: If any of the virtual consoles are in KD_GRAPHICS mode, then binding or 109 In order for binding to and unbinding from the console to properly work, 138 The current crop of console drivers should still work correctly, but binding
|
/linux-3.3/drivers/scsi/lpfc/ |
D | lpfc_disc.h | 147 #define NLP_TGT_NO_SCSIID 0x00200000 /* good PRLI but no binding for scsid */ 194 * that we have saved binding information on. This information is used when 218 * node, the node is taken off the unmapped list. The binding list is checked 219 * for a valid binding, or a binding is automatically assigned. If binding 221 * binding assignment is successful, the associated binding list entry (if
|
/linux-3.3/Documentation/driver-model/ |
D | binding.txt | 2 Driver Binding 4 Driver binding is the process of associating a device with a device 8 structures, most of the binding can take place using common code. 19 two events which trigger driver binding.
|
D | platform.txt | 21 Platform devices are given a name, used in driver binding, and a 139 Device Naming and Driver Binding 154 Driver binding is performed automatically by the driver core, invoking
|
/linux-3.3/include/xen/interface/ |
D | event_channel.h | 56 * 2. The allocated event channel is bound to the specified vcpu. The binding 87 * 1. The allocated event channel is bound to the specified vcpu. The binding 158 * the binding. This binding cannot be changed. 161 * has its binding reset to vcpu0).
|
/linux-3.3/Documentation/devicetree/bindings/spi/ |
D | spi-bus.txt | 6 SPI master mode. This binding does not describe SPI controllers 17 However, the binding does not attempt to define the specific method for 19 flexible and non-standardized, it is left out of this binding with the
|
/linux-3.3/Documentation/i2c/ |
D | old-module-parameters | 1 I2C device driver binding control from user-space 12 binding model, it became clear that these per-module parameters were no 42 other drivers from binding to it later on. If there is a real device at the
|
/linux-3.3/Documentation/devicetree/bindings/powerpc/fsl/ |
D | srio-rmu.txt | 62 binding document describing the node's interrupt parent. 92 binding document describing the node's interrupt parent. 122 binding document describing the node's interrupt parent.
|
D | srio.txt | 28 binding document describing the node's interrupt parent. 37 (See srio-rmu.txt for more details on RMU node binding)
|
D | mpic.txt | 8 notable difference from Open PIC binding is the addition of 2 18 controllers compatible with this binding have Block
|
/linux-3.3/drivers/mtd/maps/ |
D | physmap_of.c | 7 * Revised to handle newer style flash binding by: 78 * compatible binding, which has an extra "probe-type" property 91 "flash binding\n"); in obsolete_probe() 312 * vendor and device ids specified by the binding to
|
/linux-3.3/Documentation/devicetree/bindings/gpio/ |
D | gpio.txt | 18 binding for each device. 45 be documented in the device tree binding for the device.
|
/linux-3.3/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
D | qe.txt | 4 NOTE: This is an interim binding; it should be updated to fit 5 in with the CPM binding later in this document.
|
/linux-3.3/Documentation/devicetree/bindings/crypto/ |
D | fsl-sec4.txt | 2 SEC 4 Device Tree Binding 92 of the specifier is defined by the binding document 154 of the specifier is defined by the binding document 303 of the specifier is defined by the binding document
|
/linux-3.3/Documentation/devicetree/bindings/mtd/ |
D | arm-versatile.txt | 8 - Subnode partition map from mtd flash binding
|
/linux-3.3/tools/perf/util/ui/browsers/ |
D | map.c | 64 sym->binding == STB_GLOBAL ? 'g' : in map_browser__write() 65 sym->binding == STB_LOCAL ? 'l' : 'w'); in map_browser__write()
|
/linux-3.3/drivers/mtd/ |
D | ofpart.c | 7 * Revised to handle newer style flash binding by: 118 pr_warning("Device tree uses obsolete partition map binding: %s\n", in parse_ofoldpart_partitions()
|
/linux-3.3/Documentation/devicetree/bindings/i2c/ |
D | arm-versatile.txt | 10 - Child nodes conforming to i2c bus binding
|
/linux-3.3/include/linux/ |
D | capability.h | 186 /* Allows binding to TCP/UDP sockets below 1024 */ 187 /* Allows binding to ATM VCIs below 32 */ 201 /* Allow binding to any address for transparent proxying (also via NET_RAW) */ 213 /* Allow binding to any address for transparent proxying (also via NET_ADMIN) */
|
/linux-3.3/drivers/staging/usbip/userspace/doc/ |
D | usbip_bind_driver.8 | 3 usbip_bind_driver \- change driver binding for USB/IP
|
/linux-3.3/Documentation/devicetree/bindings/regulator/ |
D | fixed-regulator.txt | 13 binding, defined in regulator.txt, can also be used.
|
1234567891011