| /linux-4.1.27/Documentation/devicetree/bindings/usb/ |
| D | usb3503.txt | 11 '1' or '2' or '3' are available for this property to describe the port
13 Do not describe this property if all ports have to be enabled.
|
| D | omap-usb.txt | 11 - interface-type : This is a board specific setting to describe the type of
|
| /linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
| D | atmel,at91-pinctrl.txt | 23 - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
24 configured in this periph mode. All the periph and bank need to be describe.
109 name describe the pin function and group hierarchy.
115 4. The gpio controller must be describe in the pinctrl simple-bus.
|
| D | nvidia,tegra124-xusb-padctl.txt | 12 how to describe and reference PHYs in device trees.
|
| D | fsl,imx-pinctrl.txt | 53 name describe the pin function and group hierarchy.
|
| /linux-4.1.27/security/keys/ |
| D | user_defined.c | 35 .describe = user_describe,
55 .describe = user_describe,
|
| D | proc.c | 264 if (key->type->describe) in proc_keys_show()
265 key->type->describe(key, m); in proc_keys_show()
|
| D | big_key.c | 41 .describe = big_key_describe,
|
| D | request_key_auth.c | 41 .describe = request_key_auth_describe,
|
| D | keyring.c | 94 .describe = keyring_describe,
|
| D | trusted.c | 1103 .describe = user_describe,
|
| /linux-4.1.27/include/keys/ |
| D | asymmetric-subtype.h | 32 void (*describe)(const struct key *key, struct seq_file *m); member
|
| /linux-4.1.27/Documentation/input/ |
| D | event-codes.txt | 31 - Used to describe state changes of keyboards, buttons, or other key-like
35 - Used to describe relative axis value changes, e.g. moving the mouse 5 units
39 - Used to describe absolute axis value changes, e.g. describing the
43 - Used to describe miscellaneous input data that do not fit into other types.
46 - Used to describe binary state input switches.
152 EV_REL events describe relative changes in a property. For example, a mouse may
165 EV_ABS events describe absolute changes in a property. For example, a touchpad
171 - Used to describe the distance of a tool from an interaction surface. This
178 - Used to describe multitouch input events. Please see
183 EV_SW events describe stateful binary switches. For example, the SW_LID code is
|
| D | iforce-protocol.txt | 28 First, I describe effects that are sent by the device to the computer
|
| D | multi-touch-protocol.txt | 267 The orientation of the touching ellipse. The value should describe a signed
|
| /linux-4.1.27/Documentation/devicetree/bindings/ |
| D | graph.txt | 6 The hierarchical organisation of the device tree is well suited to describe
11 phandle properties pointing to other nodes to describe connections that
23 Here the ports describe data interfaces, and the links between them are
|
| D | marvell.txt | 6 system. In this section, we define device tree nodes to describe
105 shared register set, and the "ethernet" nodes describe ethernet
|
| D | xilinx.txt | 90 this case, the device should still describe the whole IP core with
|
| /linux-4.1.27/tools/power/cpupower/utils/ |
| D | version-gen.sh | 14 VN=$(git describe --abbrev=4 HEAD 2>/dev/null) &&
|
| /linux-4.1.27/tools/perf/util/ |
| D | PERF-VERSION-GEN | 20 TAG=$(git describe --abbrev=0 --match "v[0-9].[0-9]*" 2>/dev/null )
|
| /linux-4.1.27/Documentation/devicetree/bindings/pps/ |
| D | pps-gpio.txt | 3 These properties describe a PPS (pulse-per-second) signal connected to
|
| /linux-4.1.27/Documentation/devicetree/bindings/thermal/ |
| D | thermal.txt | 9 The target of device tree thermal descriptors is to describe only
14 There are five types of nodes involved to describe thermal bindings:
18 - trip points: describe key temperatures at which cooling is recommended. The
20 - cooling maps: used to describe links between trip points and cooling devices;
21 - thermal zones: used to describe thermal data within the hardware;
82 The trip node is a node to describe a point in the temperature domain
104 The cooling device maps node is a node to describe how cooling devices
152 Type: sub-node required to describe the thermal zone.
155 Type: sub-node map nodes, used to describe the relation between trips
|
| /linux-4.1.27/Documentation/devicetree/bindings/phy/ |
| D | qcom-ipq806x-sata-phy.txt | 4 SATA PHY nodes are defined to describe on-chip SATA Physical layer controllers.
|
| D | qcom-apq8064-sata-phy.txt | 4 SATA PHY nodes are defined to describe on-chip SATA Physical layer controllers.
|
| D | qcom-dwc3-usb-phy.txt | 4 DWC3 PHY nodes are defined to describe on-chip Synopsis Physical layer
|
| D | phy-miphy365x.txt | 17 nodes to describe the controller's topology. These nodes
|
| D | apm-xgene-phy.txt | 3 PHY nodes are defined to describe on-chip 15Gbps Multi-purpose PHY. Each
|
| D | phy-miphy28lp.txt | 15 nodes to describe the controller's topology. These nodes
|
| D | samsung-phy.txt | 87 SATA PHY nodes are defined to describe on-chip SATA Physical layer controllers.
|
| /linux-4.1.27/tools/testing/selftests/powerpc/ |
| D | Makefile | 9 GIT_VERSION = $(shell git describe --always --long --dirty || echo "unknown")
|
| /linux-4.1.27/Documentation/devicetree/bindings/sound/ |
| D | armada-370db-audio.txt | 4 These Device Tree bindings are used to describe the audio complex
|
| D | adi,adau1701.txt | 14 - adi,pll-mode-gpios: An array of two GPIO specs to describe the GPIOs
|
| D | wm8994.txt | 30 - #interrupt-cells: the number of cells to describe an IRQ, this should be 2.
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-format | 6 Attribute group to describe the magic bits that go into
|
| D | sysfs-devices-system-cpu | 19 Description: CPU topology files that describe kernel limits related to
78 Description: CPU topology files that describe a logical CPU's relationship
|
| /linux-4.1.27/crypto/asymmetric_keys/ |
| D | pkcs7_key_type.c | 80 .describe = user_describe,
|
| D | asymmetric_type.c | 242 subtype->describe(key, m); in asymmetric_key_describe()
351 .describe = asymmetric_key_describe,
|
| D | public_key.c | 125 .describe = public_key_describe,
|
| /linux-4.1.27/Documentation/devicetree/bindings/ata/ |
| D | fsl-sata.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
| D | exynos-sata.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
| D | qcom-sata.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
| D | sata_highbank.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
| D | apm-xgene.txt | 3 SATA host controller nodes are defined to describe on-chip Serial ATA
|
| D | ahci-platform.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
| /linux-4.1.27/include/linux/ |
| D | key-type.h | 131 void (*describe)(const struct key *key, struct seq_file *p); member
|
| /linux-4.1.27/Documentation/devicetree/bindings/mips/ |
| D | cpu_irq.txt | 6 With the irq_domain in place we can describe how the 8 IRQs are wired to the
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/ |
| D | brcm,bcmgenet.txt | 21 - phy-handle: See ethernet.txt file in the same directory; used to describe
26 voluntarily disabled, this property should be used to describe the "fixed link".
|
| D | fixed-link.txt | 6 binding allows to describe a "fixed link".
|
| D | apm-xgene-enet.txt | 3 Ethernet nodes are defined to describe on-chip ethernet interfaces in
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/omap/ |
| D | l4.txt | 3 These bindings describe the OMAP SoCs L4 interconnect bus.
|
| D | omap.txt | 3 OMAP is currently using a static file per SoC family to describe the
|
| /linux-4.1.27/Documentation/devicetree/bindings/dma/ |
| D | fsl-imx-dma.txt | 3 This document will only describe differences to the generic DMA Controller and
|
| D | apm-xgene-dma.txt | 3 DMA nodes are defined to describe on-chip DMA interfaces in
|
| D | shdma.txt | 5 the same configuration. To describe this topology we require all compatible
|
| /linux-4.1.27/Documentation/devicetree/bindings/panel/ |
| D | samsung,s6e8aa0.txt | 22 node should describe panel's video bus.
|
| D | samsung,ld9040.txt | 21 node should describe panel's video bus.
|
| /linux-4.1.27/Documentation/devicetree/bindings/mmc/ |
| D | tmio_mmc.txt | 6 describe hardware capabilities, known to them, or are obtained by them from
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | hwmon-kernel-api.txt | 12 This document does not describe what a hardware monitoring (hwmon) Driver or
13 Device is. It also does not describe the API which can be used by user space
|
| /linux-4.1.27/Documentation/devicetree/bindings/bus/ |
| D | simple-pm-bus.txt | 21 - #address-cells, #size-cells, ranges: Must describe the mapping between
|
| D | renesas,bsc.txt | 24 - #address-cells, #size-cells, ranges: Must describe the mapping between
|
| D | mvebu-mbus.txt | 84 In order to allow to describe valid and non-valid window entries, the
|
| /linux-4.1.27/Documentation/devicetree/bindings/video/ |
| D | ti,dra7-dss.txt | 21 can be used to describe the video PLLs:
|
| D | adi,adv7511.txt | 16 properties describe the input and map directly to the video input tables of the
|
| D | ti,omap-dss.txt | 32 The video ports are used to describe the connections to external hardware, like
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | kcopyd.txt | 15 To start a copy job, the user must set up io_region structures to describe
|
| D | dm-io.txt | 8 The user must set up an io_region structure to describe the desired location
|
| /linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
| D | tps65910.txt | 7 - #gpio-cells: number of cells to describe a GPIO, this should be 2.
11 - #interrupt-cells: the number of cells to describe an IRQ, this should be 2.
|
| D | arizona.txt | 21 - #interrupt-cells: the number of cells to describe an IRQ, this should be 2.
|
| /linux-4.1.27/Documentation/ |
| D | kernel-doc-nano-HOWTO.txt | 90 * @mem1: describe the first member of struct blah
91 * @mem2: describe the second member of struct blah,
97 The kernel-doc function comments describe each parameter to the
100 The kernel-doc data structure comments describe each structure member
|
| D | SubmittingPatches | 21 Many of these steps describe the default behavior of the git version
117 problem was spotted during code review, describe the impact you think
127 include numbers that back them up. But also describe non-obvious
133 Once the problem is established, describe what you are actually doing
134 about it in technical detail. It's important to describe the change
618 be copied to the permanent changelog to describe this patch.
638 describe the patch which that email contains. The "summary
654 characters, and it must describe both what the patch changes, as well
661 considered part of the summary phrase, but describe how the patch
707 which describe what has changed between the v1 and v2 version of the
[all …]
|
| D | media-framework.txt | 156 Entities have flags that describe the entity capabilities and state.
185 Pads have flags that describe the pad capabilities and state.
210 Links have flags that describe the link capabilities and state.
|
| D | HOWTO | 104 These files describe in explicit detail how to successfully create
370 As some of the above documents describe, the majority of the core kernel
468 - "Here is a patch that explains what I am trying to describe."
572 all time. It should describe the patch completely, containing:
|
| D | kasan.txt | 122 First sections describe slub object where bad access happened.
|
| D | oops-tracing.txt | 12 what you were doing. If it occurs repeatably try and describe how to recreate
|
| D | memory-hotplug.txt | 32 This text does not describe it.
|
| D | initrd.txt | 131 We'll describe the loopback device method:
|
| D | kobject.txt | 294 This structure is used to describe a particular type of kobject (or, more
|
| D | kernel-docs.txt | 214 of the Coda filesystem. This version document is meant to describe
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/samsung/ |
| D | interrupt-combiner.txt | 13 A single node in the device tree is used to describe the interrupt combiner
|
| /linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
| D | gpio-tz1090.txt | 49 - IRQ flags: value to describe edge and level triggering, as defined in
|
| D | gpio.txt | 30 The following example could be used to describe GPIO pins used as device enable
|
| /linux-4.1.27/Documentation/devicetree/bindings/pwm/ |
| D | pwm.txt | 26 The following example could be used to describe a PWM-based backlight
|
| /linux-4.1.27/fs/cifs/ |
| D | cifs_spnego.c | 69 .describe = user_describe,
|
| D | cifsacl.c | 86 .describe = user_describe,
|
| /linux-4.1.27/Documentation/devicetree/bindings/memory-controllers/fsl/ |
| D | ifc.txt | 25 Child device nodes describe the devices connected to IFC such as NOR (e.g.
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/spear/ |
| D | shirq.txt | 13 A single node in the device tree is used to describe the shared
|
| /linux-4.1.27/Documentation/ia64/ |
| D | aliasing.txt | 36 the EFI GetMemoryMap() interface. ACPI can also describe memory
42 space. Unfortunately, this table does not completely describe the
98 Since the EFI memory map does not describe MMIO on some
|
| D | efirtc.txt | 16 driver. We describe those calls as well the design of the driver in the
|
| /linux-4.1.27/Documentation/networking/ |
| D | switchdev.txt | 8 Lets describe a topology a bit. Imagine the following example:
|
| D | ipddp.txt | 39 I will briefly describe the operation of the tools, but you will
|
| D | dm9000.txt | 89 Extra platform data for the DM9000 can describe the IO bus width to the
|
| D | eql.txt | 46 Here I describe the general steps of getting a kernel up and working
|
| D | spider_net.txt | 23 describe the received data. This includes a pointer to a buffer
|
| D | ppp_generic.txt | 362 pointer/length pair which should describe a block of memory
|
| D | packet_mmap.txt | 106 Next I will describe PACKET_MMAP settings and its constraints,
|
| D | bonding.txt | 940 We will first describe the options for configuring bonding for
1098 settings described above, but does describe many of the other options.
1495 to describe network interface configuration, most notably Debian and it's
|
| /linux-4.1.27/Documentation/devicetree/bindings/ufs/ |
| D | ufshcd-pltfrm.txt | 3 UFSHC nodes are defined to describe on-chip UFS host controllers.
|
| /linux-4.1.27/Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 75 - iommus: A list of phandle and IOMMU specifier pairs that describe the IOMMU
95 can be useful to describe how children on the bus relate to the IOMMU if they
|
| /linux-4.1.27/Documentation/kbuild/ |
| D | headers_install.txt | 7 The linux kernel's exported header files describe the API for user space
|
| D | makefiles.txt | 988 See also chapter XXX-TODO that describe how kbuild supports
|
| /linux-4.1.27/net/dns_resolver/ |
| D | dns_key.c | 258 .describe = dns_resolver_describe,
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | raideng.txt | 3 RAID Engine nodes are defined to describe on-chip RAID accelerators. Each RAID
|
| D | board.txt | 96 - reg: should describe CPLD registers
|
| D | srio.txt | 51 Definition: A standard property. Utilized to describe the memory mapped
|
| D | mpc5200.txt | 17 maximum compatibility information; but still accurately describe the
41 function. For example, "fsl,mpc5200-spi" and "fsl,mpc5200-psc-spi" describe
|
| D | dcsr.txt | 7 may turn out to be inappropriate, or need additional properties to describe
16 defined DCSR Memory Map. Child nodes will describe the individual
|
| D | pamu.txt | 14 A standard property. Utilized to describe the memory mapped
|
| /linux-4.1.27/Documentation/fmc/ |
| D | API.txt | 23 The data structure that describe a device is detailed in *note FMC
|
| /linux-4.1.27/Documentation/ABI/stable/ |
| D | sysfs-class-ubi | 28 The /sys/class/ubi0, /sys/class/ubi1, etc directories describe
131 etc directories describe UBI volumes on UBI device X (volumes
|
| /linux-4.1.27/arch/powerpc/kernel/vdso64/ |
| D | sigtramp.S | 301 # Do we really need to describe the frame at this point? ie. will
|
| /linux-4.1.27/Documentation/devicetree/bindings/mipi/dsi/ |
| D | mipi-dsi-bus.txt | 12 set of properties that characterize the bus. Child nodes describe individual
|
| /linux-4.1.27/Documentation/devicetree/bindings/regulator/ |
| D | tps6586x.txt | 7 - #gpio-cells: number of cells to describe a GPIO
|
| /linux-4.1.27/Documentation/fb/ |
| D | api.txt | 53 Visuals describe how color information is encoded and assembled to create
54 macropixels. Types describe how macropixels are stored in memory. The following
257 to zero, and the red, blue, green and transp fields to describe the layout of
|
| /linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/ |
| D | interrupts.txt | 7 Nodes that describe devices which generate interrupts must contain an
|
| /linux-4.1.27/Documentation/scsi/ |
| D | osd.txt | 159 describe the IN/OUT buffers above, two BIOs for the data payload and up to five
167 layer, is to describe a vector of buffers that will be transferred to/from the
|
| /linux-4.1.27/Documentation/watchdog/ |
| D | watchdog-kernel-api.txt | 9 This document does not describe what a WatchDog Timer (WDT) Driver or Device is.
10 It also does not describe the API which can be used by user space to communicate
14 So what does this document describe? It describes the API that can be used by
|
| /linux-4.1.27/Documentation/crypto/ |
| D | asymmetric-keys.txt | 24 associated with the key and provides operations to describe and destroy it.
183 void (*describe)(const struct key *key, struct seq_file *m);
196 (1) describe().
|
| /linux-4.1.27/Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.txt | 22 describe these lines as:
|
| D | trivial-devices.txt | 6 describe some aspect of it, there needs to be a specific binding
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | emu10k1-jack.txt | 74 TODO: describe use of ld10k1/qlo10k1 in conjunction with JACK
|
| /linux-4.1.27/fs/nfs/ |
| D | nfs4idmap.c | 183 .describe = user_describe,
406 .describe = user_describe,
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra20-emc.txt | 14 Child device nodes describe the memory settings for different configurations and clock rates.
|
| /linux-4.1.27/Documentation/devicetree/bindings/clock/ |
| D | xgene.txt | 29 is not present, the reg property is assumed to describe
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | coresight.txt | 8 sink. Each CoreSight component device should use these properties to describe
|
| D | topology.txt | 10 are used to describe the layout of physical CPUs in the system:
58 subnodes describe the CPU topology.
|
| D | vexpress.txt | 100 different setups, the device tree should describe platform topology.
|
| D | cpus.txt | 5 The device tree allows to describe the layout of CPUs in a system through
|
| D | idle-states.txt | 222 subnodes describe the CPU idle states.
|
| /linux-4.1.27/Documentation/arm/ |
| D | Setup | 49 These two together describe the character size of the dummy console,
|
| /linux-4.1.27/Documentation/devicetree/bindings/spi/ |
| D | spi-bus.txt | 6 SPI master mode. This binding does not describe SPI controllers
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | qe.txt | 54 - ranges : Should be defined as specified in 1) to describe the
|
| /linux-4.1.27/arch/arm/nwfpe/ |
| D | ChangeLog | 75 * NOTES - Added file to describe known bugs/problems
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | dax.txt | 89 from a DAX file will fail as there are no 'struct page' to describe
|
| D | fiemap.txt | 58 If this flag is set, the extents returned will describe the inodes
98 The fe_flags field contains flags which describe the extent returned.
|
| D | xfs-self-describing-metadata.txt | 63 the type of metadata in the object, then the metadata doesn't describe itself
|
| D | coda.txt | 30 tem. This document version is meant to describe the current interface
173 describe the semantic invariants resulting from the calls.
|
| D | vfs.txt | 1022 automount directory to describe the automount target and the parent
|
| /linux-4.1.27/Documentation/phy/ |
| D | samsung-usb2.txt | 33 structures that describe particular SoCs.
|
| /linux-4.1.27/Documentation/sound/alsa/soc/ |
| D | codec.txt | 105 xtexts = pointer to array of strings that describe each setting
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | class.txt | 143 particular class type. Device interfaces describe these mechanisms.
|
| /linux-4.1.27/Documentation/gpio/ |
| D | board.txt | 14 describe its hardware layout. Currently, mappings can be defined through device
|
| /linux-4.1.27/tools/perf/Documentation/ |
| D | perf-list.txt | 76 If the Intel docs for a QM720 Core i7 describe an event as:
|
| D | perf-script-perl.txt | 169 The following sections describe the functions and variables available
|
| D | perf-script-python.txt | 564 The following sections describe the functions and variables available
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | freezer-subsystem.txt | 5 whole. The cgroup freezer uses cgroups to describe the set of tasks to
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | booting-without-of.txt | 226 running one. This method is what I will describe in more
513 First, let's quickly describe the device-tree concept before detailing
514 the storage format. This chapter does _not_ describe the detail of the
705 documentations. If you choose to describe a bus with the device-tree
1001 - ranges : Should be defined as specified in 1) to describe the
1210 describe the devices on the SOC. This will allow for the
1272 of 'interrupt specifier' values which describe the interrupt or
1340 reasonably describe. Thus, each device controlled in such a manner
1387 The dma-ranges property is used to describe the direct memory access (DMA)
|
| D | usage-model.txt | 25 is defined for how data should appear in the tree to describe typical
323 nodes that don't describe devices (although arguably memory could be
|
| /linux-4.1.27/arch/frv/kernel/ |
| D | head-mmu-fr451.S | 40 # describe the position and layout of the SDRAM controller registers
|
| D | head-uc-fr401.S | 39 # describe the position and layout of the SDRAM controller registers
|
| D | head-uc-fr555.S | 38 # describe the position and layout of the SDRAM controller registers
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 6.Followthrough | 56 thank them, and describe how you will answer their questions.
61 suggested change, describe it and justify your solution to the problem. If
|
| D | 5.Posting | 164 To that end, the summary line should describe the effects of and motivation
190 The tags mentioned above are used to describe how various developers have
|
| D | 4.Coding | 320 changelog. Log entries should describe the problem being solved, the form
|
| D | 2.Process | 141 In the hopes of reducing that frustration, this document will describe how
|
| /linux-4.1.27/net/rxrpc/ |
| D | ar-key.c | 48 .describe = rxrpc_describe,
64 .describe = rxrpc_describe,
|
| /linux-4.1.27/Documentation/hid/ |
| D | hid-transport.txt | 75 The terms "asynchronous" and "synchronous" in this document describe the
92 will describe them as two bi-directional channels as they have several
|
| D | hid-sensor.txt | 15 This specification describes many usage IDs, which describe the type of sensor
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | nested-vmx.txt | 17 We describe in much greater detail the theory behind the nested VMX feature,
|
| D | timekeeping.txt | 22 First, we will describe the various timekeeping hardware available, then
|
| D | api.txt | 1207 array 'entries'. If the number of entries is too low to describe the cpu
2728 to describe the cpu capabilities, an error (E2BIG) is returned. If the
|
| /linux-4.1.27/Documentation/arm/nwfpe/ |
| D | README.FPE | 4 In the following nomenclature is used to describe the floating point
|
| /linux-4.1.27/fs/cramfs/ |
| D | README | 4 These notes describe what mkcramfs generates. Kernel requirements are
|
| /linux-4.1.27/Documentation/i2c/ |
| D | slave-interface | 39 Each backend should come with separate documentation to describe its specific
|
| D | instantiating-devices | 87 ACPI can also describe I2C devices. There is special documentation for this
|
| /linux-4.1.27/fs/ |
| D | Kconfig.binfmt | 51 ELF core dump files describe each memory mapping of the crashed
|
| /linux-4.1.27/fs/jffs2/ |
| D | README.Locking | 5 This document attempts to describe the existing locking rules for
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | fscache.txt | 349 where the first set of columns before the '|' describe the object:
367 and the second set of columns describe the object's cookie, if present:
|
| D | backend-api.txt | 117 The fields that might be of use to the backend describe the object
|
| D | netfs-api.txt | 73 For example, kAFS (linux/fs/afs/) uses the following definitions to describe
|
| /linux-4.1.27/Documentation/arm64/ |
| D | arm-acpi.txt | 21 system. The purpose of this document is to describe the interaction between
52 -- Choosing a single interface to describe the abstraction between a platform
230 are always multiple ways to describe the same thing -- including device
|
| /linux-4.1.27/Documentation/pps/ |
| D | pps.txt | 114 pps_source_info_s which describe the capabilities of the driver).
|
| /linux-4.1.27/Documentation/acpi/ |
| D | enumeration.txt | 255 ACPI 5 introduced two new resources to describe GPIO connections: GpioIo
|
| D | namespace.txt | 29 includes various fixed-length entries that describe fixed ACPI features
|
| /linux-4.1.27/Documentation/s390/ |
| D | cds.txt | 79 The next chapters describe the functions other than do_IRQ() in more details.
92 The following chapters describe the I/O related interface routines the
|
| D | s390dbf.txt | 36 that the records which describe the origin of the exception are not
|
| /linux-4.1.27/security/keys/encrypted-keys/ |
| D | encrypted.c | 976 .describe = user_describe,
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | cxl.txt | 241 queues the WED may describe.
|
| D | pci_iov_resource_on_powernv.txt | 8 requirement. The first two sections describe the concepts of Partitionable
|
| /linux-4.1.27/Documentation/locking/ |
| D | rt-mutex-design.txt | 9 This document tries to describe the design of the rtmutex.c implementation.
10 It doesn't describe the reasons why rtmutex.c exists. For that please see
75 Here I explain some terminology that is used in this document to help describe
|
| /linux-4.1.27/Documentation/target/ |
| D | tcmu-design.txt | 153 entries in iov[] needed to describe either the Data-In or Data-Out
|
| /linux-4.1.27/Documentation/serial/ |
| D | driver | 385 uart_port structures describe the same port.
|
| /linux-4.1.27/Documentation/ioctl/ |
| D | cdrom.txt | 8 This document attempts to describe the ioctl(2) calls supported by
|
| D | hdio.txt | 8 This document attempts to describe the ioctl(2) calls supported by
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | cdrom-standard.tex | 104 describe. The implementation of the \UCD\ is in the file \cdromc. This
265 $cdrom_device_ops$ because they describe the capability of the {\em
311 because they describe properties of the drive, which don't change after
|
| /linux-4.1.27/Documentation/security/ |
| D | keys.txt | 674 The payload and plen arguments describe the payload data as for add_key().
676 The payload_iov and ioc arguments describe the payload data in an iovec
1299 (*) void (*describe)(const struct key *key, struct seq_file *p);
|
| D | Smack.txt | 403 describe access modes:
|
| /linux-4.1.27/Documentation/RCU/ |
| D | checklist.txt | 35 If you choose #b, be prepared to describe how you have handled
|
| D | trace.txt | 7 The following sections describe the debugfs files and formats, first
|
| D | RTFP.txt | 71 before freeing blocks awaiting deferred free. Jacobson did not describe
323 of virtual address. Does not describe how one determines that
|
| D | whatisRCU.txt | 17 assumption that there is "one true way" to describe RCU. Instead,
|
| /linux-4.1.27/Documentation/vm/ |
| D | numa_memory_policy.txt | 8 document attempts to describe the concepts and APIs of the 2.6 memory policy
|
| /linux-4.1.27/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 293 This is referred to as the "enumerated" tag type. It is used to describe
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 984 The sections below describe this in more detail.
1475 To use this transport, you need to describe the virtual network device
1638 isn't acceptable for some reason. The rest of the arguments describe
2773 init and cleanup addresses once in a while, as describe below. Now
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | vivid.txt | 516 Different devices support different controls. The sections below will describe
|
| /linux-4.1.27/Documentation/power/ |
| D | pci.txt | 78 configuration space. This field is used to describe and control the standard
|
| /linux-4.1.27/Documentation/block/ |
| D | biodoc.txt | 415 of <page, offset, len> to describe the i/o buffer, and has various other
|
| /linux-4.1.27/arch/arm/ |
| D | Kconfig | 1346 affinity between processors which is then used to describe the cpu
|
| /linux-4.1.27/drivers/staging/speakup/ |
| D | spkguide.txt | 1114 briefly describe the use of these tools.
|