Home
last modified time | relevance | path

Searched refs:writing (Results 1 – 200 of 390) sorted by relevance

12

/linux-4.1.27/Documentation/DocBook/
D.writing-an-alsa-driver.xml.cmd1 …Book/writing-an-alsa-driver.xml := SRCTREE=./ ./scripts/docproc doc Documentation/DocBook/writing-…
2 Documentation/DocBook/writing-an-alsa-driver.xml: Documentation/DocBook/writing-an-alsa-driver.tmpl
DMakefile16 alsa-driver-api.xml writing-an-alsa-driver.xml \
/linux-4.1.27/Documentation/cdrom/
D00-INDEX9 packet-writing.txt
10 - Info on the CDRW packet writing module
Dpacket-writing.txt23 Packet writing for DVD-RW media
38 Packet writing for DVD+RW media
65 Packet writing for DVD-RAM media
132 about DVD writing.
/linux-4.1.27/net/sunrpc/xprtrdma/
Dphysical_ops.c49 int nsegs, bool writing) in physical_op_map() argument
54 rpcrdma_data_dir(writing)); in physical_op_map()
Dfrwr_ops.c178 int nsegs, bool writing) in frwr_op_map() argument
182 enum dma_data_direction direction = rpcrdma_data_dir(writing); in frwr_op_map()
229 fastreg_wr.wr.fast_reg.access_flags = writing ? in frwr_op_map()
Dfmr_ops.c85 int nsegs, bool writing) in fmr_op_map() argument
89 enum dma_data_direction direction = rpcrdma_data_dir(writing); in fmr_op_map()
Dxprt_rdma.h435 rpcrdma_data_dir(bool writing) in rpcrdma_data_dir() argument
437 return writing ? DMA_FROM_DEVICE : DMA_TO_DEVICE; in rpcrdma_data_dir()
/linux-4.1.27/Documentation/virtual/kvm/
Dcpuid.txt44 || || writing to msr 0x4b564d02
47 || || writing to msr 0x4b564d03.
50 || || handler can be enabled by writing
Dreview-checklist.txt37 host/guest memory must be unshared to prevent the host from writing to
Dhypercalls.txt50 Purpose: Support MMU operations such as writing to PTE,
/linux-4.1.27/drivers/mtd/lpddr/
Dlpddr_cmds.c92 shared[i].writing = shared[i].erasing = NULL; in lpddr_cmdset()
213 contender = shared->writing; in get_chip()
267 shared->writing = chip; in get_chip()
339 if (shared->writing == chip && chip->oldstate == FL_READY) { in put_chip()
341 shared->writing = shared->erasing; in put_chip()
342 if (shared->writing && shared->writing != chip) { in put_chip()
344 struct flchip *loaner = shared->writing; in put_chip()
355 shared->writing = NULL; in put_chip()
356 } else if (shared->erasing == chip && shared->writing != chip) { in put_chip()
/linux-4.1.27/Documentation/fmc/
D00-INDEX20 - writing a carrier (a device)
23 - writing code for your mezzanine (a driver)
Dparameters.txt5 client modules. Both parameters can be modified by writing to
/linux-4.1.27/sound/usb/line6/
DKconfig12 * Reading/writing individual parameters
13 * Reading/writing complete channel, effects setup, and amp
/linux-4.1.27/drivers/firmware/google/
DKconfig19 platforms. This provides an interface for writing to and
20 clearing the EFI event log and reading and writing NVRAM
/linux-4.1.27/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt12 Since all Linux filesystems lock the whole inode during writing, algorithm
17 Object creation and data reading and writing are processed asynchronously.
37 command (or set of commands, which is frequently used during data writing: single transactions
38 can contain creation and data writing commands). Transactions are committed by all the servers
51 removal of objects and data writing are asynchronous and are sent to
/linux-4.1.27/Documentation/hwmon/
Damc682166 4 degree C. Read it out after writing to get
73 writing to get the actual value.
89 writing to get actual value.
Dabituguru361 neither is writing any of the sensor settings and writing / reading the
Dsubmitting-patches4 This text is a collection of suggestions for people writing patches or
84 * Avoid writing to chip registers in the detect function. If you have to write,
89 writing to it might cause a bad misconfiguration.
Dabituguru-datasheet63 that many bytes, reading / writing more will fail, the results when writing
76 when reading you should always use the read address and when writing the
96 not yet reported 0x08 at DATA and you proceed with writing a bank address.
154 turned up which do not hold 0x08 at DATA within 250 reads after writing the
Dnct668339 well hidden. Given this, writing any values from the operating system is
Df71805f152 You ask for a specific PWM duty cycle or DC voltage by writing to the
163 You ask for a specific fan speed by writing to the fan<n>_target file.
Djc4282 which applies to all limits. This register can be written by writing into
Dw8379395 by writing 0 to the sysfs file "intrusion0_alarm".
Dpmbus-core93 (used for detection), writing any value causes the associated history to be
102 or writing virtual registers (in other words, the PMBus core code will never
Df71882fg123 fan#_full_speed by writing to the pwm# file. This mode is only
/linux-4.1.27/arch/cris/arch-v10/
Doutput_arch.ld1 /* At the time of this writing, there's no equivalent ld option. */
/linux-4.1.27/arch/cris/arch-v32/
Doutput_arch.ld1 /* At the time of this writing, there's no equivalent ld option. */
/linux-4.1.27/Documentation/devicetree/bindings/mtd/
Dfsl-upm-nand.txt11 UPM pattern (0x1), after writing a data byte (0x2) or after
12 writing out a buffer (0x4).
Dfsmc-nand.txt24 when writing) after the command deassertation. Zero means
/linux-4.1.27/Documentation/power/
Dinterface.txt28 suspend-to-disk mechanism is in the 'testproc' mode, writing 'disk' to
31 in the 'test' mode, writing 'disk' to /sys/power/state will cause the kernel
66 contains '0' which may be changed to '1' by writing a string representing a
Duserland-swsusp.txt21 The device can be open either for reading or for writing. If open for
24 reading and writing. It is also impossible to have the device open more than
116 Currently it is assumed that the userland utilities reading/writing the
Dstates.txt89 of writing memory contents to disk. On resume, this is read and memory
/linux-4.1.27/Documentation/ABI/testing/
Ddebugfs-pktcdvd10 The pktcdvd module (packet writing driver) creates
Dprocfs-diskstats18 11 - time spent writing (ms)
Dsysfs-driver-pciback6 If the permissive attribute is set, then writing a string in
Dsysfs-power57 'testproc' mode, writing 'disk' to /sys/power/state will cause
60 the 'test' mode, writing 'disk' to /sys/power/state will cause
67 The suspend-to-disk method may be chosen by writing to this
106 it contains '0' which may be changed to '1' by writing a
156 disabled by writing "0" to this file, in which case all devices
256 Writing a "1" enables this printing while writing a "0"
Ddebugfs-ec15 or writing to them.
Dsysfs-i2c-bmp08523 value. When writing to this file the chip will use 2^x samples
Dsysfs-bus-platform9 to the device. The override is specified by writing a string
Dsysfs-kernel-livepatch26 while writing 1 will re-enable the patch.
Dsysfs-bus-amba9 the device. The override is specified by writing a string to the
Dsysfs-class-backlight-driver-adp887054 It can be enabled by writing the value stored in
Dsysfs-bus-pci-drivers-ehci_hcd20 companion controller, and writing the negative of a port
Dsysfs-class-pktcdvd10 The pktcdvd module (packet writing driver) creates
Dima_policy11 by opening the file, writing the rules one at a time and
Dsysfs-wusb_cbaf37 the host with device by: writing a randomly
Dsysfs-devices-power28 by the contents of this file by writing either "enabled", or
70 The value of this attribute may be changed by writing either
197 to writing "on" to the power/control attribute). Values >=
Dsysfs-driver-wacom68 When writing a 1024 byte raw image in Wacom Intuos 4
Dsysfs-driver-hid-wiimote10 disables the led, writing 1 enables it.
Dsysfs-bus-fcoe31 writing it's name, i.e. ctlr_X to the ctlr_delete file.
Dsysfs-ptp74 assignment may be changed by two writing numbers into
Dsysfs-driver-hid-roccat-savu74 This file allows reading and writing of the mouse sensors registers.
/linux-4.1.27/include/linux/mtd/
Dflashchip.h107 struct flchip *writing; member
/linux-4.1.27/Documentation/input/
Dedt-ft5x06.txt41 mode" by writing "1" or "0" to it. In factory mode (1) it is
53 mode. The same happens when reading/writing to the parameter files when the
Dyealink.txt117 hide_icon Write, hide the element by writing the icon name.
118 show_icon Write, display the element by writing the icon name.
Dsentelic.txt546 Register writing sequence:
592 9. the register writing sequence is completed.
597 command to FSP at the end of register writing to verify that the
598 register writing operation is successful (?? indicates don't care
614 to page 0x83, then start reading/writing from/to offset 0x01 by using
635 Page register writing sequence:
665 9. the page register writing sequence is completed.
/linux-4.1.27/Documentation/devicetree/bindings/fpga/
Daltera-socfpga-fpga-mgr.txt7 - The second index is for writing FPGA configuration data.
/linux-4.1.27/drivers/staging/xgifb/
DTODO2 going to be long. So, I'm writing "cleanups" and not the list.
/linux-4.1.27/Documentation/w1/masters/
Dds248226 However, the device cannot be detected without writing to the i2c bus, so no
/linux-4.1.27/Documentation/devicetree/bindings/serial/
Dqcom,msm-uart.txt5 with the MSM serial UARTDM except that it only supports reading and writing one
Dqcom,msm-uartdm.txt6 that it supports reading and writing multiple characters at a time.
/linux-4.1.27/arch/arm/include/debug/
Dmsm.S41 @ Clear TX_READY by writing to the UARTDM_CR register
/linux-4.1.27/Documentation/devicetree/bindings/
Deeprom.txt15 - pagesize : the length of the pagesize for writing. Please consult the
/linux-4.1.27/Documentation/powerpc/
Dcpu_features.txt33 that shouldn't be used by writing nop's over it. Using cpufeatures requires
55 __ftr_fixup, and if the required feature is not present it will loop writing
/linux-4.1.27/arch/powerpc/include/asm/
Dkvm_book3s_64.h300 static inline pte_t kvmppc_read_update_linux_pte(pte_t *ptep, int writing) in kvmppc_read_update_linux_pte() argument
321 if (writing && pte_write(old_pte)) in kvmppc_read_update_linux_pte()
Dkvm_book3s.h157 extern pfn_t kvmppc_gpa_to_pfn(struct kvm_vcpu *vcpu, gpa_t gpa, bool writing,
/linux-4.1.27/drivers/soc/ti/
DKconfig16 Packets are queued/de-queued by writing/reading descriptor address
/linux-4.1.27/drivers/staging/iio/Documentation/
Ddevice.txt3 This is not intended to provide a comprehensive guide to writing an
41 Raw value writing function. Used for writable device values such
Dsysfs-bus-iio-dds10 can control the desired active tuning word by writing Y to the
41 accumulator output by writing Y to the phase_en file.
/linux-4.1.27/drivers/staging/fbtft/
DREADME5 The module 'fbtft' makes writing drivers for some of these displays very easy.
/linux-4.1.27/Documentation/device-mapper/
Dstatistics.txt16 provided: total time spent reading and writing in milliseconds. All
123 8. the number of milliseconds spent writing
130 13. the total time spent writing in milliseconds
Dcache-policies.txt1 Guidance for writing policies
14 e.g. to start writing back dirty blocks that are going to be evicte
Ddm-log.txt9 are writing to it because the writes need to be replicated for all
/linux-4.1.27/Documentation/scsi/
Dst.txt23 new tape is loaded into the drive or if writing begins at the
26 QIC-drives). The result is that any tape can be read, writing can be
84 writing and the last operation has been a write. Two filemarks can be
108 device can be opened for writing even if there is a write protected
194 Asynchronous writing. Writing the buffer contents to the tape is
238 returns -1 and errno is set to ENOSPC. To enable writing a trailer,
295 opens the device for writing if the tape contents will be modified
297 not open for writing for, e.g., erase).
372 MT_ST_TWO_FM writing of two filemarks (global)
392 writing a filemark, don't wait for it to complete). Please
[all …]
Dhptiop.txt99 - Post the packet to IOP by writing it to inbound queue. For requests
119 by writing it to the outbound queue.
Dhpsa.txt112 to rescan for new devices. This does exactly the same thing as writing to the
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-devices-system-cpu5 Description: Writes are equivalent to writing to
Dvdso25 (As of this writing, this ABI documentation as been confirmed for x86_64.
Dsysfs-bus-usb24 being autosuspended at all, and writing a negative value
/linux-4.1.27/Documentation/usb/
Dehci.txt22 At this writing, this driver has been seen to work with implementations
52 At this writing the driver should comfortably handle all control, bulk,
57 at this writing no Linux drivers have been using that support.
160 At this writing, individual USB 2.0 devices tend to max out at around
192 In typical situations, a usb_bulk_msg() loop writing out 4 KB chunks is
Dfunctionfs.txt5 the user space driver has registered by writing descriptors and
Dgadget_printer.txt12 This driver may be used if you are writing printer firmware using Linux as
276 printf("Error %d writing to %s\n",
Dpersist.txt107 the feature by writing 0 instead of 1. For hubs the feature is
123 On the other hand, writing a persistent volume manager would be a big
Dpower-management.txt111 autosuspend. In fact, at the time of this writing (Linux 2.6.23) the
183 Writing "-1" to power/autosuspend_delay_ms and writing "on" to
188 (In 2.6.21 writing "0" to power/autosuspend would prevent the device
258 or a program explicitly enables it. As of this writing there aren't
425 writing "auto" to the device's power/control attribute. Likewise,
430 This is exactly the same as writing "on" to the power/control attribute.
/linux-4.1.27/include/linux/
Dpktcdvd.h69 int writing; /* Non-zero when writing, zero when reading */ member
/linux-4.1.27/Documentation/
Dpercpu-rw-semaphore.txt14 writing is very expensive, it calls synchronize_rcu() that can take
Dkernel-docs.txt133 a practical approach to writing Linux device drivers as kernel
156 abstract: "This article, the third of four on writing character
157 device drivers, introduces concepts of reading, writing, and using
166 writing character device drivers as loadable kernel modules. This
170 writing, and several different facilities have been provided for
203 Description: Introductory 50-minutes (sic) tutorial on writing
234 Description: 68 pages paper on writing character drivers. A little
297 (have data ready to be read or are ready for writing). Ideally you
320 URL: http://www.alsa-project.org/~iwai/writing-an-alsa-driver/index.html
478 overview on writing drivers, from the naming of functions to
Dbasic_profiling.txt4 Thanks to John Levon, Dave Hansen, et al. for help writing this.
Dsmsc_ece1099.txt26 are active interrupts. Software clears an interrupt by writing a 1 to the
Dhw_random.txt42 RNG available, you may change the one used by writing a name from
Dmd.txt95 An array is 'created' by writing appropriate superblocks to all
211 and writing will effect the 'new' value, leaving the 'old'
259 writing the word for the desired state, however some states
506 read are meaningful for writing.
540 If the array has a write-intent bitmap, then writing to this
Drtc.txt84 a negative impact on performance. This 64Hz limit can be changed by writing
102 probably a lot more useful to people interested in writing applications
Dunaligned-memory-access.txt34 When writing code, assume the target architecture has natural alignment
39 writing code that satisfies natural alignment requirements is the easiest way
/linux-4.1.27/Documentation/w1/slaves/
Dw1_ds240613 These chips also provide 128 bytes of OTP EPROM, but reading/writing it is
/linux-4.1.27/Documentation/acpi/
Ddebug.txt31 command line argument, and you can change it after boot by writing values
79 command line argument, and you can change it after boot by writing values
/linux-4.1.27/Documentation/security/
DSmack.txt46 smackload - properly formats data for writing to smackfs/load
47 smackcipso - properly formats data for writing to smackfs/cipso
104 can set the process Smack by writing there.
106 Most Smack configuration is accomplished by writing to files
212 label. The value is set by writing the desired label to the
213 file or cleared by writing "-" to the file.
323 policy is said to have privilege. As of this writing a task can
471 and writing. Creating a new task is an internal operation that results in two
491 privileged process can change its own Smack label by writing to
534 /sys/fs/smackfs/doi and can be changed by writing to /sys/fs/smackfs/doi.
[all …]
/linux-4.1.27/drivers/scsi/
Dst.h44 int writing; member
Dosst.h518 int writing; member
/linux-4.1.27/Documentation/fault-injection/
Dprovoke-crashes.txt29 You can also induce failures by mounting debugfs and writing the type to
/linux-4.1.27/Documentation/mmc/
Dmmc-dev-parts.txt7 As of this writing, MMC boot partitions as supported and exposed as
/linux-4.1.27/Documentation/cpu-freq/
Dboost.txt10 Reading or writing 1 does not mean that the system is boosting at this
56 Explicitly changing the permissions and writing to that file anyway will
/linux-4.1.27/drivers/ata/
Dpata_hpt3x2n.c299 static int hpt3x2n_use_dpll(struct ata_port *ap, int writing) in hpt3x2n_use_dpll() argument
304 if (writing) in hpt3x2n_use_dpll()
/linux-4.1.27/Documentation/virtual/kvm/devices/
Darm-vgic.txt53 reading or writing the register on the actual hardware from the cpu
74 same effect as reading or writing the register on the actual hardware.
Dmpic.txt33 edge, and writing 0 is ignored. Reading returns 1 if a previously
/linux-4.1.27/arch/powerpc/kvm/
Dbook3s_hv_rm_mmu.c151 unsigned int writing; in kvmppc_do_h_enter() local
158 writing = hpte_is_writable(ptel); in kvmppc_do_h_enter()
216 pte = kvmppc_read_update_linux_pte(ptep, writing); in kvmppc_do_h_enter()
218 if (writing && !pte_write(pte)) in kvmppc_do_h_enter()
Dbook3s_64_mmu_hv.c450 unsigned int writing, write_ok; in kvmppc_book3s_hv_page_fault() local
509 writing = (dsisr & DSISR_ISSTORE) != 0; in kvmppc_book3s_hv_page_fault()
511 write_ok = writing; in kvmppc_book3s_hv_page_fault()
513 npages = get_user_pages_fast(hva, 1, writing, pages); in kvmppc_book3s_hv_page_fault()
537 if (!writing && hpte_is_writable(r)) { in kvmppc_book3s_hv_page_fault()
Dbook3s.c367 pfn_t kvmppc_gpa_to_pfn(struct kvm_vcpu *vcpu, gpa_t gpa, bool writing, in kvmppc_gpa_to_pfn() argument
389 return gfn_to_pfn_prot(vcpu->kvm, gfn, writing, writable); in kvmppc_gpa_to_pfn()
/linux-4.1.27/Documentation/sh/
Dregister-banks.txt18 in mind when writing code that utilizes these banked registers, for obvious
/linux-4.1.27/tools/testing/selftests/rcutorture/doc/
Drcu-test-image.txt39 http://www.landley.net/writing/rootfs-howto.html
/linux-4.1.27/Documentation/filesystems/nfs/
Dnfsd-admin-interfaces.txt14 writing to nfsd/portlist; that write may be:
Drpc-server-gss.txt16 (At draft n. 02 at the time of writing)
Dnfs41-server.txt9 It can be disabled at run time by writing the string "-4.1" to
/linux-4.1.27/drivers/pnp/pnpbios/
DKconfig33 not be notified of any resource changes made by writing directly.
/linux-4.1.27/Documentation/thermal/
Dexynos_thermal_emulation33 Disabling emulation mode only requires writing value 0 to sysfs node.
/linux-4.1.27/block/
Dscsi_ioctl.c291 int writing = 0; in sg_io() local
308 writing = 1; in sg_io()
318 rq = blk_get_request(q, writing ? WRITE : READ, GFP_KERNEL); in sg_io()
/linux-4.1.27/Documentation/sound/alsa/soc/
Dplatform.txt50 http://www.alsa-project.org/~iwai/writing-an-alsa-driver/
Dcodec.txt126 http://www.alsa-project.org/~iwai/writing-an-alsa-driver/
/linux-4.1.27/drivers/fmc/
DKconfig49 acquainted with a mezzanine before writing its specific driver.
/linux-4.1.27/Documentation/filesystems/
Dsysfs-pci.txt77 call, and disable it following the access by writing "0" to the file. Note
82 The 'remove' file is used to remove the PCI device, by writing a non-zero
Decryptfs.txt47 Try writing a new file:
Dqnx6.txt169 When finished with writing (a sync write is completed, the maximum sync leap
174 For all data outside the system area, blocks are just copied while writing.
Dxfs-delayed-logging-design.txt64 dirtier as they get relogged, so each subsequent transaction is writing more
139 of accumulating changes in memory for some period before writing them to the
162 existing log item dirty region tracking) is that when it comes to writing the
186 the changes in a format that is compatible with the log buffer writing code.
231 buffer writing (i.e. double encapsulation). This would be an on-disk format
312 items are stored as log vectors, we can use the existing log buffer writing
314 minimise the time we hold the CIL locked while writing the checkpoint
316 way it separates the writing of the transaction contents (the log vectors) from
336 To ensure that we can be writing an item into a checkpoint transaction at
664 an ordering loop after writing all the log vectors into the log buffers but
[all …]
Dudf.txt10 Write support requires a block driver which supports writing. Currently
Dfiemap.txt137 in-place by writing to the indicated location without the
143 clear; user applications must not try reading or writing to the
Dlogfs.txt70 each level requires its own separate segment to be open for writing.
111 have a separate segment open for writing. Each (level, vim) tupel can
Drelay.txt37 sub-buffer, while the kernel continues writing to the next.
82 kernel which allow writing formatted text or raw data to a channel,
285 normal channel-writing functions, e.g. relay_write(), can still be
413 writing into the previous sub-buffer.
Dsysfs.txt197 When writing sysfs files, userspace processes should first read the
202 buffer when reading and writing values.
Dext2.txt252 the visible on-disk format). However, an old kernel writing to such a
285 It is frequently claimed that the ext2 implementation of writing
350 been modified, prior to writing them into the filesystem. This means
/linux-4.1.27/Documentation/ia64/
Defirtc.txt40 enables flexibility and permits writing wrapper code is ncase things change.
119 However writing such a program should be hard by simply using those two
DIRQ-redir.txt6 By writing to /proc/irq/IRQ#/smp_affinity the interrupt routing can be
/linux-4.1.27/drivers/block/
DKconfig196 Synchronous operation (i.e. always writing data to the host's disk
223 writing them to floppy. Furthermore, some Linux distributions avoid
420 tristate "Packet writing on CD/DVD media"
423 If you have a CDROM/DVD drive that supports packet writing, say
428 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
432 See the file <file:Documentation/cdrom/packet-writing.txt>
447 a disc is opened for writing.
Dsx8.c845 int writing = 0, pci_dir, i, n_elem, rc; in carm_rq_fn() local
865 writing = 1; in carm_rq_fn()
896 if (writing) { in carm_rq_fn()
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dmmci.txt4 reading and writing to MultiMedia and SD cards alike.
/linux-4.1.27/fs/ufs/
DKconfig34 Say Y here if you want to try writing to UFS partitions. This is
/linux-4.1.27/fs/jffs2/
DTODO24 By writing _new_ nodes to one block, and garbage-collected REF_PRISTINE
/linux-4.1.27/drivers/firmware/efi/
DKconfig27 will allow writing console messages, crash dumps, or anything
/linux-4.1.27/Documentation/arm64/
Dlegacy_instructions.txt7 The emulation mode can be controlled by writing to sysctl nodes
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DS3C2412.txt35 and reading or writing to them.
DGPIO.txt22 of the GPIO functions such as reading and writing a pin will
/linux-4.1.27/drivers/mtd/chips/
Dcfi_cmdset_0001.c754 shared[i].writing = shared[i].erasing = NULL; in cfi_intelext_partition_fixup()
922 contender = shared->writing; in get_chip()
976 shared->writing = chip; in get_chip()
995 if (shared->writing == chip && chip->oldstate == FL_READY) { in put_chip()
997 shared->writing = shared->erasing; in put_chip()
998 if (shared->writing && shared->writing != chip) { in put_chip()
1000 struct flchip *loaner = shared->writing; in put_chip()
1011 shared->writing = NULL; in put_chip()
1012 } else if (shared->erasing == chip && shared->writing != chip) { in put_chip()
DKconfig48 data bits when writing the 'magic' commands to the chips. Saying
151 This enables support for reading, writing and locking so called
/linux-4.1.27/Documentation/trace/
Devents-kmem.txt36 of writing, no information is available on what slab is being allocated from,
73 amount of writing on struct page.
Devents.txt206 A filter for an individual event is set by writing a filter expression
248 cleared as a group by writing a filter expression into the filter file
305 Triggers are added to and removed from a particular event by writing
346 For ease of use, writing to the trigger file using '>' currently just
Dtracepoint-analysis.txt220 data must be recorded. At the time of writing, this required root:
258 take a slightly different example. In the course of writing this, it was
Dring-buffer-design.txt57 will stop writing to the buffer. This will lose most recent events.
64 but a writer may interrupt another writer, but it must finish writing
83 buffer at the same time as a writer is writing, but the reader must be
215 is finished writing data into that position, it commits the write.
/linux-4.1.27/Documentation/fb/
Dpvr2fb.txt35 defaults to 640x480-16@60. At the time of writing the
Ddeferred_io.txt16 - app continues writing to that page with no additional cost. this is
/linux-4.1.27/Documentation/vm/
Dsoft-dirty.txt8 This is done by writing "4" into the /proc/PID/clear_refs file of the
Dtranshuge.txt120 It's possible to disable huge zero page by writing 0 or enable it
121 back by writing 1:
133 also possible to disable defrag in khugepaged by writing 0 or enable
134 defrag in khugepaged by writing 1:
/linux-4.1.27/drivers/s390/char/
DKconfig190 prompt "API for writing z/VM monitor service records"
193 Character device driver for writing z/VM monitor service records
/linux-4.1.27/drivers/block/drbd/
DKconfig50 The actual simulation of IO errors is done by writing 3 values to
/linux-4.1.27/drivers/mmc/card/
DKconfig65 in host controllers. The tests are executed by writing to the
/linux-4.1.27/Documentation/wimax/
DREADME.i2400m192 level; by writing to it, you can set it.
239 By writing a 0, a 1 or a 2 to the file
246 By writing any value to the /sys/kernel/debug/wimax:wmx0 file, the
DREADME.wimax72 level; by writing to it, you can set it.
/linux-4.1.27/Documentation/dvb/
DREADME.dvb-usb113 2004-05-11 - start writing the driver
216 writing the vp7045-driver.
227 (when writing the vp7041 driver)
/linux-4.1.27/Documentation/gpio/
Dsysfs.txt46 a GPIO to userspace by writing its number to this file.
95 for reading and writing. Existing and subsequent
/linux-4.1.27/Documentation/blockdev/
Dzram.txt61 Set disk size by writing the value to sysfs node 'disksize'.
78 Set memory limit by writing the value to sysfs node 'mem_limit'.
/linux-4.1.27/Documentation/networking/
Dcxacru.txt25 Configuration writing interface.
Dgen_stats.txt72 Locks are taken before writing and released once all statistics have
Ddns_resolver.txt154 Debugging messages can be turned on dynamically by writing a 1 into the
/linux-4.1.27/Documentation/i2c/
Di2c-stub14 commands (also to the specified addresses) by reading from or writing to
Dslave-interface27 driver. However, at this time of writing, the layer is transparent.
166 this time of writing. Some points to keep in mind when using buffers:
/linux-4.1.27/Documentation/sound/alsa/
DOSS-Emulation.txt120 writing a command to the proc file. There is a proc file for each PCM
180 filled. The latter stops writing the silence data ahead
277 current mixer configuration by reading and writing the whole file
DProcfile.txt79 mapping by writing to this device. Read OSS-Emulation.txt for
95 It takes an integer value, can be changed by writing to this
DHD-Audio.txt362 vendor-id value by writing to this file.
365 subsystem-id value by writing to this file.
368 revision-id value by writing to this file.
374 Shows the codec name string. Can be changed by writing to this
377 Shows the currently set `model` option. Can be changed by writing
381 writing to this file. Pass three numbers: nid, verb and parameter
/linux-4.1.27/Documentation/misc-devices/
Dc2port.txt88 after writing you have to reset the device to execute the new code:
Dspear-pcie-gadget.txt60 read back bar size and address after writing to cross check.
/linux-4.1.27/arch/m68k/
DKconfig108 initially work for you. As of this writing the exact hardware
/linux-4.1.27/drivers/staging/unisys/Documentation/
Doverview.txt161 and writing a channel in memory.
166 driver modules. Among its features it abstracts reading, writing, and
/linux-4.1.27/Documentation/laptops/
Ddisk-shock-protection.txt42 Otherwise, writing an integer value to this file will take the heads
114 kernel to enable the usage of this feature for that drive by writing
/linux-4.1.27/Documentation/serial/
Dtty.txt19 and writing over an existing ldisc will cause demons to eat your computer.
58 write() - A process is writing data through the line
124 put_char() Queues a character for writing to the tty device.
/linux-4.1.27/Documentation/infiniband/
Duser_verbs.txt19 devices. Fast path operations are typically performed by writing
/linux-4.1.27/Documentation/cpuidle/
Dsysfs.txt19 In this case users can switch the governor at run time by writing
/linux-4.1.27/drivers/media/dvb-frontends/
Drtl2832.c228 u8 msb, lsb, reading[4], writing[4], len; in rtl2832_wr_demod_reg() local
249 writing[i] = (writing_tmp >> ((len - 1 - i) * 8)) & 0xff; in rtl2832_wr_demod_reg()
251 ret = rtl2832_bulk_write(client, reg_start_addr, writing, len); in rtl2832_wr_demod_reg()
/linux-4.1.27/drivers/i2c/busses/
Di2c-mpc.c126 static int i2c_wait(struct mpc_i2c *i2c, unsigned timeout, int writing) in i2c_wait() argument
172 if (writing && (cmd_err & CSR_RXAK)) { in i2c_wait()
/linux-4.1.27/tools/perf/Documentation/
Dperf-script.txt47 using 'live-mode' i.e. without writing anything to disk. <script>
61 i.e. without writing anything to disk. <top-script> is the name
Dperf-trace.txt24 automatically include the raw_syscalls events when writing events to a file.
/linux-4.1.27/Documentation/isdn/
DREADME.hysdn120 After successfully writing the boot file, complete config files or single
122 If an error occurs the return value given to the writing process has the
/linux-4.1.27/Documentation/pti/
Dpti_intel_mid.txt31 *Hook /dev/pti to a user-level debugging application for writing
/linux-4.1.27/Documentation/devicetree/bindings/regulator/
Dregulator.txt27 but includes a final step of writing memory contents to disk.
/linux-4.1.27/drivers/auxdisplay/
DKconfig59 int "Delay between each control writing (microseconds)"
/linux-4.1.27/fs/reiserfs/
DREADME89 writing the cleanest code. He always made the effort to be the best he
135 Igor Zagorovsky is writing much of the new item handler and extent code
/linux-4.1.27/fs/ceph/
Dsuper.h163 int writing; /* a sync write is still in progress */ member
717 ci_item)->writing; in __ceph_have_pending_cap_snap()
Dsnap.c543 capsnap->writing = 1; in ceph_queue_cap_snap()
570 BUG_ON(capsnap->writing); in __ceph_finish_cap_snap()
/linux-4.1.27/drivers/xen/
DKconfig45 could be added by writing proper value to
110 For example, by reading and writing the "xenbus" file, guests
/linux-4.1.27/Documentation/s390/
Ds390dbf.txt72 writing events, high priority log entries should have a low level
75 through writing a number string "x" to the 'level' debugfs file which is
546 callback functions which are used for reading and writing the debugfs files:
590 'prolog_proc' once for writing the prolog.
/linux-4.1.27/Documentation/arm/
DPorting103 out of bounds memory accesses (eg, something writing off the end
/linux-4.1.27/Documentation/cgroups/
Ddevices.txt105 Allowing or denying all by writing 'a' to devices.allow or devices.deny will
Dmemory.txt291 is removed. The memory limitation itself, can of course be removed by writing
463 When writing anything to this
556 You can reset failcnt by writing 0 to failcnt file.
614 can be enabled by writing 1 to memory.use_hierarchy file of the root cgroup
674 writing to memory.move_charge_at_immigrate of the destination cgroup.
753 You can disable the OOM-killer by writing "1" to memory.oom_control file, as:
/linux-4.1.27/Documentation/block/
Dqueue-sysfs.txt132 control of this block device to that new IO scheduler. Note that writing
/linux-4.1.27/Documentation/RCU/
Drcu.txt62 o What guidelines should I follow when writing code that uses RCU?
/linux-4.1.27/drivers/char/
DKconfig56 If you say Y here, the support for writing user messages (i.e.
83 bool "Enable writing support of OTP pages"
87 If you say Y here, you will enable support for writing of the
263 power-off and for which writing to disk is too insecure. Note
/linux-4.1.27/security/selinux/
DKconfig45 This option enables writing to a selinuxfs node 'disable', which
/linux-4.1.27/arch/powerpc/platforms/ps3/
DKconfig93 Enables support for writing to the PS3 System Repository.
/linux-4.1.27/Documentation/devicetree/bindings/net/
Dfsl-tsec-phy.txt35 As of this writing, every tsec is associated with an internal TBI PHY.
/linux-4.1.27/Documentation/x86/
Dpat.txt122 interfaces. Users writing to /proc/mtrr are suggested to use above interfaces.
/linux-4.1.27/Documentation/development-process/
D3.Early-stage84 problems like this before writing the code.
136 currently active within the subsystem of interest. Look at who is writing
/linux-4.1.27/security/
DKconfig111 from userspace allocation. Keeping a user from writing to low pages

12