/linux-4.1.27/Documentation/usb/ |
D | bulk-streams.txt | 33 allocate memory so the driver can use up to num_streams stream IDs. They must 35 IDs. This is to ensure that a UASP driver will be able to use the same stream 41 declares how many stream IDs it can support, and each bulk endpoint on a 42 SuperSpeed device will say how many stream IDs it can handle. Therefore, 43 drivers should be able to deal with being allocated less stream IDs than they 55 Picking new Stream IDs to use 64 driver supports secondary stream IDs. 77 All stream IDs will be deallocated when the driver releases the interface, to
|
D | persist.txt | 81 same descriptors as before, including the Vendor and Product IDs, then 141 manufacturer, same IDs, and so on) there's an excellent chance the
|
D | usb-serial.txt | 349 the same Vendor ID but different Product IDs. Sitecom's U232-P25 serial
|
/linux-4.1.27/Documentation/devicetree/bindings/clock/ |
D | mvebu-core-clock.txt | 7 The following is a list of provided IDs and clock names on Armada 370/XP: 14 The following is a list of provided IDs and clock names on Armada 375: 20 The following is a list of provided IDs and clock names on Armada 380/385: 26 The following is a list of provided IDs and clock names on Armada 39x: 34 The following is a list of provided IDs and clock names on Kirkwood and Dove: 40 The following is a list of provided IDs and clock names on Orion5x:
|
D | mvebu-gated-clock.txt | 10 The following is a list of provided IDs for Armada 370: 26 The following is a list of provided IDs for Armada 375: 53 The following is a list of provided IDs for Armada 380/385: 80 The following is a list of provided IDs for Armada 39x: 92 The following is a list of provided IDs for Armada XP: 119 The following is a list of provided IDs for Dove: 142 The following is a list of provided IDs for Kirkwood:
|
D | imx6sl-clock.txt | 10 for the full list of i.MX6 SoloLite clock IDs.
|
D | efm32-clock.txt | 11 IDs.
|
D | clps711x-clock.txt | 11 for the full list of CLPS711X clock IDs.
|
D | mvebu-corediv-clock.txt | 3 The following is a list of provided IDs and clock names on Armada 370/XP:
|
D | imx6sx-clock.txt | 13 for the full list of i.MX6 SoloX clock IDs.
|
D | lsi,axm5516-clks.txt | 11 supported clock IDs.
|
D | imx27-clock.txt | 11 for the full list of i.MX27 clock IDs.
|
D | imx1-clock.txt | 10 for the full list of i.MX1 clock IDs.
|
D | imx21-clock.txt | 11 for the full list of i.MX21 clock IDs.
|
D | imx5-clock.txt | 11 for the full list of i.MX5 clock IDs.
|
D | imx6q-clock.txt | 11 for the full list of i.MX6 Quad and DualLite clock IDs.
|
D | imx23-clock.txt | 10 clocks and IDs.
|
D | prima2-clock.txt | 11 clocks and IDs.
|
D | imx31-clock.txt | 11 clocks and IDs.
|
D | imx28-clock.txt | 10 clocks and IDs.
|
D | vf610-clock.txt | 23 for the full list of VF610 clock IDs.
|
D | imx35-clock.txt | 11 clocks and IDs.
|
D | nvidia,tegra124-car.txt | 17 <dt-bindings/clock/tegra124-car-common.h> (which covers IDs common
|
D | imx25-clock.txt | 11 clocks and IDs.
|
D | sunxi.txt | 111 IDs 1 and 2, respectively.
|
/linux-4.1.27/Documentation/devicetree/bindings/arm/ |
D | psci.txt | 27 0.2. For these cases function IDs must be provided. 30 IDs are not required and should be ignored by an OS with PSCI 0.2 86 A DTB may provide IDs for use by kernels without PSCI 0.2 support, 88 These IDs will be ignored by kernels with PSCI 0.2 support, which will 89 use the standard PSCI 0.2 IDs exclusively.
|
/linux-4.1.27/Documentation/devicetree/bindings/usb/ |
D | keystone-usb.txt | 15 - clocks: Clock IDs array as required by the controller. 16 - clock-names: names of clocks correseponding to IDs in the clock property.
|
D | samsung-usbphy.txt | 17 - clocks: Clock IDs array as required by the controller. 18 - clock-names: names of clock correseponding IDs clock property as requested 78 - clocks: Clock IDs array as required by the controller. 79 - clock-names: names of clocks correseponding to IDs in the clock property
|
D | exynos-usb.txt | 93 - clocks: Clock IDs array as required by the controller. 94 - clock-names: names of clocks correseponding to IDs in the clock property
|
/linux-4.1.27/Documentation/namespaces/ |
D | compatibility-list.txt | 18 1. Both the IPC and the PID namespaces provide IDs to address 28 2. Intentionally, two equal user IDs in different user namespaces
|
/linux-4.1.27/Documentation/devicetree/bindings/video/ |
D | exynos_hdmi.txt | 16 - clocks: list of clock IDs from SoC clock driver. 27 - clock-names: aliases as per driver requirements for above clock IDs:
|
D | exynos_mixer.txt | 14 - clocks: list of clock IDs from SoC clock driver.
|
/linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
D | mc13xxx.txt | 28 MC13783 LED IDs: 42 MC13892 LED IDs: 50 MC34708 LED IDs:
|
D | rk808.txt | 9 outputs). See <dt-bindings/clock/rockchip,rk808.h> for clock IDs.
|
/linux-4.1.27/arch/powerpc/include/asm/ |
D | hydra.h | 32 u_int IDs; member
|
/linux-4.1.27/Documentation/driver-model/ |
D | binding.txt | 27 ID of the device must match one of the device IDs that the driver 28 supports. The format and semantics for comparing IDs is bus-specific. 31 a device against the IDs of a driver. The bus returns 1 if a match was
|
D | bus.txt | 45 of device IDs of devices they support that reside in a bus-specific 50 comparing the device IDs the driver supports with the device ID of a
|
D | porting.txt | 333 A driver typically contains a list of device IDs that it supports. The 334 bus driver compares these IDs to the IDs of devices registered with it. 335 The format of the device IDs, and the semantics for comparing them are
|
D | driver.txt | 46 typically defines an array of device IDs that it supports. The format 47 of these structures and the semantics for comparing device IDs are
|
/linux-4.1.27/Documentation/ |
D | pnp.txt | 24 id - displays a list of support EISA IDs 141 1.) the protocol must use EISA IDs 161 - adds an EISA ID to the list of supported IDs for the specified device 190 Supported PnP card IDs can optionally be defined.
|
D | media-framework.txt | 135 IDs manually must ensure that all IDs are unique. IDs are not guaranteed to be 142 Unregistering an entity will not change the IDs of the other entities, and the
|
D | svga.txt | 68 next section for a description of mode IDs). 99 3. Mode IDs 101 Because of the complexity of all the video stuff, the video mode IDs 241 flag, 0xffff and 0xfffe became aliases instead of real IDs.
|
D | pwm.txt | 15 Users of the legacy PWM API use unique IDs to refer to PWM devices.
|
D | stable_kernel_rules.txt | 21 - New device IDs and quirks are also accepted.
|
D | vme_api.txt | 306 specific VME level and status IDs.
|
D | 00-INDEX | 207 - notes on the change from 16 bit to 32 bit user/group IDs.
|
D | parport-lowlevel.txt | 789 Many devices have ill-formed IEEE 1284 Device IDs.
|
D | SubmittingPatches | 183 collisions with shorter IDs a real possibility. Bear in mind that, even if
|
D | kernel-parameters.txt | 1276 hvc_iucv_allow= [S390] Comma-separated list of z/VM user IDs. 1278 from listed z/VM user IDs only. 1907 port specification list means that device IDs
|
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
D | brcm,bcm2835-gpio.txt | 40 - brcm,pins: An array of cells. Each cell contains the ID of a pin. Valid IDs 41 are the integer GPIO IDs; 0==GPIO0, 1==GPIO1, ... 53==GPIO53.
|
D | pinctrl-bindings.txt | 39 those names to the integer IDs. 43 IDs that must be provided, or whether to define the set of state names that 83 /* For the same device if using state IDs */ 223 - pins takes a list of pin names or IDs as a required argument. The specific
|
/linux-4.1.27/Documentation/devicetree/bindings/media/ |
D | exynos5-gsc.txt | 21 to retrieve the device IDs using "of_alias_get_id()" call.
|
/linux-4.1.27/Documentation/devicetree/bindings/sound/ |
D | nvidia,tegra30-i2s.txt | 15 - nvidia,ahub-cif-ids : The list of AHUB CIF IDs for this port, rx (playback)
|
D | nvidia,tegra30-ahub.txt | 58 AHUB client modules need to specify the IDs of their CIFs (Client InterFaces).
|
/linux-4.1.27/Documentation/pcmcia/ |
D | driver.txt | 8 New PCMCIA IDs may be added to a device driver pcmcia_device_id table at
|
/linux-4.1.27/Documentation/devicetree/bindings/soc/fsl/ |
D | qman-portals.txt | 55 IDs by 8 102 IDs by 8
|
/linux-4.1.27/Documentation/filesystems/ |
D | udf.txt | 45 IDs on the disk, not just -1. The forget option causes all IDs to be written
|
D | exofs.txt | 137 IDs correspond to the files' inode numbers and will be allocated according to
|
D | xfs.txt | 302 ID or one of the supplementary group IDs of the parent dir, the
|
/linux-4.1.27/Documentation/acpi/ |
D | enumeration.txt | 37 for the device and add supported ACPI IDs. If this same IP-block is used on 46 /* ACPI IDs here */ 164 The SPI device drivers only need to add ACPI IDs in a similar way than with 224 The slaves behind I2C bus controller only need to add the ACPI IDs like
|
D | scan_handlers.txt | 42 where ids is the list of IDs of device nodes the given handler is supposed to
|
/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-bus-acpi | 16 This attribute indicates the PNP IDs of the device object.
|
D | sysfs-bus-usb | 67 device IDs in the same format, with one entry per 100 device IDs, exactly like reading from the entry
|
/linux-4.1.27/Documentation/devicetree/bindings/phy/ |
D | samsung-phy.txt | 134 - clocks: Clock IDs array as required by the controller 135 - clock-names: names of clocks correseponding to IDs in the clock property;
|
/linux-4.1.27/Documentation/rapidio/ |
D | tsi721.txt | 12 destination IDs without need for changes in outbound window translation.
|
/linux-4.1.27/Documentation/w1/ |
D | w1.netlink | 108 len is equal to number of IDs multiplied by 8] 111 w1_netlink_cmd->len = N * 8; where N is number of IDs in this message.
|
/linux-4.1.27/Documentation/networking/ |
D | can.txt | 106 frames on different or the same CAN IDs. Several sockets listening on 112 CAN-IDs, frames, etc. 144 IDs, supporting several open file descriptors and (de)multiplexing 162 (can_id) is used for arbitration on the CAN-bus. Therefore the CAN-IDs 164 network the CAN-IDs are mapped to be sent by a specific ECU. 171 CAN-IDs from the same CAN network interface. The SocketCAN core 175 requests the (range of) CAN-IDs from the SocketCAN core that are 177 CAN-IDs can be done for specific CAN interfaces or for all(!) known 617 where the CAN_INV_FILTER flag is set in order to notch single CAN IDs or 853 modules to subscribe needed CAN IDs (see chapter 3.1). [all …]
|
D | phonet.txt | 94 2^10 object IDs available, and can send and receive packets with any
|
D | dccp.txt | 29 It has a base protocol and pluggable congestion control IDs (CCIDs).
|
D | l2tp.txt | 231 addresses reversed. The tunnel and session IDs can be any non-zero
|
D | ixgb.txt | 197 # set mmrbc to 4k reads, modify only Intel 10GbE device IDs
|
D | bonding.txt | 1735 "learn" the VLAN IDs configured above it, and use those IDs to tag
|
/linux-4.1.27/Documentation/gpio/ |
D | consumer.txt | 311 connection IDs (names) for GPIOs, so it is necessary to use an additional 315 which, among other things, may be used to provide connection IDs for specific 319 connection IDs need to be provided by device drivers.
|
/linux-4.1.27/Documentation/ABI/stable/ |
D | firewire-cdev | 30 - Query node IDs of local node, root node, IRM, bus
|
/linux-4.1.27/Documentation/hid/ |
D | hiddev.txt | 155 use the relative IDs above to enumerate the valid IDs. The ioctl
|
D | hid-sensor.txt | 15 This specification describes many usage IDs, which describe the type of sensor
|
/linux-4.1.27/drivers/media/usb/dvb-usb/ |
D | Kconfig | 49 bool "Support faulty USB IDs" 52 Support for faulty USB IDs due to an invalid EEPROM on some Artec devices.
|
/linux-4.1.27/Documentation/isdn/ |
D | README.gigaset | 244 Call-IDs are numbers used to tag commands to, and responses from, the 247 mode"). Without Call-IDs (in Unimodem mode), only a very limited set of 252 connection to the base while Call-IDs are activated. As the Gigaset
|
/linux-4.1.27/Documentation/RCU/ |
D | arrayRCU.txt | 40 semaphore, message-queue, and shared-memory IDs to the data structure
|
D | RTFP.txt | 261 IDs for this if the ID space was large enough that overlapping 294 IDs for this if the ID space was large enough that overlapping
|
/linux-4.1.27/Documentation/frv/ |
D | features.txt | 270 (*) MMU Context IDs and Pinning 279 numbers, the kernel will pass context IDs from one task to another if
|
/linux-4.1.27/Documentation/sound/alsa/ |
D | hda_codec.txt | 38 needs to check the PCI subsystem IDs, so on. For non-PCI system, it 311 as a module parameter, and PCI subsystem IDs. If the matching entry
|
D | ALSA-Configuration.txt | 2294 VENDOR and DEVICE are PCI vendor and device IDs. They take
|
/linux-4.1.27/Documentation/hwmon/ |
D | smsc47b397 | 22 [1] And SMSC SCH5307-NS and SCH5317, which have different device IDs but are
|
/linux-4.1.27/Documentation/infiniband/ |
D | user_mad.txt | 99 Transaction IDs
|
/linux-4.1.27/Documentation/PCI/ |
D | pci.txt | 155 New PCI IDs may be added to a device driver pci_ids table at runtime 567 Do not add new device or vendor IDs to include/linux/pci_ids.h unless they 571 The device IDs are arbitrary hex numbers (vendor controlled) and normally used 574 Please DO submit new vendor/device IDs to http://pciids.sourceforge.net/.
|
/linux-4.1.27/Documentation/arm/OMAP/ |
D | omap_pm | 112 DSPBridge expresses target DSP performance levels in terms of OPP IDs.
|
/linux-4.1.27/Documentation/devicetree/bindings/iommu/ |
D | iommu.txt | 158 /* device has master IDs 23 and 24 in the IOMMU */
|
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/ |
D | macros.fuc | 141 // Kernel message IDs
|
/linux-4.1.27/Documentation/i2c/busses/ |
D | i2c-i801 | 132 The motherboard is identified using the subvendor and subdevice IDs of the
|
/linux-4.1.27/Documentation/scsi/ |
D | aic7xxx.txt | 51 8. Multiple Target IDs - Allows the controller to respond to selection 52 as a target on multiple SCSI IDs.
|
D | ChangeLog.megaraid | 169 1. Sorted out PCI IDs to remove megaraid support overlaps. 170 Based on the patch from Daniel, sorted out PCI IDs along with
|
D | ChangeLog.lpfc | 973 * Removed Volume Set Addressing handling on LUN IDs.
|
/linux-4.1.27/Documentation/input/ |
D | xpad.txt | 138 IDs see the xpad_device[] array[6].
|
D | input-programming.txt | 239 of the device. The bus IDs are defined in input.h. The vendor and device ids
|
D | sentelic.txt | 674 supported gesture IDs:
|
/linux-4.1.27/Documentation/dvb/ |
D | README.dvb-usb | 76 - new usb IDs (Compro, Artec)
|
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
D | fman.txt | 175 Super set of all hardware Port IDs available at FMan Reference
|
/linux-4.1.27/drivers/zorro/ |
D | zorro.ids | 2 # List of Zorro IDs
|
/linux-4.1.27/drivers/acpi/ |
D | Kconfig | 302 This driver supports ACPI Container and Module devices (IDs
|
/linux-4.1.27/drivers/usb/gadget/legacy/ |
D | Kconfig | 36 to tweak product and vendor IDs before host software knows about
|
/linux-4.1.27/drivers/scsi/aic7xxx/ |
D | aic79xx.reg | 1670 * SCSI Bus Initiator IDs 1719 * SCSI Bus Target IDs 1791 * Multiple Target IDs
|
/linux-4.1.27/Documentation/x86/ |
D | boot.txt | 55 pref_address fields. Added extended boot loader IDs. 363 For boot loader IDs above T = 0xD, write T = 0xE to this field and
|
/linux-4.1.27/drivers/net/usb/ |
D | Kconfig | 82 <petkan@users.sourceforge.net> vendor and device IDs.
|
/linux-4.1.27/arch/arm/boot/compressed/ |
D | head.S | 923 .word 0x00007000 @ ARM7 IDs
|
/linux-4.1.27/drivers/char/ |
D | Kconfig | 144 IDs).
|
/linux-4.1.27/drivers/mmc/host/ |
D | Kconfig | 103 ACPI Hardware IDs.
|
/linux-4.1.27/Documentation/cgroups/ |
D | cgroups.txt | 236 - cgroup.procs: list of thread group IDs in the cgroup. This list is
|
/linux-4.1.27/arch/x86/ |
D | Kconfig | 348 This allows 32-bit apic IDs (so it can support very large systems), 2357 PCI-IDs of several on-chip devices, so its a good dependency
|
/linux-4.1.27/Documentation/security/ |
D | keys.txt | 642 representing the IDs of all the keys to which it is subscribed. The user
|
/linux-4.1.27/init/ |
D | Kconfig | 415 in a new file format that also logs the process IDs of each
|
/linux-4.1.27/Documentation/sound/oss/ |
D | README.OSS | 921 and have different PnP IDs. There is no way to get two cards with the same
|