Home
last modified time | relevance | path

Searched refs:reading (Results 1 – 200 of 381) sorted by relevance

12

/linux-4.4.14/drivers/staging/speakup/
DDefaultKeyAssignments12 InsKeyPad-8 say from top of screen to reading cursor.
18 InsKeyPad-4 say from left edge of line to reading cursor.
20 InsKeyPad-6 Say from reading cursor to right edge of line.
26 InsKeyPad-plus Say from reading cursor line to bottom of screen.
27 KeyPad-Minus Park reading cursor (toggle)
31 InsKeyPad-9 Move reading cursor to top of screen (insert pgup)
32 InsKeyPad-3 Move reading cursor to bottom of screen (insert pgdn)
33 InsKeyPad-7 Move reading cursor to left edge of screen (insert home)
34 InsKeyPad-1 Move reading cursor to right edge of screen (insert end)
35 ControlKeyPad-1 Move reading cursor to last character on current line.
[all …]
Dspkguide.txt191 can still use the reading controls to review the screen however.
435 level and the reading punctuation level at the same time. For
441 # set punc and reading punc levels to 0
448 # set punc and reading punc levels to 1
455 # set punc and reading punc levels to 2
462 # set punc and reading punc levels to 3
469 chmod command, then you could change the default reading punc and
472 then the reading punc and punc level would both get set to 3.
810 Use the speakup review keys to position the reading cursor on the first
811 character of the above url. When the reading cursor is in position,
[all …]
/linux-4.4.14/drivers/media/usb/gspca/
Dsn9c2028.c111 static int sn9c2028_read4(struct gspca_dev *gspca_dev, u8 *reading) in sn9c2028_read4() argument
123 memcpy(reading, gspca_dev->usb_buf, 4); in sn9c2028_read4()
124 PDEBUG(D_USBI, "read4 response %02x%02x%02x%02x", reading[0], in sn9c2028_read4()
125 reading[1], reading[2], reading[3]); in sn9c2028_read4()
132 __u8 reading[4]; in sn9c2028_long_command() local
146 memset(reading, 0, 4); in sn9c2028_long_command()
147 status = sn9c2028_read4(gspca_dev, reading); in sn9c2028_long_command()
/linux-4.4.14/drivers/hwmon/
Dpowr1220.c116 int reading; in powr1220_read_adc() local
151 reading = result >> 4; in powr1220_read_adc()
158 reading |= result << 4; in powr1220_read_adc()
161 reading *= ADC_STEP_MV; in powr1220_read_adc()
162 data->adc_values[ch_num] = reading; in powr1220_read_adc()
165 result = reading; in powr1220_read_adc()
167 if (reading > data->adc_maxes[ch_num]) in powr1220_read_adc()
168 data->adc_maxes[ch_num] = reading; in powr1220_read_adc()
/linux-4.4.14/Documentation/
Dpercpu-rw-semaphore.txt5 optimized for locking for reading.
8 cores take the lock for reading, the cache line containing the semaphore
12 Locking for reading is very fast, it uses RCU and it avoids any atomic
Dnumastat.txt24 For easier reading you can use the numastat utility from the numactl package
Dcircular-buffers.txt203 /* Read index before reading contents at that index. */
214 /* Finish reading descriptor before incrementing tail. */
221 This will instruct the CPU to make sure the index is up to date before reading
222 the new item, and then it shall make sure the CPU has finished reading the item
Dsysfs-rules.txt24 reading directories and opening the files yourself.
66 - retrieved by reading the "subsystem"-link and using only the
72 - it is retrieved by reading the "driver"-link and using only the
165 - When reading and writing sysfs device attribute files, avoid dependency
Dio_ordering.txt4 typically done by reading a 'safe' device or bridge register, causing the I/O
Dlocal_ops.txt8 properly. It also stresses on the precautions that must be taken when reading
73 variable can be read when reading some _other_ cpu's variables.
Dunaligned-memory-access.txt15 For example, reading 4 bytes of data from address 0x10004 is fine, but
16 reading 4 bytes of data from address 0x10005 would be an unaligned memory
89 by 4 (remember, we're reading a 4 byte value here).
Dntb.txt70 The Tool provides access through debugfs for reading, setting, and clearing the
71 NTB doorbell, and reading and writing scratchpads.
Ddell_rbu.txt24 maintains a link list of packets for reading them back.
Dxillybus.txt248 reading from the device's register space. All communication from the FPGA to
275 necessary). The host responds by making the data available for reading through
313 For example, reading single bytes from a pipe with 32 bit granularity works
Dxz.txt94 Support for limited random-access reading is planned for the
/linux-4.4.14/drivers/staging/iio/Documentation/
Dsysfs-bus-iio-light43 use a infrared sensor reading to remove infrared noise from the
44 proximity reading. If this is not enabled, the driver can still
45 do this calculation manually by reading the infrared sensor
53 used to return the value of a reading by the sensor. If this
62 sensing mode. This value should be the output from a reading
94 sensing mode. This value should be the output from a reading
Dinkernel.txt48 about this channel such as it's current reading.
51 iio_read_channel_raw() - get a reading
Dring.txt35 The primary buffer reading function. Note that it may well not return
Doverview.txt45 capture or reading from a number of sensors. These triggers are
Ddevice.txt38 Raw data reading function. Used for both raw channel access
/linux-4.4.14/Documentation/hwmon/
Dina20936 in0_input_highest shunt voltage historical maximum reading (mV)
37 in0_input_lowest shunt voltage historical minimum reading (mV)
49 in1_input_highest bus voltage historical maximum reading (mV)
50 in1_input_lowest bus voltage historical minimum reading (mV)
62 power1_input_highest power historical maximum reading (uW)
Dabituguru-datasheet9 Winbond (W83L950D). And no, reading the manual for this specific uC or
45 hold 0x09 and will only hold 0x08 after reading CMD first, so CMD must be read
63 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
93 After reading CMD, DATA should hold 0x08 which means that the uGuru is ready
195 This byte holds the reading from the sensor. Sensors in Bank1 can be both
200 Volt sensors use a linear scale, a reading 0 corresponds with 0 volt and a
201 reading of 255 with 3494 mV. The sensors for higher voltages however are
206 Temp sensors also use a linear scale, a reading of 0 corresponds with 0 degree
207 Celsius and a reading of 255 with a reading of 255 degrees Celsius.
[all …]
Dadm102537 input, or as the a fifth digital entry for the VID reading (bit 4). It's
43 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
Dntc_thermistor97 (reading this file initiates the reading procedure.)
Dgl518sm29 0x80 chips support the reading of all voltages and revision 0x00 only
58 reading the current voltage of any input except for VIN3; limit setting and
72 The GL518SM only updates its values each 1.5 seconds; reading it more often
Dabituguru35 * Abit uGuru revision 3 (Hardware Monitor part, reading only)
61 neither is writing any of the sensor settings and writing / reading the
Dasc762122 specification. First enhancement is temperature reading resolution. We
30 next read of any register. So to get an atomic reading, read high or low
57 that the reported reading as well as the temperature used to determine
110 - Noise filtering of temperature reading for fan speed control
266 Remote Diode 1 reading is associated with
Dadm924057 The adm9240 driver will take a measurement reading no faster than once
92 - auto fan clock adjuster enabled for valid fan speed reading
136 The reading is an unsigned 8-bit value, nominal voltage measurement is
137 represented by a reading of 192, being 3/4 of the measurement range.
Dtmp10317 wafer chip-scale package (WCSP). The TMP103 is capable of reading
Dsmsc47b39727 Methods for detecting the HP SIO and reading the thermal data on a dc7100.
69 How to convert the tach reading to RPM.
70 The tach reading (TCount) is given by: (Tach MSB * 256) + (Tach LSB)
Dmax161927 other second; reading them more often will do no harm, but will return
Dltc415139 Current reading provided by this driver is reported as obtained from the Current
Dlm6340 The datasheet isn't very clear about what the tachometer reading is.
68 the update_interval sysfs attribute; reading them more often will do no harm,
Dfam15h_power19 This driver permits reading of registers providing power information
Dibmpowernv12 This driver implements reading the platform sensors data like temperature/fan/
Dg760a35 other second; reading them more often will do no harm, but will return
Dhtu2145 Different resolutions, the on-chip heater, using the CRC checksum and reading
Dw83627hf57 VID reading. However the two chips have the identical 128 pin package. So,
62 doesn't help, you may just ignore the bogus VID reading with no harm done.
Dltc426043 Current reading provided by this driver is reported as obtained from the ADC
Dw83l785ts29 every other second; reading them more often will do no harm, but will
Dsht2148 Different resolutions, the on-chip heater, using the CRC checksum and reading
Dibmaem20 This driver implements sensor reading support for the energy and power meters
Dadc128d81842 reading it more often will do no harm, but will return 'old' values.
Dk8temp16 This driver permits reading temperature sensor(s) embedded inside AMD K8
Dltc426143 Current reading provided by this driver is reported as obtained from the ADC
Dacpi_power_meter16 This driver implements sensor reading support for the power meters exposed in
Dltc294543 Current reading provided by this driver is reported as obtained from the ADC
Dthmc5043 The THMC50 only updates its values each 1.5 seconds; reading it more often
Dlm8062 The LM80 only updates its values each 1.5 seconds; reading it more often
Dnct677573 reading returns an invalid value, and it reduces it if the fan speed reading
Dit8790 by either the battery or the onboard power supply. Only the first reading
93 the chip so can be read at any time. Excessive reading may decrease
213 The IT87xx only updates its values each 1.5 seconds; reading it more often
Dltc424596 the sensor reading.
Dlm8757 The lm87 driver only updates its values each 1.0 seconds; reading it more
Dlm7867 The LM7* only updates its values each 1.5 seconds; reading it more often
Dlm7578 slowest chips and 125 ms for the fastest chips; reading it more often
Dlm93121 circuitry that allows an accurate tachometer reading to be
210 If a temperature reading falls below the base value for that channel, the LM93
256 All eight GPIOs are read by reading the bitmask in the sysfs file gpio. The
Dsmsc47m19266 in[0-7]_max - lower and upper alarm thresholds for in[0-7]_input reading
Dk10temp48 This driver permits reading of the internal temperature sensor of AMD
Dlm8384 other second; reading them more often will do no harm, but will return
Dvia686a65 The driver only updates its values each 1.5 seconds; reading it more often
Dcoretemp20 This driver permits reading the DTS (Digital Temperature Sensor) embedded
Dsis559599 The SiS5595 only updates its values each 1.5 seconds; reading it more often
Dlm90226 the update_interval attribute; reading them more often will do no harm, but will
248 When reading a register value, the PEC byte is computed and sent by the
Dadm102185 This driver only updates its values each 1.5 seconds; reading it more often
Dw83792d103 The chips only update values each 3 seconds; reading them more often will
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-ryos27 Before reading this file, control has to be written to select
37 Before reading this file, control has to be written to select
47 Before reading this file, control has to be written to select
57 Before reading this file, control has to be written to select
67 Before reading this file, control has to be written to select
77 Before reading this file, control has to be written to select
88 Before reading this file, control has to be written to select
99 Before reading this file, control has to be written to select
110 Before reading this file, control has to be written to select
156 Before reading this file, control has to be written to select
[all …]
Dsysfs-driver-hid-roccat-isku27 Before reading this file, control has to be written to select
37 Before reading this file, control has to be written to select
47 Before reading this file, control has to be written to select
57 Before reading this file, control has to be written to select
67 Before reading this file, control has to be written to select
77 Before reading this file, control has to be written to select
87 Before reading this file, control has to be written to select
106 Before reading this file, control has to be written to select
117 Before reading this file, control has to be written to select
Dsysfs-driver-hid-roccat-savu12 Before reading this file, control has to be written to select
54 Before reading this file, control has to be written to select
74 This file allows reading and writing of the mouse sensors registers.
Dsysfs-driver-hid-roccat-konepure51 Before reading this file, control has to be written to select
67 Before reading this file, control has to be written to select
Dsysfs-driver-hid-roccat-kovaplus73 Before reading this file, control has to be written to select
101 Before reading this file, control has to be written to select
Dsysfs-driver-hid-roccat-pyra59 Before reading this file, control has to be written to select
87 Before reading this file, control has to be written to select
Dsysfs-driver-hid-roccat-koneplus66 Before reading this file, control has to be written to select
94 Before reading this file, control has to be written to select
/linux-4.4.14/block/
Dblk-map.c206 int reading = rq_data_dir(rq) == READ; in blk_rq_map_kern() local
219 bio = bio_copy_kern(q, kbuf, len, gfp_mask, reading); in blk_rq_map_kern()
226 if (!reading) in blk_rq_map_kern()
Dbio.c1492 gfp_t gfp_mask, int reading) in bio_copy_kern() argument
1523 if (!reading) in bio_copy_kern()
1533 if (reading) { in bio_copy_kern()
/linux-4.4.14/drivers/macintosh/
Dvia-macii.c105 reading, enumerator
424 macii_state = reading; in macii_interrupt()
473 case reading: in macii_interrupt()
503 if (macii_state == reading) { in macii_interrupt()
Dvia-cuda.c72 reading, enumerator
485 cuda_state = reading; in cuda_interrupt()
496 cuda_state = reading; in cuda_interrupt()
541 case reading: in cuda_interrupt()
586 cuda_state = reading; in cuda_interrupt()
Dvia-maciisi.c77 reading, enumerator
480 maciisi_state = reading; in maciisi_interrupt()
549 case reading: in maciisi_interrupt()
627 maciisi_state = reading; in maciisi_interrupt()
Dvia-pmu68k.c82 reading, enumerator
622 pmu_state = reading; in pmu_interrupt()
637 case reading: in pmu_interrupt()
Dvia-pmu.c119 reading, enumerator
1466 if (pmu_state == reading || pmu_state == reading_intr) in pmu_sr_intr()
1495 pmu_state = reading; in pmu_sr_intr()
1514 case reading: in pmu_sr_intr()
/linux-4.4.14/Documentation/w1/
Dw1.generic38 2. reading. This will issue reading eeprom response.
54 provides temperature reading function which is bound to ->rbin() method
57 w1_smem - driver for simple 64bit memory cell provides ID reading method.
59 You can call above methods by reading appropriate sysfs files.
/linux-4.4.14/drivers/media/v4l2-core/
Dvideobuf-core.c195 if (q->reading) { in videobuf_queue_is_busy()
238 if (q->streaming || q->reading) { in __videobuf_free()
269 q->reading = 0; in videobuf_queue_cancel()
542 if (q->reading) { in videobuf_qbuf()
744 if (q->reading) in videobuf_streamon()
993 q->reading = 1; in __videobuf_read_start()
1040 if (q->reading) in videobuf_stop()
1061 if (!q->reading) { in videobuf_read_stream()
1134 if (!q->reading) in videobuf_poll_stream()
1136 if (!q->reading) { in videobuf_poll_stream()
/linux-4.4.14/Documentation/input/
Dedt-ft5x06.txt52 Note that reading raw_data gives a I/O error when the device is not in factory
53 mode. The same happens when reading/writing to the parameter files when the
Djoystick-api.txt139 If read returns -1 when reading in O_NONBLOCK mode, this isn't
189 process the events and keep reading it until you empty the driver queue.
Damijoy.txt151 give a full scale (FF) reading with about 500kohms in one
Dsentelic.txt459 1. Identify FSP by reading device ID(0x00) and version(0x01) register
461 2a. For FSP version < STL3888 Cx, determine number of buttons by reading
501 Register reading sequence:
614 to page 0x83, then start reading/writing from/to offset 0x01 by using
617 Page register reading sequence:
/linux-4.4.14/drivers/scsi/qla4xxx/
Dql4_attr.c38 long reading; in qla4_8xxx_sysfs_write_fw_dump() local
48 ret = kstrtol(buf, 10, &reading); in qla4_8xxx_sysfs_write_fw_dump()
55 switch (reading) { in qla4_8xxx_sysfs_write_fw_dump()
/linux-4.4.14/Documentation/fmc/
Dfmc-trivial.txt17 This driver is worth reading, in my opinion.
Dfmc-chardev.txt51 repeated reading data is written to stdout; repeated writes read from
54 The following examples show reading the SDB magic number and the first
/linux-4.4.14/Documentation/devicetree/bindings/media/i2c/
Dmt9m111.txt10 For further reading on port node refer to
Dmt9p031.txt19 For further reading on port node refer to
Dov2659.txt15 For further reading on port node refer to
Dmt9v032.txt24 For further reading on port node refer to
Dtvp514x.txt23 For further reading on port node refer to Documentation/devicetree/bindings/
Dtvp7002.txt30 For further reading of port node refer Documentation/devicetree/bindings/media/
/linux-4.4.14/drivers/hwtracing/coresight/
Dcoresight-tmc.c124 bool reading; member
248 if (drvdata->reading) { in tmc_enable()
367 if (drvdata->reading) in tmc_disable()
451 drvdata->reading = true; in tmc_read_prepare()
480 drvdata->reading = false; in tmc_read_unprepare()
/linux-4.4.14/Documentation/ABI/testing/
Dprocfs-diskstats14 7 - time spent reading (ms)
Dsysfs-devices-sun13 So reading the sysfs file, we can identify a physical position
Ddebugfs-olpc8 reading their responses.
Dsysfs-firmware-dmi-tables14 through sysfs as an alternative to utilities reading them
Dsysfs-devices-soc7 regarding each SoC can be obtained by reading sysfs files. This
Dsysfs-block10 4 - time spent reading (ms)
223 the result of reading a discarded area is undefined.
Dsysfs-driver-wacom96 reports have been received from the paired device, reading
/linux-4.4.14/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.4.14/Documentation/devicetree/bindings/power/
Drx51-battery.txt11 * "temp" - The ADC channel for temperature reading
/linux-4.4.14/drivers/virt/
DKconfig25 2) A file interface to reading incoming doorbells.
/linux-4.4.14/Documentation/device-mapper/
Dstatistics.txt16 provided: total time spent reading and writing. When the histogram
35 memory is used by reading
156 4. the number of milliseconds spent reading
166 12. the total time spent reading in milliseconds
/linux-4.4.14/drivers/extcon/
Dextcon-arizona.c528 static int arizona_hpdet_do_id(struct arizona_extcon_info *info, int *reading, in arizona_hpdet_do_id() argument
539 info->hpdet_res[info->num_hpdet_res++] = *reading; in arizona_hpdet_do_id()
565 *reading = info->hpdet_res[0]; in arizona_hpdet_do_id()
568 if (*reading >= ARIZONA_HPDET_MAX && !info->hpdet_retried) { in arizona_hpdet_do_id()
604 int ret, reading; in arizona_hpdet_irq() local
632 reading = ret; in arizona_hpdet_irq()
640 ret = arizona_hpdet_do_id(info, &reading, &mic); in arizona_hpdet_irq()
647 if (reading >= 5000) in arizona_hpdet_irq()
/linux-4.4.14/drivers/soc/ti/
DKconfig16 Packets are queued/de-queued by writing/reading descriptor address
/linux-4.4.14/drivers/firmware/google/
DKconfig20 clearing the EFI event log and reading and writing NVRAM
/linux-4.4.14/drivers/gpu/drm/gma500/
Dcdv_intel_dp.c79 i2c_algo_dp_aux_address(struct i2c_adapter *adapter, u16 address, bool reading) in i2c_algo_dp_aux_address() argument
85 if (reading) in i2c_algo_dp_aux_address()
100 i2c_algo_dp_aux_stop(struct i2c_adapter *adapter, bool reading) in i2c_algo_dp_aux_stop() argument
105 if (reading) in i2c_algo_dp_aux_stop()
155 bool reading = false; in i2c_algo_dp_aux_xfer() local
162 reading = (msgs[m].flags & I2C_M_RD) != 0; in i2c_algo_dp_aux_xfer()
163 ret = i2c_algo_dp_aux_address(adapter, msgs[m].addr, reading); in i2c_algo_dp_aux_xfer()
166 if (reading) { in i2c_algo_dp_aux_xfer()
184 i2c_algo_dp_aux_stop(adapter, reading); in i2c_algo_dp_aux_xfer()
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dmoxa,moxart-clock.txt8 by reading registers holding multiplier and divisor information.
Dmvebu-core-clock.txt4 reading the Sample-At-Reset (SAR) register. The core clock consumer should
/linux-4.4.14/Documentation/networking/
Dsmc9.txt9 should not be using the driver without reading this file.
/linux-4.4.14/Documentation/laptops/
Dsony-laptop.txt33 actual_brightness reading from this file will query the HW
97 reading the DSDT table source should reveal that:
121 those entries are for, by reading/writing random values from/to those
Dasus-laptop.txt64 You can get information on the version of your DSDT table by reading the
74 You can also know if they are on/off by reading their content and use
Ddisk-shock-protection.txt57 reading from /sys/block/*/device/unload_heads will report the number
59 otherwise, reading the unload_heads attribute will return 0.
/linux-4.4.14/drivers/media/dvb-frontends/
Drtl2832.c198 u8 msb, lsb, reading[4], len; in rtl2832_rd_demod_reg() local
207 ret = rtl2832_bulk_read(client, reg_start_addr, reading, len); in rtl2832_rd_demod_reg()
213 reading_tmp |= reading[i] << ((len - 1 - i) * 8); in rtl2832_rd_demod_reg()
228 u8 msb, lsb, reading[4], writing[4], len; in rtl2832_wr_demod_reg() local
237 ret = rtl2832_bulk_read(client, reg_start_addr, reading, len); in rtl2832_wr_demod_reg()
243 reading_tmp |= reading[i] << ((len - 1 - i) * 8); in rtl2832_wr_demod_reg()
/linux-4.4.14/Documentation/block/
Dcmdline-partition.txt4 Support for reading the block device partition table from the command line.
/linux-4.4.14/Documentation/w1/slaves/
Dw1_ds240613 These chips also provide 128 bytes of OTP EPROM, but reading/writing it is
/linux-4.4.14/Documentation/power/
Duserland-swsusp.txt21 The device can be open either for reading or for writing. If open for
22 reading, it is considered to be in the suspend mode. Otherwise it is
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
Ds2ram.txt9 2) If that does not help, try reading tricks.txt and
Dpm_qos_interface.txt34 reading the aggregated value does not require any locking mechanism.
104 Note: The aggregated target values are implemented in such a way that reading
Dswsusp-dmcrypt.txt63 of your crypto devices, again by reading the setup from the
/linux-4.4.14/fs/reiserfs/
DREADME48 Stop reading here. Go there, then return.
81 To understand the code, after reading the website, start reading the
82 code by reading reiserfs_fs.h first.
/linux-4.4.14/Documentation/ia64/
Derr_inject.txt490 perror("status reading error.\n");
502 perror("capabilities reading error.\n");
518 perror("err_type_info reading error.\n");
525 perror("err_struct_info reading error.\n");
532 perror("err_data_buffer reading error.\n");
539 perror("status reading error.\n");
546 perror("capabilities reading error.\n");
553 perror("resources reading error.\n");
Defirtc.txt82 For reading:
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-dsp-keystone.txt13 - reading pin value returns 0 - if IRQ was handled or 1 - IRQ is still
/linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/
Dtsc2007.txt22 - ti,poll-period: how much time to wait (in milliseconds) before reading again the
/linux-4.4.14/Documentation/misc-devices/
Disl2900361 returns the value from the last sensor reading
Deeprom48 This is a simple EEPROM module meant to enable reading the first 256 bytes
/linux-4.4.14/drivers/media/usb/stkwebcam/
Dstk-webcam.h121 int reading; member
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Dinfo.txt25 Number of milliseconds to wait for reply from remote server for data reading command.
26 If this timeout is exceeded, reading returns an error.
Ddesign_notes.txt17 Object creation and data reading and writing are processed asynchronously.
40 For example, reading will return an error if no servers are available.
/linux-4.4.14/Documentation/mtd/nand/
Dpxa3xx-nand.txt36 So, in order to achieve reading (for instance), we issue several READ0 commands
52 and expected to be located (when reading/programming) right after the spare
/linux-4.4.14/Documentation/virtual/kvm/devices/
Darm-vgic.txt53 reading or writing the register on the actual hardware from the cpu whose
75 same effect as reading or writing the register on the actual hardware.
/linux-4.4.14/fs/squashfs/
DKconfig128 Saying Y here includes support for reading Squashfs file systems
143 Saying Y here includes support for reading Squashfs file systems
158 Saying Y here includes support for reading Squashfs file systems
/linux-4.4.14/include/scsi/
Dosd_ore.h142 bool reading; member
/linux-4.4.14/Documentation/devicetree/bindings/phy/
Dsun4i-usb-phy.txt30 - usb0_id_det-gpios : gpio phandle for reading the otg id pin value
/linux-4.4.14/Documentation/usb/
Ddwc3.txt4 Please pick something while reading :)
/linux-4.4.14/drivers/iio/humidity/
DKconfig10 This driver supports reading data via a single interrupt
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt163 a new IO, but the (slow) reader thread is still reading from it. In other words,
164 the reader consulted a map entry, and started reading the corresponding block. A
167 internal, postmap block that the reader is (still) reading has been inserted
173 into rtt[lane_number], the postmap ABA it is reading, and clears it after the
/linux-4.4.14/tools/perf/tests/
DBuild29 perf-y += code-reading.o
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dmmci.txt4 reading and writing to MultiMedia and SD cards alike.
/linux-4.4.14/Documentation/devicetree/bindings/input/
Dcros-ec-keyb.txt4 a separate EC (Embedded Controller) device. It provides a message for reading
/linux-4.4.14/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.4.14/include/media/
Dvideobuf-core.h152 unsigned int reading:1; member
/linux-4.4.14/crypto/asymmetric_keys/
DKconfig56 it is, the PKCS#7 wrapper is discarded and reading the key returns
/linux-4.4.14/Documentation/video4linux/
DREADME.cpia2106 program has started reading the other. If this happens, the driver must drop
108 this case use 2 buffers. You are probably not reading at the full frame rate.
DREADME.ir48 The cvs version of the lircd daemon supports reading events from the
Dradiotrack.txt78 Results available by reading ioport >60 msec after last port write.
/linux-4.4.14/Documentation/s390/
Dmonreader.txt119 There are two alternative methods for reading: either non-blocking read in
180 continue reading subsequent data or rather exit.
194 will account for the message limit, i.e. opening the device without reading
Dzfcpdump.txt24 CONFIG_CRASH_DUMP has to be set. When reading from "zcore/mem", the part of
Ds390dbf.txt66 a view can be inspected simply by reading the corresponding debugfs file.
401 Views to the debug logs can be investigated through reading the corresponding
546 callback functions which are used for reading and writing the debugfs files:
580 The output when reading a debugfs file is structured like this:
/linux-4.4.14/Documentation/vm/
Dsoft-dirty.txt15 This is done by reading from the /proc/PID/pagemap. The bit 55 of the
Dactive_mm.txt7 and when I do I feel better about more people reading them.
Dtranshuge.txt200 available by reading the AnonHugePages field in /proc/meminfo. To
203 for each mapping. Note that reading the smaps file is expensive and
204 reading it frequently will incur overhead.
Didle_page_tracking.txt44 /sys/kernel/mm/page_idle/bitmap. The pages can be found by reading
/linux-4.4.14/Documentation/filesystems/
D9p.txt49 seen by reading /sys/bus/virtio/drivers/9pnet_virtio/virtio<n>/mount_tag files.
95 rfdno=n the file descriptor for reading with trans=fd
Decryptfs.txt54 just wrote. To test reading, from start to finish, you need to clear
Dudf.txt6 If you encounter problems with reading UDF discs using this driver,
Dmandatory-locking.txt21 read has actually completed, and the reading process may see
39 prevent reading the mailbox while it is being updated.
/linux-4.4.14/drivers/s390/char/
DKconfig183 prompt "API for reading z/VM monitor service records"
186 Character device driver for reading z/VM monitor service records
/linux-4.4.14/fs/befs/
DChangeLog244 * Fixed a problem with reading the superblock on devices with large sector
253 * Fix bug with reading an empty directory. (btree.c and dir.c)
267 * Added B+tree reading functions (in btree.c).
327 * Added sanity check for inode reading
/linux-4.4.14/Documentation/i2c/
Di2c-stub14 commands (also to the specified addresses) by reading from or writing to
/linux-4.4.14/fs/jffs2/
DREADME.Locking34 jffs2_sb_info structure. Atomically reading the wbuf_len member to see
129 been unlinked. Because reading from the flash may sleep, the
/linux-4.4.14/arch/arm/mach-pxa/
Dsleep.S162 @ force address lines low by reading at physical address 0
/linux-4.4.14/Documentation/arm/keystone/
Dknav-qmss.txt14 reading descriptor address to a particular memory mapped location. The PDSPs
/linux-4.4.14/Documentation/wimax/
DREADME.wimax71 By reading the file you can obtain the current value of said debug
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dfw-cfg.txt38 with key 0x0000, and reading four bytes from the data register. The returned
/linux-4.4.14/Documentation/dmaengine/
Ddmatest.txt47 initialization to pause until a test run has completed, while reading
Dpxa_dma.txt107 - reading the physical channel last updater mark
/linux-4.4.14/tools/perf/Documentation/
Dperf-bench.txt29 Default style. This is mainly for human reading.
Dperf-trace.txt110 hooking the open syscall return + vfs_getname or via reading /proc/pid/fd, etc.
/linux-4.4.14/Documentation/fb/
Dintelfb.txt141 4. The X developers. Insights were provided just by reading the
Dvesafb.txt136 the video memory (i.e. starts reading from top if it
/linux-4.4.14/fs/exofs/
Dore.c288 ios->reading = is_reading; in ore_get_rw_state()
455 u64 residual = ios->reading ? in ore_check_io()
606 if (!ios->reading) { in _ore_add_stripe_unit()
/linux-4.4.14/Documentation/scsi/
Dst.txt69 of the physical block on tape. When reading, the drive reads the next
75 be a multiple of the block size. This is not required when reading but
204 when reading them back via sysfs they may be in the process of being
455 reading in variable block mode to enhance performance when
456 reading blocks shorter than the byte count; set this only
489 reading/writing.
Dscsi-generic.txt10 Thus sg is used for scanners, CD writers and reading audio CDs digitally
DChangeLog.sym53c8xx_284 - Mask GPCNTL against 0x1c (was 0xfc) for the reading of the NVRAM.
Dhptiop.txt89 - Get a free request packet by reading the inbound queue port or
DChangeLog.megaraid40 > strange effect: reading from some files leads to the
46 > file reading.
58 > sda : reading 26/26 512 byte blocks.
DChangeLog.ncr53c8xx3 - Ensure LEDC bit in GPCNTL is cleared when reading the NVRAM.
71 * NVRAM detection and reading
88 * NVRAM detection and reading
/linux-4.4.14/Documentation/filesystems/nfs/
Drpc-server-gss.txt89 before starting nfsd. Whoever starts nfsd can guarantee this by reading
Dnfs41-server.txt5 by reading this file will contain either "+4.1" or "-4.1"
/linux-4.4.14/Documentation/sound/alsa/
DHD-Audio-Models.txt87 auto auto-config reading BIOS (default)
139 auto auto-config reading BIOS (default)
DOSS-Emulation.txt183 You can check the currently defined configuration by reading the proc
277 current mixer configuration by reading and writing the whole file
/linux-4.4.14/Documentation/RCU/
DNMI-RCU.txt119 clear to someone reading the code that the pointer is
/linux-4.4.14/Documentation/ioctl/
Dcdrom.txt70 The information that follows was determined from reading kernel source
205 EIO I/O error reading TOC
474 ENOSYS Drive is not capable of reading MCN data.
/linux-4.4.14/arch/m68k/ifpsp060/
DCHANGES34 was reading the intermediate bytes. Emulation now only
/linux-4.4.14/security/
DKconfig13 This enforces restrictions on unprivileged users reading the kernel
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-tape.1995-2002194 * reading tapes with multiple consecutive write
200 * required after reading from /dev/nhtx to be
/linux-4.4.14/Documentation/frv/
Dbooting.txt174 Normally the kernel will work out how much SDRAM it has by reading the
/linux-4.4.14/drivers/net/wireless/rt2x00/
DKconfig260 These debugfs files support both reading and writing of the
/linux-4.4.14/Documentation/gpio/
Dsysfs.txt94 for reading and writing. Existing and subsequent
/linux-4.4.14/Documentation/virtual/kvm/
Dlocking.txt80 writable between reading spte and updating spte. Like below case:
/linux-4.4.14/Documentation/locking/
Dlglock.txt19 reading and occasional cpu local writing with very infrequent
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-qmss.txt10 reading descriptor address to a particular memory mapped location. The PDSPs
/linux-4.4.14/Documentation/cdrom/
Dcdrom-standard.tex290 & int& speed;& maximum speed for reading data \cr
350 \item[0] Open for reading data, as done by {\tt {mount()}} (2), or the
429 common). It has been reported that these drives can make reading
521 fact, there are 6 different $ioctl$s for reading data, either in some
523 reading audio tracks as data, I believe this is because of protection
628 either by reading/writing to the device file, or by issuing
868 option flag register after modification. Use $arg = \rm0$ for reading

12