| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-bus-bcma | 14 There are a few types of BCMA cores, they can be identified by
30 Each BCMA core is identified by few fields, including class it
|
| D | sysfs-devices-platform-docg3 | 14 Users: None identified so far.
34 Users: None identified so far.
|
| D | sysfs-bus-rpmsg | 7 processor. Channels are identified with a (textual) name,
59 processor. Channels are identified by a textual name (see
|
| D | sysfs-gpio | 13 GPIOs are identified as they are inside the kernel, using integers in
|
| D | sysfs-bus-event_source-devices-events | 26 "raw code" for the perf event identified by the file's
|
| D | sysfs-devices-system-cpu | 34 present: cpus that have been identified as being present in
|
| /linux-4.1.27/drivers/staging/i2o/ |
| D | README.ioctl | 131 This function posts a UtilParamsSet message to the device identified
172 This function posts a UtilParamsGet message to the device identified
212 to the iop identified by sw->iop. The DownloadFlags, SwID, SwType
252 This function uploads a software fragment from the IOP identified
294 This function removes software from the IOP identified by sw->iop.
321 identified by iop. This message indicates that the current
351 This function posts an UtilConfigDialog message to the device identified
|
| /linux-4.1.27/Documentation/devicetree/bindings/regulator/ |
| D | 88pm860x.txt | 7 device. Each sub-node is identified using the regulator-compatible
|
| D | 88pm800.txt | 7 device. Each sub-node is identified using the node's name (or the deprecated
|
| D | isl9305.txt | 8 device. Each sub-node is identified using the node's name, with valid
|
| D | da9211.txt | 8 device. Each sub-node is identified using the node's name, with valid
|
| D | max8907.txt | 15 device. Each sub-node is identified using the node's name (or the deprecated
|
| D | tps6586x.txt | 10 device. Each sub-node is identified using the node's name (or the deprecated
|
| D | tps65090.txt | 8 device. Each sub-node is identified using the node's name, with valid
|
| /linux-4.1.27/Documentation/devicetree/bindings/dma/ |
| D | ste-coh901318.txt | 11 COH 901 318 are simple and identified by a single number
|
| D | renesas,rcar-dmac.txt | 8 Each DMA client is connected to one dedicated port of the DMAC, identified by
|
| /linux-4.1.27/Documentation/devicetree/bindings/metag/ |
| D | meta.txt | 19 Clocks are identified by name. Valid clocks are:
|
| /linux-4.1.27/Documentation/devicetree/bindings/hwmon/ |
| D | ltc2978.txt | 15 the device. Each sub-node is identified using the node's name, with valid
|
| /linux-4.1.27/drivers/bcma/ |
| D | README | 18 16 devices identified by Broadcom specific fields: manufacturer, id, revision
|
| /linux-4.1.27/Documentation/networking/ |
| D | i40evf.txt | 45 If an issue is identified with the released source code on the supported
|
| D | ixgbevf.txt | 50 If an issue is identified with the released source code on the supported
|
| D | xfrm_sync.txt | 26 The identified items that need to be synchronized are:
55 The unique SA is identified by the combination of xfrm_usersa_id,
|
| D | igbvf.txt | 78 If an issue is identified with the released source code on the supported
|
| D | i40e.txt | 115 If an issue is identified with the released source code on the supported
|
| D | igb.txt | 127 If an issue is identified with the released source code on the supported
|
| D | cxgb.txt | 203 These issues have been identified during testing. The following information
270 Corruption" bug identified by AMD while using a 133Mhz PCI-X card on the
|
| D | e100.txt | 181 If an issue is identified with the released source code on the supported
|
| D | e1000e.txt | 310 If an issue is identified with the released source code on the supported
|
| D | ixgbe.txt | 347 If an issue is identified with the released source code on the supported
|
| D | ixgb.txt | 431 If an issue is identified with the released source code on the supported
|
| D | e1000.txt | 459 If an issue is identified with the released source code on the supported
|
| D | can.txt | 955 controller and have to be identified as not feasible in a multi-user
|
| /linux-4.1.27/Documentation/devicetree/bindings/mtd/ |
| D | jedec,spi-nor.txt | 12 be identified by the JEDEC READ ID opcode (0x9F).
|
| /linux-4.1.27/arch/m68k/fpsp040/ |
| D | README | 28 and that such modified versions are clearly identified as such.
|
| /linux-4.1.27/drivers/net/caif/ |
| D | Kconfig | 13 identified as N_CAIF. When this ldisc is opened from user space
|
| /linux-4.1.27/Documentation/i2c/busses/ |
| D | i2c-ali1535 | 27 can be identified by comparing this driver to the i2c-ali15x3 driver. For
|
| D | i2c-i801 | 132 The motherboard is identified using the subvendor and subdevice IDs of the
|
| /linux-4.1.27/Documentation/devicetree/bindings/leds/ |
| D | common.txt | 15 outputs are identified by the numbers that must be defined
|
| /linux-4.1.27/drivers/staging/iio/Documentation/ |
| D | inkernel.txt | 42 by calling iio_channel_get(). The correct channel is identified by:
|
| /linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
| D | qcom-rpm.txt | 53 Regulator nodes are identified by their compatible:
141 sub-node is identified using the node's name, with valid values listed for each
|
| /linux-4.1.27/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 8 Each error log is identified by a unique ID and will
|
| /linux-4.1.27/Documentation/virtual/kvm/devices/ |
| D | xics.txt | 11 sources, each identified by a 20-bit source number, and a set of
|
| /linux-4.1.27/Documentation/filesystems/nfs/ |
| D | Exporting | 135 in the directory identified by the parent dentry, which leads to the
136 object identified by the child dentry. If no get_name function is
|
| D | nfs41-server.txt | 33 The OPTIONAL features identified and their abbreviations are as follows:
|
| /linux-4.1.27/arch/m68k/ifpsp060/ |
| D | README | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | MISC | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | CHANGES | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | ilsp.doc | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | os.S | 25 |redistributed versions, and that such modified versions are clearly identified as such.
|
| D | iskeleton.S | 25 |redistributed versions, and that such modified versions are clearly identified as such.
|
| D | fplsp.doc | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | isp.doc | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | TEST.DOC | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | fpsp.doc | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | fskeleton.S | 25 |redistributed versions, and that such modified versions are clearly identified as such.
|
| /linux-4.1.27/arch/arm/boot/dts/ |
| D | kirkwood-b3.dts | 103 * Not yet identified what it is, maybe the eeprom
|
| /linux-4.1.27/Documentation/usb/ |
| D | functionfs.txt | 36 each FunctionFS instance is identified by the device name used
|
| D | hotplug.txt | 92 specific criteria are identified by bits set in "match_flags", paired
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | coda.txt | 606 and Venus will search the directory identified by cfs_lookup_in.VFid.
649 DDeessccrriippttiioonn This call returns the attributes of the file identified by
718 DDeessccrriippttiioonn Verify if access to the object identified by VFid for
760 The file will be created in the directory identified by VFid, its name
852 identified by destFid with name tname. The source must reside in the
881 directory identified by VFid and named tname. It should point to the
912 identified by VFid.
941 identified by VFid.
975 identified by VFid into the buffer data. The buffer data must be able
1007 DDeessccrriippttiioonn This request asks Venus to place the file identified by
[all …]
|
| D | ext3.txt | 33 identified through either its new major/minor numbers
|
| D | squashfs.txt | 115 boundaries, therefore inodes overlap compressed blocks. Inodes are identified
|
| D | f2fs.txt | 65 2. It loads parent index structures of all the data in the victim identified by
|
| D | ext4.txt | 151 identified through either its new major/minor numbers
|
| /linux-4.1.27/Documentation/vm/ |
| D | zswap.txt | 27 been identified in prior community discussions.
|
| /linux-4.1.27/Documentation/ |
| D | cputopology.txt | 82 present: CPUs that have been identified as being present in the
|
| D | media-framework.txt | 132 Entities are identified by a unique positive integer ID. Drivers can provide an
181 Pads are identified by their entity and their 0-based index in the pads array.
|
| D | coccinelle.txt | 213 identified.
|
| D | rpmsg.txt | 50 rpmsg devices are called channels). Channels are identified by a textual name
|
| D | kmemcheck.txt | 604 we do a memcpy() on the struct. This means that we have identified a false
|
| D | pinctrl.txt | 772 This function will pass in the affected GPIO range identified by the pin
|
| /linux-4.1.27/Documentation/acpi/ |
| D | gpio-properties.txt | 66 once it has identified the device. Having done that, it can simply assign names
|
| D | namespace.txt | 80 is a hierarchy of objects identified by names and paths.
|
| /linux-4.1.27/Documentation/arm/Atmel/ |
| D | README | 123 that they can be identified easily. Note that some files are historical exceptions
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | class.txt | 8 device. The following device classes have been identified:
|
| D | devres.txt | 168 Each group is identified by void *id. It can either be explicitly
|
| /linux-4.1.27/Documentation/power/ |
| D | pm_qos_interface.txt | 40 Will insert an element into the list for that identified PM QoS class with the
111 Will insert an element into the list for that identified device with the
|
| D | pci.txt | 225 may be identified later). The GPEs used in such situations are referred to as
250 read by the interrupt handler allowing the device to be identified. [PME
404 identified.
|
| /linux-4.1.27/Documentation/security/ |
| D | keys-trusted-encrypted.txt | 58 application specific, which is identified by 'format'.
|
| D | Smack.txt | 317 violate an aspect of the system security policy, as identified by
|
| /linux-4.1.27/Documentation/devicetree/bindings/mmc/ |
| D | mmc.txt | 85 The subnodes are identified by the standard 'reg' property.
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | w83792d | 105 different between C and B version. C or B version can be identified
|
| /linux-4.1.27/Documentation/power/powercap/ |
| D | powercap.txt | 160 part of the system represented by that zone to be identified.
|
| /linux-4.1.27/Documentation/fmc/ |
| D | mezzanine.txt | 56 identified by an array of cores (it matches if all of the cores are
|
| /linux-4.1.27/drivers/scsi/ |
| D | aha152x.c | 315 identified = 0x0004, /* IDENTIFY was sent */ enumerator
1871 CURRENT_SC->SCp.phase |= identified; in msgo_run()
2456 (ptr->SCp.phase & identified) ? "identified|" : "", in show_command()
2515 if (ptr->SCp.phase & identified) in get_command()
|
| /linux-4.1.27/Documentation/devicetree/bindings/pci/ |
| D | mvebu-pci.txt | 34 of the internal register window (as identified by MBUS_ID(0xf0,
|
| /linux-4.1.27/Documentation/devicetree/bindings/bus/ |
| D | mvebu-mbus.txt | 144 Since each window is identified by its target ID and attribute ID there's
|
| /linux-4.1.27/Documentation/input/ |
| D | multi-touch-protocol.txt | 58 identified contact, and use that slot to propagate changes for the contact.
215 may be used to track identified contacts over time [5].
|
| D | alps.txt | 35 If the E6 report is successful, the touchpad model is identified using the "E7
|
| D | elantech.txt | 785 No special registers have been identified.
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | uvcvideo.txt | 178 This ioctl queries a UVC XU control identified by its extension unit ID
|
| /linux-4.1.27/drivers/mtd/chips/ |
| D | Kconfig | 22 CFI-targeted flash drivers for any chips which are identified which
|
| /linux-4.1.27/Documentation/scsi/ |
| D | FlashPoint.txt | 85 After this problem was identified, BusLogic contacted its major OEM
|
| D | ChangeLog.megaraid_sas | 622 i. New template defined to represent each family of controllers (identified by processor used).
|
| D | scsi_mid_low_api.txt | 1248 on a host. Scsi devices connected to a host are uniquely identified by a
|
| D | ChangeLog.1992-1997 | 493 Print hosts after we have identified all of them. Use info()
|
| /linux-4.1.27/Documentation/timers/ |
| D | hrtimers.txt | 44 identified as "timeouts". Such timeouts are usually set up to cover
|
| D | highres.txt | 222 new timer whose expiry time is before the time which was identified as the
|
| /linux-4.1.27/Documentation/gpio/ |
| D | driver.txt | 17 Inside a GPIO driver, individual GPIOs are identified by their hardware number,
|
| D | consumer.txt | 26 With the descriptor-based interface, GPIOs are identified with an opaque,
|
| D | gpio-legacy.txt | 92 GPIOs are identified by unsigned integers in the range 0..MAX_INT. That
|
| /linux-4.1.27/Documentation/i2c/ |
| D | instantiating-devices | 167 manufacturer and device ID registers, so they can be identified by
|
| /linux-4.1.27/Documentation/trace/ |
| D | tracepoint-analysis.txt | 213 can be identified
|
| /linux-4.1.27/Documentation/ide/ |
| D | ide.txt | 114 Such drives will be identified at boot time, just like a hard disk.
|
| /linux-4.1.27/Documentation/video4linux/bttv/ |
| D | Cards | 127 1) 878 cards can be identified by PCI Subsystem-ID:
145 1) Some models can be identified by PCI subsystem ID:
|
| /linux-4.1.27/drivers/ide/ |
| D | Kconfig | 127 If you say Y here, the CD-ROM drive will be identified at boot time
158 If you say Y here, the tape drive will be identified at boot time
|
| /linux-4.1.27/arch/m68k/ifpsp060/src/ |
| D | isp.S | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | ilsp.S | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | ftest.S | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | pfpsp.S | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | itest.S | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | fpsp.S | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| D | fplsp.S | 25 redistributed versions, and that such modified versions are clearly identified as such.
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | idle-states.txt | 17 power states an ARM CPU can be put into are identified by the following list:
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | usage-model.txt | 217 After the board has been identified, and after the early configuration data
|
| /linux-4.1.27/Documentation/s390/ |
| D | cds.txt | 114 single device is uniquely identified to the system by a so called subchannel,
|
| /linux-4.1.27/Documentation/kbuild/ |
| D | makefiles.txt | 658 qconf.cc - identified by $(qconf-cxxobjs).
1266 A subdirectory is identified by a trailing '/' which
|
| /linux-4.1.27/tools/power/cpupower/po/ |
| D | de.po | 245 #. P state changes via MSR are identified via cpuid 80000007
|
| D | cs.po | 249 #. P state changes via MSR are identified via cpuid 80000007
|
| D | it.po | 244 #. P state changes via MSR are identified via cpuid 80000007
|
| D | fr.po | 244 #. P state changes via MSR are identified via cpuid 80000007
|
| D | pt.po | 243 #. P state changes via MSR are identified via cpuid 80000007
|
| /linux-4.1.27/drivers/mmc/host/ |
| D | Kconfig | 102 identified by ACPI Compatibility ID PNP0D40 or specific
|
| /linux-4.1.27/sound/pci/ |
| D | Kconfig | 300 can be identified in the quirks list.
|
| /linux-4.1.27/drivers/scsi/aic7xxx/ |
| D | aic7xxx.seq | 486 * we properly identified ourselves.
1627 * If we are identified and have successfully sent the CDB,
|
| D | aic79xx.seq | 1190 * If we are identified and have successfully sent the CDB,
1333 * no identified transaction exists should a
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | cgroups.txt | 548 identified by the passed cgroup object having a NULL parent (since
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | cdrom-standard.tex | 865 commands can be identified by the underscores in their names.
|