| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | sodaville.txt | 13 The interrupt specifier consists of two cells encoded as follows:
15 - <2nd cell>: The level-sense information, encoded as follows:
|
| /linux-4.4.14/Documentation/RCU/ |
| D | lockdep-splat.txt | 63 Line 2776 of block/cfq-iosched.c in v3.0-rc5 is as follows:
73 which would permit us to invoke rcu_dereference_protected as follows:
88 add rcu_read_lock() and rcu_read_unlock() as follows:
105 by rcu_access_pointer() as follows:
|
| D | rcuref.txt | 45 in this scenario as follows:
80 as follows:
118 delete(), so that el_free() can be subsumed into delete as follows:
|
| D | listRCU.txt | 27 implementation of audit_filter_task() might be as follows:
51 This means that RCU can be easily applied to the read side, as follows:
76 lock might be used as follows for deletion and insertion:
162 follows (presumably, the field_count is only permitted to decrease,
190 RCU ("read-copy update") its name. The RCU code is as follows:
240 as follows:
271 flag under the spinlock as follows:
|
| D | trace.txt | 27 of "cat rcu/rcutorture" looks as follows:
57 The output of "cat rcu/rcu_preempt/rcudata" looks as follows:
69 The fields are as follows:
206 as follows:
238 The output of "cat rcu/rcu_preempt/rcuexp" looks as follows:
242 These fields are as follows:
261 The output of "cat rcu/rcu_preempt/rcugp" looks as follows:
265 These fields are taken from the rcu_state structure, and are as follows:
289 The output of "cat rcu/rcu_preempt/rcuhier" looks as follows:
295 The fields are as follows:
[all …]
|
| D | rcubarrier.txt | 35 context might then be as follows:
41 IRQ context. The function p_callback() might be defined as follows:
80 Pseudo-code using rcu_barrier() is as follows:
100 as follows:
204 The original code for rcu_barrier() was as follows:
230 to post an RCU callback, as follows:
252 reaches zero, as follows:
|
| D | whatisRCU.txt | 20 different paths, as follows:
246 this local variable, for example as follows:
324 used as follows:
341 These three mechanisms are used as follows:
451 The call_rcu() API is as follows:
459 have an rcu_head structure added, perhaps as follows:
468 The foo_update_a() function might then be written as follows:
498 The foo_reclaim() function might appear as follows:
|
| D | torture.txt | 167 torture_type The type of RCU to test, with string values as follows:
198 The statistics output is as follows:
217 The entries are as follows:
|
| D | lockdep.txt | 85 code, it could instead be written as follows:
|
| D | NMI-RCU.txt | 85 follows:
|
| D | arrayRCU.txt | 5 also be used to protect arrays. Three situations are as follows:
|
| /linux-4.4.14/Documentation/pcmcia/ |
| D | locking.txt | 60 The "main" struct pcmcia_socket is protected as follows (read-only fields
99 The "main" struct pcmcia_device is protected as follows (read-only fields
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | pops_clicks.txt | 22 shutdown and follows some basic rules:-
36 ADC until all the pops have occurred. This follows similar power rules to
|
| D | codec.txt | 80 Defines a single control as follows:-
100 Defines an single enumerated control as follows:-
|
| D | clocking.txt | 31 Bit Clock can be generated as follows:-
|
| D | DPCM.txt | 89 The audio driver processes this as follows :-
142 FE DAI links are defined as follows :-
170 The BE DAIs are configured as follows :-
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
| D | mux.txt | 15 results in programming the register as follows:
24 "index-starts-at-one" modified the scheme as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | img,meta-intc.txt | 30 Interrupt specifiers consists of 2 cells encoded as follows:
35 encoded as follows:
|
| D | img,pdc-intc.txt | 32 Interrupt specifiers consists of 2 cells encoded as follows:
39 flags as follows (only 4 valid for peripheral interrupts):
|
| D | open-pic.txt | 40 follows:
44 - <2nd-cell>: The level-sense information, encoded as follows:
|
| D | brcm,bcm2836-l1-intc.txt | 20 The interrupt sources are as follows:
|
| D | cirrus,clps711x-intc.txt | 11 The interrupt sources are as follows:
|
| D | brcm,bcm2835-armctrl-ic.txt | 34 The interrupt sources are as follows:
|
| D | arm,gic-v3.txt | 22 The 3rd cell is the flags, encoded as follows:
|
| D | arm,gic.txt | 35 The 3rd cell is the flags, encoded as follows:
|
| /linux-4.4.14/drivers/usb/misc/ |
| D | ftdi-elan.c | 119 int follows; member
382 command->follows = 0; in ftdi_elan_flush_targets()
404 command->follows = 0; in ftdi_elan_flush_targets()
440 command->follows = 0; in ftdi_elan_cancel_targets()
747 int F = command->follows; in fill_buffer_with_all_queued_commands()
772 total_size += 5 + command->follows; in ftdi_elan_total_command_size()
1258 command->follows = 4; in ftdi_elan_write_reg()
1290 command->follows = 4; in ftdi_elan_write_config()
1322 command->follows = 4; in ftdi_elan_write_pcimem()
1368 command->follows = 0; in ftdi_elan_read_reg()
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | ndfc.txt | 12 - partition(s) - follows the OF MTD standard for partitions
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-devices-sun | 7 Configuration and Power Interface Specification as follows:
|
| D | sysfs-driver-intel-rapid-start | 5 Description: An integer representing a set of wakeup events as follows:
|
| D | sysfs-driver-hid-logitech-lg4ff | 14 mode is listed as follows:
|
| D | sysfs-firmware-memmap | 22 The structure is as follows: Under /sys/firmware/memmap there
|
| D | sysfs-driver-hid-roccat-kone | 96 The values map to the weights as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/crypto/ |
| D | fsl-sec2.txt | 18 EU_SEL0 field documentation, i.e. as follows:
36 field documentation, i.e. as follows:
|
| /linux-4.4.14/Documentation/i2c/busses/ |
| D | i2c-amd8111 | 9 follows.
|
| /linux-4.4.14/Documentation/gpio/ |
| D | board.txt | 136 A lookup table can then be defined as follows, with an empty entry defining its
150 And the table can be added by the board code as follows:
154 The driver controlling "foo.0" will then be able to obtain its GPIOs as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic.txt | 83 follows:
96 <2nd-cell> level-sense information, encoded as follows:
141 The type-specific cell is encoded as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/phy/ |
| D | samsung-phy.txt | 10 the PHY specifier identifies the PHY and its meaning is as follows:
52 and Exynos 4212) it is as follows:
157 PHY id, which is interpreted as follows:
|
| /linux-4.4.14/Documentation/cma/ |
| D | debugfs.txt | 9 The structure of the files created under that directory is as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/hsi/ |
| D | nokia-modem.txt | 3 The Nokia modem HSI client follows the common HSI client binding
|
| /linux-4.4.14/scripts/coccinelle/misc/ |
| D | bugon.cocci | 3 //# This makes an effort to find cases where BUG() follows an if
|
| /linux-4.4.14/fs/ceph/ |
| D | caps.c | 998 u64 follows, bool inline_data) in send_cap_msg() argument
1011 mseq, follows, size, max_size, in send_cap_msg()
1037 fc->snap_follows = cpu_to_le64(follows); in send_cap_msg()
1117 u64 seq, issue_seq, mseq, time_warp_seq, follows; in __send_cap() local
1171 follows = flushing ? ci->i_head_snapc->seq : 0; in __send_cap()
1203 follows, inline_data); in __send_cap()
1251 if (capsnap->follows < next_follows) in __ceph_flush_snaps()
1317 inode, capsnap, capsnap->follows, capsnap->flush_tid); in __ceph_flush_snaps()
1326 capsnap->follows, capsnap->inline_data); in __ceph_flush_snaps()
1328 next_follows = capsnap->follows + 1; in __ceph_flush_snaps()
[all …]
|
| D | super.h | 160 u64 follows, flush_tid; member
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | powr1220 | 27 The input naming convention is as follows:
|
| D | ds620 | 24 The thermostat function works as follows: When configured via platform_data
|
| D | max1668 | 24 entries as follows:
|
| D | k8temp | 28 Mapping of /sys files is as follows:
|
| D | acpi_power_meter | 47 follows:
|
| D | vt1211 | 81 follows. And this is of course totally dependent on the actual board
145 The equation for the thermistor is as follows (google it if you want to know
|
| D | hwmon-kernel-api.txt | 98 which is defined as follows.
|
| D | dme1737 | 70 millivolts and don't need scaling. The voltage inputs are mapped as follows
121 need any user-space adjustments. The temperature inputs are mapped as follows
|
| D | pmbus | 75 Emerson DS1200 power modules might look as follows.
|
| D | ds1621 | 131 values defined in the datasheet as follows:
|
| D | w83627ehf | 88 follows:
|
| D | asc7621 | 48 that follows Intel's specs.
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/tilcdc/ |
| D | tilcdc.txt | 24 binding follows Documentation/devicetree/bindings/graph.txt and
|
| /linux-4.4.14/Documentation/fb/ |
| D | ep93xx-fb.txt | 15 mode for it as follows:
90 obtained as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/ |
| D | pincfg.txt | 9 - dir : direction of the pin, should encode as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | sun4i-dma.txt | 3 This driver follows the generic DMA bindings defined in dma.txt.
|
| D | sun6i-dma.txt | 3 This driver follows the generic DMA bindings defined in dma.txt.
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | ste-u300-syscon-clock.txt | 17 The available clocks per type are as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | samsung-sxgbe.txt | 9 These interrupts are ordered by fixed and follows variable
|
| /linux-4.4.14/Documentation/devicetree/bindings/bus/ |
| D | simple-pm-bus.txt | 12 While "simple-pm-bus" follows the "simple-bus" set of properties, as specified
|
| /linux-4.4.14/Documentation/timers/ |
| D | hpet.txt | 3 The High Precision Event Timer (HPET) hardware follows a specification
|
| D | timer_stats.txt | 71 timer will appear as follows
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | changesets.txt | 13 The sequence of a changeset is as follows.
|
| /linux-4.4.14/drivers/usb/class/ |
| D | Kconfig | 43 Say Y here if you want to connect a USB device that follows
|
| /linux-4.4.14/tools/virtio/virtio-trace/ |
| D | README | 11 The trace agent operates as follows:
43 of CPUs and a control path, so FIFO (named pipe) should be created as follows:
|
| /linux-4.4.14/Documentation/input/ |
| D | amijoy.txt | 74 Register bits are as follows:
103 Joystick switch closures can be deciphered as follows:
|
| D | userio.txt | 26 The struct used for sending commands to /dev/userio is as follows:
|
| D | ff.txt | 198 and meanings of the fields of the event are as follows:
|
| /linux-4.4.14/Documentation/early-userspace/ |
| D | buffer-format.txt | 47 The structure of the cpio_header is as follows (all fields contain
93 should be set to zero to indicate no data section follows. If data is
|
| /linux-4.4.14/Documentation/networking/ |
| D | dm9000.txt | 23 The minimum set of resources attached to the platform device are as follows:
93 The flags for the platform data .flags field are as follows:
|
| D | ipv6.txt | 12 The parameters are as follows:
|
| D | mac80211-injection.txt | 43 The ieee80211 header follows immediately afterwards, looking for example like
|
| D | phonet.txt | 24 Phonet packets have a common header as follows:
110 This protocol follows the SOCK_DGRAM connection-less semantics.
|
| D | regulatory.txt | 99 domain value to a specific alpha2 as follows:
111 as follows:
|
| D | netconsole.txt | 143 param follows.
163 chunk, the 2nd chunk." may be split as follows.
|
| D | PLIP.txt | 135 two DB-25 male connectors symmetrically connected as follows:
165 The cable for this transfer mode should be constructed as follows:
|
| D | tlan.txt | 85 The bits in the third byte are assigned as follows:
|
| D | netlink_mmap.txt | 85 The ring parameters used for setting up the ring are defined as follows:
130 The frame header is defined as follows:
|
| D | spider_net.txt | 37 buffers, and marks them "full". The OS follows up, taking the full
60 The head pointer (somewhat mis-named) follows after the tail pointer.
|
| D | iphase.txt | 14 The features and limitations of this driver are as follows:
|
| D | altera_tse.txt | 126 as follows:
133 The statistics supported by the TSE and the device driver are as follows:
|
| D | operstates.txt | 110 follows:
|
| D | e100.txt | 75 default. The ethtool utility can be used as follows to force speed/duplex.
|
| D | fib_trie.txt | 83 level compression. This part follows the original paper pretty closely
|
| D | xfrm_sync.txt | 164 seen, then an odd behavior is seen as follows:
|
| D | de4x5.txt | 32 16M of data to a DECstation 5000/200 as follows:
|
| D | e1000.txt | 157 follows:
348 For copper-based boards, the keywords interact as follows:
|
| D | dl2k.txt | 134 The commands to unload a driver are as follows:
|
| D | dccp.txt | 57 be formatted using a cmsg(3) message header filled in as follows:
|
| /linux-4.4.14/Documentation/arm/SPEAr/ |
| D | overview.txt | 14 Hierarchy in SPEAr is as follows:
|
| /linux-4.4.14/drivers/spi/ |
| D | spi-s3c24xx-fiq.S | 24 @ entry to these routines is as follows, with the register names
|
| /linux-4.4.14/Documentation/leds/ |
| D | leds-blinkm.txt | 17 The registration follows the scheme:
|
| /linux-4.4.14/Documentation/kdump/ |
| D | kdump.txt | 84 3) Unpack the tarball with the tar command, as follows:
88 4) Change to the kexec-tools directory, as follows:
92 5) Configure the package, as follows:
96 6) Compile the package, as follows:
100 7) Install the package, as follows:
141 .config file itself to ensure that sysfs is turned on, as follows:
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | cpqarray.txt | 54 as follows:
|
| D | ramdisk.txt | 68 as follows. The low 11 bits (0 -> 10) specify an offset (in 1 k blocks) of up
|
| D | cciss.txt | 50 is as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/i2c/ |
| D | adv7604.txt | 25 are numbered as follows.
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/ |
| D | cros-ec-keyb.txt | 8 This binding is based on matrix-keymap.txt and extends/modifies it as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | da9062.txt | 40 The component follows the standard regulator framework and the bindings
|
| D | qcom-pm8xxx.txt | 39 encoded as follows:
|
| D | da9063.txt | 47 The component follows the standard regulator framework and the bindings
|
| /linux-4.4.14/Documentation/power/ |
| D | swsusp-dmcrypt.txt | 64 pcmcia flash disk. What follows now is a /linuxrc for your
135 What then follows is the well known process to change the root
|
| D | opp.txt | 49 Typical usage of the OPP library is as follows:
208 implementation might choose to do something as follows:
224 choose to do something as follows:
312 represented as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/can/ |
| D | m_can.txt | 25 The format should be as follows:
|
| /linux-4.4.14/Documentation/arm/SA1100/ |
| D | Itsy | 21 configuration parameters in the monitor as follows:
|
| D | Assabet | 105 as follows:
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | scosh.S | 35 | Thus, we calculate sinh(X) as follows:
|
| D | ssinh.S | 35 | Thus, we calculate sinh(X) as follows:
|
| D | binstr.S | 47 | The registers are used as follows:
|
| /linux-4.4.14/Documentation/video4linux/cx2341x/ |
| D | fw-upload.txt | 9 The firmware stored in a Windows driver can be detected as follows:
|
| D | fw-dma.txt | 31 transfers. Detailed information follows this section.
|
| /linux-4.4.14/Documentation/thermal/ |
| D | exynos_thermal | 40 The threshold levels are defined as follows:
|
| D | cpu-cooling-api.txt | 168 device pass a function pointer that follows the `get_static_t`
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | README.maya44 | 87 As the ICE1724 chip only allows one global sampling rate, this is handled as follows:
103 PCM devices correspond to inputs/outputs as follows (assuming Maya44 is card #0):
|
| D | Channel-Mapping-API.txt | 82 /* this follows the alsa-lib mixer channel value + 3 */
|
| /linux-4.4.14/Documentation/scsi/ |
| D | LICENSE.FlashPoint | 26 The BSD-style License is as follows:
|
| D | ufs.txt | 33 For UFS version 1.0 and 1.1 the target performance is as follows,
|
| /linux-4.4.14/Documentation/devicetree/bindings/serial/ |
| D | qcom,msm-uartdm.txt | 10 A more specific property should be specified as follows depending
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | adfs.txt | 30 The mapping is performed as follows:
|
| D | affs.txt | 92 The Amiga protection flags RWEDRWEDHSPARWED are handled as follows:
112 The Linux rwxrwxrwx file mode is handled as follows:
|
| D | xfs-self-describing-metadata.txt | 217 A typical buffer read verifier is structured as follows:
242 the case it can't, the code is structured as follows:
|
| D | mandatory-locking.txt | 92 O_TRUNC flag set should be rejected. The Linux implementation follows the SVID
|
| D | nilfs2.txt | 253 among NILFS2 files can be depicted as follows:
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | soc-camera.txt | 50 function. The host object can be initialized as follows:
109 Above user ioctls modify image geometry as follows:
|
| D | pxa_camera.txt | 103 The descriptors are used as follows :
|
| D | radiotrack.txt | 56 The bits of the ioport are arranged as follows:
|
| /linux-4.4.14/Documentation/ |
| D | initrd.txt | 25 When using initrd, the system typically boots as follows:
228 # exec chroot . what-follows <dev/console >dev/console 2>&1
230 Where what-follows is a program under the new root, e.g. /sbin/init
261 as follows:
|
| D | vme_api.txt | 17 registration function. The structure is as follows:
328 The callback parameters are as follows. Care must be taken in writing a callback
392 The callback function is declared as follows.
|
| D | unaligned-memory-access.txt | 207 To avoid the unaligned memory access, you would rewrite it as follows:
218 memory and you wish to avoid unaligned access, its usage is as follows:
|
| D | futex-requeue-pi.txt | 56 would be modified as follows:
|
| D | dell_rbu.txt | 56 packets of data arranged back to back. It can be done as follows
|
| D | memory-barriers.txt | 295 defines "memory location" as follows:
634 as follows:
642 branches of the "if" statement as follows:
655 Unfortunately, current compilers will transform this as follows at high
726 one, perhaps as follows:
1270 This indicates that CPU 2's load from X in some sense follows CPU 1's
1277 CPU A follows a load from the same variable executing on CPU B, then
1363 Prevent both the compiler and the CPU from doing this as follows:
1505 to prevent this as follows:
1550 The compiler might save a branch by optimizing this as follows:
[all …]
|
| D | volatile-considered-harmful.txt | 32 If all the code follows the locking rules, the value of shared_data cannot
|
| D | atomic_ops.txt | 128 additional load as follows:
315 an example, which follows a pattern occurring frequently in the Linux
496 They are used as follows, and are akin to their atomic_t operation
|
| D | pnp.txt | 241 They are as follows:
|
| D | eisa.txt | 118 encapsulated in a 'struct eisa_device' described as follows :
|
| D | stable_kernel_rules.txt | 57 Send the patch, after verifying that it follows the above rules, to
|
| D | gcov.txt | 22 directory and use gcov with the -o option as follows (requires root):
|
| D | lzo.txt | 33 The first byte of the block follows a different encoding from other bytes, it
|
| D | kref.txt | 184 pointless to do so). You could use kref_put() as follows:
|
| D | printk-formats.txt | 258 and va_list as follows:
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | device.txt | 68 organized as follows into a group:
|
| /linux-4.4.14/Documentation/x86/x86_64/ |
| D | fake-numa-for-cpusets | 23 A machine may be split as follows with "numa=fake=4*512," as reported by dmesg:
|
| /linux-4.4.14/Documentation/spi/ |
| D | spi-lm70llp | 30 The hardware interfacing on the LM70 LLP eval board is as follows:
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | CMI8330 | 52 The old documentation file follows for reference
|
| D | mwave | 72 for Linux. Mine is as follows
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | nvidia,tegra20-i2c.txt | 9 Details of compatible are as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/ |
| D | ti-tsc-adc.txt | 24 is as follows:
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | ppc-pv.txt | 35 The parameters are as follows:
55 Return codes can be as follows:
|
| /linux-4.4.14/Documentation/pps/ |
| D | pps.txt | 88 pps_source_info_s as follows:
101 intialization routine as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/ti/ |
| D | ti,omap-dss.txt | 88 shifter). The video pipelines for the connectors are formed as follows:
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | firewire-cdev | 82 be used as follows: addr = NULL, length = the desired buffer
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | time.c | 827 int follows; in etr_sync_clock_stop() local
832 follows = etr_aib_follows(sync_port, aib, port); in etr_sync_clock_stop()
834 if (!follows) in etr_sync_clock_stop()
|
| /linux-4.4.14/Documentation/phy/ |
| D | samsung-usb2.txt | 70 The exynos4210_phys configuration array is as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | l2cc.txt | 9 The ARM L2 cache representation in the device tree should be done as follows:
|
| D | arm,scpi.txt | 81 - #thermal-sensor-cells: should be set to 1. This property follows the
|
| D | topology.txt | 100 Bindings for cluster/cpu/thread nodes are defined as follows:
|
| D | cpus.txt | 19 This document follows the conventions described in the ePAPR v1.1, with
|
| /linux-4.4.14/Documentation/acpi/ |
| D | scan_handlers.txt | 13 acpi_device objects are referred to as "device nodes" in what follows, but they
|
| /linux-4.4.14/arch/arc/kernel/ |
| D | entry.S | 374 ##### DONT ADD CODE HERE - .Lrestore_regs actually follows in entry-<isa>.S
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | pnfs.txt | 90 The API to the login script is as follows:
|
| D | nfs41-server.txt | 33 The OPTIONAL features identified and their abbreviations are as follows:
|
| D | nfs-rdma.txt | 98 This mount.nfs binary should be installed at /sbin/mount.nfs as follows:
|
| /linux-4.4.14/Documentation/arm64/ |
| D | booting.txt | 73 The decompressed kernel image contains a 64-byte header as follows:
105 composed as follows:
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-trace.txt | 131 When tracing pagefaults, the format of the trace is as follows:
|
| D | perf-probe.txt | 153 Each probe argument follows below syntax.
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | fs.txt | 191 root process follows a hardlink created by another user). Additionally,
211 root process follows a symlink belonging to another user). For a likely
|
| /linux-4.4.14/Documentation/i2c/ |
| D | upgrading-clients | 96 as follows:
|
| D | dev-interface | 33 Next thing, open the device file, as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | brcm,brcmnand.txt | 87 properties are as follows.
|
| /linux-4.4.14/Documentation/locking/ |
| D | locktorture.txt | 39 with string values as follows:
|
| /linux-4.4.14/Documentation/arm/OMAP/ |
| D | omap_pm | 141 in these cases, the board file needs to do additional steps as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,brcmstb.txt | 79 The layout of the property is as follows:
|
| /linux-4.4.14/Documentation/power/regulator/ |
| D | overview.txt | 110 to through the levels as follows :-
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 89 transmitted in network byte order. The format of this option is as follows:
209 follows:
295 Sensitivity tag type class. The format of this tag type is as follows:
358 class. The format of this tag type is as follows:
|
| /linux-4.4.14/Documentation/dvb/ |
| D | ci.txt | 101 This CI interface follows the CI high level interface, which is not
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | ilsp.doc | 115 An example of using the "cmp2" instruction is as follows:
|
| /linux-4.4.14/Documentation/hid/ |
| D | hidraw.txt | 49 will be the report number; the report data follows, beginning in the second
|
| D | hiddev.txt | 191 that influence the read() call above. The flags are as follows:
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/ |
| D | samsung-fimc.txt | 60 each cell is as follows:
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | pxa_dma.txt | 50 The descriptors are used as follows :
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | Insmod-options | 79 type=n type of the tuner chip. n as follows:
|
| /linux-4.4.14/Documentation/arm/nwfpe/ |
| D | README.FPE | 5 instructions. It follows the conventions in the ARM manual.
|
| /linux-4.4.14/fs/cramfs/ |
| D | README | 49 <block> immediately follows the last <block_pointer> for the file.
|
| /linux-4.4.14/Documentation/laptops/ |
| D | asus-laptop.txt | 111 is as follows:
|
| /linux-4.4.14/drivers/staging/most/Documentation/ |
| D | driver_usage.txt | 119 Internally the synchronous threshold is calculated as follows:
|
| /linux-4.4.14/sound/drivers/ |
| D | Kconfig | 201 the 'power_save' parameter can be set via sysfs as follows:
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | hvcs.txt | 105 To override the default use an insmod parameter as follows (requesting 4
187 mknod can be used as follows:
337 explicit example follows:
|
| /linux-4.4.14/drivers/usb/usbip/ |
| D | usbip_protocol.txt | 4 The USB/IP protocol follows a server/client architecture. The server exports the
|
| /linux-4.4.14/Documentation/trace/ |
| D | mmiotrace.txt | 128 end of line. The format for version 20070824 is as follows:
|
| /linux-4.4.14/Documentation/arm/ |
| D | cluster-pm-race-avoidance.txt | 47 Each cluster and CPU is assigned a state, as follows:
125 Transitions between states occur as follows.
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | cdrom.txt | 13 are as follows:
70 The information that follows was determined from reading kernel source
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | cachefiles.txt | 134 The daemon is run as follows:
466 columns are as follows:
|
| /linux-4.4.14/Documentation/serial/ |
| D | moxa-smartio | 290 as follows.
335 the source code as follows.
|
| /linux-4.4.14/arch/arm/nwfpe/ |
| D | softfloat-macros | 90 bits shifted off form a second 64-bit result as follows: The _last_ bit
215 off form a third 64-bit result as follows: The _last_ bit shifted off is
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | unified-hierarchy.txt | 279 C00, C01 under C0 and C10 under C1 as follows.
461 file follows the following format. More fields may later be
496 to the file follows the same format but the individual
|
| /linux-4.4.14/Documentation/s390/ |
| D | monreader.txt | 140 The layout of the data stream provided by the monreader device is as follows:
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | Overview.txt | 71 The currently supported machines are as follows:
|