Home
last modified time | relevance | path

Searched refs:reported (Results 1 – 200 of 267) sorted by relevance

12

/linux-4.4.14/arch/sparc/kernel/
Dsbus.c276 int reported, portid; in sysio_ue_handler() local
309 reported = 0; in sysio_ue_handler()
311 reported++; in sysio_ue_handler()
315 reported++; in sysio_ue_handler()
319 reported++; in sysio_ue_handler()
322 if (!reported) in sysio_ue_handler()
350 int reported, portid; in sysio_ce_handler() local
388 reported = 0; in sysio_ce_handler()
390 reported++; in sysio_ce_handler()
394 reported++; in sysio_ce_handler()
[all …]
Dpci_sabre.c202 int reported; in sabre_ue_intr() local
233 reported = 0; in sabre_ue_intr()
235 reported++; in sabre_ue_intr()
239 reported++; in sabre_ue_intr()
243 reported++; in sabre_ue_intr()
246 if (!reported) in sabre_ue_intr()
262 int reported; in sabre_ce_intr() local
296 reported = 0; in sabre_ce_intr()
298 reported++; in sabre_ce_intr()
302 reported++; in sabre_ce_intr()
[all …]
Dpci_psycho.c138 int reported; in psycho_ue_intr() local
169 reported = 0; in psycho_ue_intr()
171 reported++; in psycho_ue_intr()
175 reported++; in psycho_ue_intr()
179 reported++; in psycho_ue_intr()
182 if (!reported) in psycho_ue_intr()
217 int reported; in psycho_ce_intr() local
254 reported = 0; in psycho_ce_intr()
256 reported++; in psycho_ce_intr()
260 reported++; in psycho_ce_intr()
[all …]
Dpci_schizo.c377 int reported, limit; in schizo_ue_intr() local
422 reported = 0; in schizo_ue_intr()
424 reported++; in schizo_ue_intr()
428 reported++; in schizo_ue_intr()
431 if (!reported) in schizo_ue_intr()
465 int reported, limit; in schizo_ce_intr() local
514 reported = 0; in schizo_ce_intr()
516 reported++; in schizo_ce_intr()
520 reported++; in schizo_ce_intr()
523 if (!reported) in schizo_ce_intr()
[all …]
Dpsycho_common.c307 int reported; in psycho_pcierr_intr() local
336 reported = 0; in psycho_pcierr_intr()
338 reported++; in psycho_pcierr_intr()
342 reported++; in psycho_pcierr_intr()
346 reported++; in psycho_pcierr_intr()
350 reported++; in psycho_pcierr_intr()
353 if (!reported) in psycho_pcierr_intr()
/linux-4.4.14/Documentation/input/
Dgamepad.txt82 devices for _all_ reported events that you need. Otherwise, you will also get
100 If only 2 action-buttons are present, they are reported as BTN_SOUTH and
104 If only 3 action-buttons are present, they are reported as (from left
106 If the buttons are aligned perfectly vertically, they are reported as
110 different formations. If diamond-shaped, they are reported as BTN_NORTH,
120 both are reported.
121 Digital buttons are reported as:
123 Analog buttons are reported as:
128 The left analog-stick is reported as ABS_X, ABS_Y. The right analog stick is
129 reported as ABS_RX, ABS_RY. Zero, one or two sticks may be present.
[all …]
Dntrig.txt12 This driver has been reported to work properly with multiple N-Trig devices
46 These nodes just provide easy access to the ranges reported by the device.
47 sensor_logical_height the range for positions reported during activity
66 obvious that these sensors were prone to erroneous events. Users reported
67 seeing both inappropriately dropped contact and ghosts, contacts reported
86 Time is measured in terms of the number of fingers reported, not frames since
Devent-codes.txt311 REL_{X,Y} must be reported when the mouse moves. BTN_LEFT must be used to report
318 ABS_{X,Y} must be reported with the location of the touch. BTN_TOUCH must be
320 BTN_{MOUSE,LEFT,MIDDLE,RIGHT} must not be reported as the result of touch
321 contact. BTN_TOOL_<name> events should be reported where possible.
339 BTN_TOOL_<name> events must be reported when a stylus or other tool is active on
340 the tablet. ABS_{X,Y} must be reported with the location of the tool. BTN_TOUCH
Dgpio-tilt.txt16 The array of struct gpio_tilt_axis describes the axes that are reported
Dalps.txt124 where the pointingstick buttons get reported separately in the PSM, PSR
161 Note that for some devices the trackstick buttons are reported in this packet,
162 and on others it is reported in the trackstick packets.
311 are in the button area, then the 2 coordinates reported
Dmulti-touch-protocol.txt70 contact that is reported by the hardware. Whenever the identity of the
81 total number of type B slots reported in the absinfo for the ABS_MT_SLOT axis.
276 degree orientation, the reported orientation must exceed the range max to
405 In order to stay compatible with existing applications, the data reported
Drotary-encoder.txt47 rotational direction based on the last stable state. Events are reported in
Dxpad.txt8 Due to backwards compatibility all buttons are reported as digital.
20 The number of buttons/axes reported varies based on 3 things:
Djoystick.txt256 There is one caveat with the 3D Pro. There are 9 buttons reported,
459 doing this, the device will be reported and will start working.
462 side of the orb, although reported as an ordinary button, causes internal
Dinput-programming.txt173 It's reported to the input system via:
/linux-4.4.14/Documentation/hwmon/
Dltc426137 Voltage readings provided by this driver are reported as obtained from the ADC
39 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the
43 Current reading provided by this driver is reported as obtained from the ADC
44 Current Sense register. The reported value assumes that a 1 mOhm sense resistor
46 current by dividing the reported value by the sense resistor value in mOhm.
51 on all chip variants. To ensure that the alarm condition is reported to the user,
Dltc426037 Voltage readings provided by this driver are reported as obtained from the ADC
39 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the
43 Current reading provided by this driver is reported as obtained from the ADC
44 Current Sense register. The reported value assumes that a 1 mOhm sense resistor
46 current by dividing the reported value by the sense resistor value in mOhm.
Dltc294537 Voltage readings provided by this driver are reported as obtained from the ADC
39 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the
43 Current reading provided by this driver is reported as obtained from the ADC
44 Current Sense register. The reported value assumes that a 1 mOhm sense resistor
46 current by dividing the reported value by the sense resistor value in mOhm.
Dltc415136 Voltage readings provided by this driver are reported as obtained from the ADIN
39 Current reading provided by this driver is reported as obtained from the Current
40 Sense register. The reported value assumes that a 1 mOhm sense resistor is
Dnct668326 Fan rotation speeds are reported in RPM (rotations per minute).
50 The driver has been reported to work with the following boards and
Dadc128d81838 caches the alarm status for each sensor until it is at least reported
39 once, to ensure that alarms are reported to user space.
Dasb10031 Temperatures are measured and reported in degrees Celsius.
33 Fan speeds are reported in RPM (rotations per minute). An alarm is
Dnct780225 The driver has been reported to work with the following boards and
Dnct677567 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
199 temperature measurement device. As a result, the temperature reported on CPUTIN
201 temperatures, and in some cases the reported temperature declines if the actual
204 boards. The CPU temperature on ASUS boards is reported from PECI 0.
Dpc8736060 Fan rotation speeds are reported in RPM (revolutions per minute). An alarm
105 One user reported problems with PWM. Changing PWM values would break fan
112 Temperatures are reported in degrees Celsius. Each temperature measured has
138 Voltages are reported relatively to a reference voltage, either internal or
Ducd900092 reported, but not both. If voltage or current is
93 reported depends on the chip configuration.
Demc210319 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
Dw83l786ng33 Fan rotation speeds are reported in RPM (rotations per minute). Fan readings
Dw83627ehf59 configurable. temp4 and higher attributes are only reported if its temperature
60 source differs from the temperature sources of the already reported temperature
71 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
Dpc8742734 Fan rotation speeds are reported as 14-bit values from a gated clock
Dsmsc47m144 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
Dsysfs-interface15 the CPU. Also, some values reported by the chips need some computation
326 Must be reported as an absolute temperature, NOT a delta
333 Must be reported as an absolute temperature, NOT a delta
349 Must be reported as an absolute temperature, NOT a delta
363 Must be reported as an absolute temperature, NOT a delta
375 Must be reported as an absolute temperature, NOT a delta
Dltc297869 in a single die. The chip is instantiated and reported as two separate chips
75 additional components on a single die. The chip is instantiated and reported
Dadm924073 On chip temperature is reported as degrees Celsius as 9-bit signed data
160 Alarm flags reported as 16-bit word
Df71805f99 Fan rotation speeds are reported as 12-bit values from a gated clock
114 Temperatures are reported in degrees Celsius. Each temperature measured
Dlm8041 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
Dg76227 fan1_input: provide current fan rotation value in RPM as reported by
Dgl518sm42 Rotation speeds are reported in RPM (rotations per minute). An alarm is
Dlm8738 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
Dlm7841 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
Dasc762126 Our conversion process produces a result that is reported as two bytes.
57 that the reported reading as well as the temperature used to determine
Dlm8329 will be reported instead of four.
Dvia686a46 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
Dsis559573 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
Dadm102649 Fan rotation speeds are reported in RPM (rotations per minute) but measured
Dlm85108 Devices has confirmed this "bug". The ADT7463 is reported to work as
192 NOTE: It has been reported that there is a bug in the LM85 that causes the flag
Dsmm66585 For SMM465 and SMM764, values for Channel E and F are reported but undefined.
Dit87172 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
267 The driver supports temp[1-3]_offset sysfs attributes to adjust the reported
Dw83791d73 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
Dw83792d58 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
Dvt1211106 Temperatures are reported in millidegree Celsius. Each measured temperature
Dw83781d92 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
160 One user has reported problems with fans stopping
Ddme1737117 Temperatures are measured with 12-bit resolution and reported in millidegree
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-bus-css5 Description: Contains the subchannel type, as reported by the hardware.
12 Description: Contains the module alias as reported with uevents.
21 subchannel, as reported by the channel subsystem
30 Description: Contains the PIM/PAM/POM values, as reported by the
Dsysfs-class-iommu-intel-iommu31 The architecture version as reported from the
Dsysfs-bus-mdio6 This attribute contains the 32-bit PHY Identifier as reported
Dconfigfs-usb-gadget-mass-storage28 cdrom - Flag specifying that LUN shall be reported as
Dsysfs-class-regulator24 the reported state is invalid.
324 This will be one of the same strings reported by
337 This will be one of the same strings reported by
350 This will be one of the same strings reported by
372 the reported state is invalid.
Dsysfs-class-power-twl403015 plug event. These event are reported via udev.
Dsysfs-driver-hid-roccat-kone7 setting reported by the mouse. This number has to be further
32 firmware reported by the mouse. Using the integer value eases
Dsysfs-block140 rarely reported for disk drives. For RAID arrays it is
145 reported this file contains 0.
191 unit in bytes if reported by the device. Otherwise the
Dsysfs-platform-dell-laptop19 as reported by the ambient light sensor.
Dconfigfs-usb-gadget125 qw_sign - an identifier to be reported as "OS String"
Dsysfs-class-mtd144 region comprising an ecc step (as reported by the driver) equals
193 The number of failures reported by this device's ECC. Typically,
Dsysfs-driver-hid-wiimote24 supported and if detected, it's no longer reported as static
Dsysfs-class-net-statistics181 reported as heartbeat errors. See the driver for the exact
Dsysfs-devices-power121 been reported with a timeout that expired. This attribute is
Dsysfs-power171 to a sleep state if any wakeup events are reported after the
/linux-4.4.14/drivers/acpi/apei/
DKconfig29 errors are reported to firmware firstly, then reported to
39 PCIe AER errors may be reported via APEI firmware first mode.
46 Memory errors may be reported via APEI firmware first mode.
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Dsnps-dw-apb-uart.txt28 be reported as active instead of being obtained from the modem status
31 be reported as active instead of being obtained from the modem status
34 be reported as active instead of being obtained from the modem status
37 reported as inactive instead of being obtained from the modem status register.
/linux-4.4.14/Documentation/
Dkmemleak.txt11 reported via /sys/kernel/debug/kmemleak. A similar method is used by the
40 objects to be reported as orphan.
54 marking all current reported unreferenced objects grey,
96 4. the remaining white objects are considered orphan and reported via
111 'clear' command to clear all reported unreferenced objects from the
162 reported by kmemleak because values found during the memory scanning
168 The false positives are objects wrongly reported as being memory leaks
174 Some of the reported leaks are only transient, especially on SMP
177 the minimum age of an object to be reported as a memory leak.
Dbad_memory.txt5 How to deal with bad memory e.g. reported by memtest86+ ?
37 Example: memtest86+ reported here errors at address 0x18691458, 0x18698424 and
Drtc.txt14 the Gregorian calendar and 24 hour time, as reported by gmtime(3).
49 are reported by interrupt number 8. (Oh! So *that* is what IRQ 8 is
57 The interrupts are reported via /dev/rtc (major 10, minor 135, read only
61 the last read. Status information is reported through the pseudo-file
Ddigsig.txt18 coding style, and checkpatch.pl reported errors and warnings have been fixed.
DIntel-IOMMU.txt70 When errors are reported, the DMA engine signals via an interrupt. The fault
Doops-tracing.txt85 stuff are the values reported by the Oops - you can just cut-and-paste
245 5: 'M' if any processor has reported a Machine Check Exception,
Dstable_kernel_rules.txt15 - Serious issues as reported by a user of a distribution kernel may also
DChanges290 events when CONFIG_X86_MCE is enabled. Machine check events are errors reported
Dedac.txt446 are reported through the system message log system. UE statistics
459 errors are reported through the system message log system.
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dimg-mdc-dma.txt14 The maximum burst size is this value multiplied by the hardware-reported bus
24 the number reported by the hardware is used.
/linux-4.4.14/Documentation/usb/
Derror-codes.txt9 way certain faults are reported.
77 reported. That's because transfers often involve several packets, so that
113 reported as -EPROTO or -EILSEQ.
117 completed, and no other error was reported by HC.
Dusbmon.txt11 Controller Drivers (HCD). So, if HCD is buggy, the traces reported by
161 is reported. For callbacks, actual length is reported.
173 reported in the Data Length word. In the case of an Isochronous input (Zi)
317 than requested, all events present are removed, and no error is reported.
Dusb-serial.txt308 reported state. Queries of outputs (DTR,RTS) show the last
314 states reported by the interrupt and the states requested.
Dmass-storage.txt89 reported as read only. This will prevent host from modifying the
DURB.txt205 Note that even when an error (or unlink) is reported, data may have been
/linux-4.4.14/Documentation/block/
Dnull_blk.txt36 The size of the device reported to the system.
39 The block size reported to the system.
Dqueue-sysfs.txt20 reported by the device. A value of '0' means device does not support
83 This is the smallest preferred IO size reported by the device.
109 This is the optimal IO size reported by the device.
/linux-4.4.14/drivers/staging/rdma/ehca/
Dehca_reqs.c180 qmap_entry->reported = 0; in ehca_write_swqe()
562 qmap_entry->reported = 0; in internal_post_recv()
737 if (qmap_entry->reported) { in ehca_poll_cq_one()
745 qmap_entry->reported = 1; in ehca_poll_cq_one()
816 while ((nr < num_entries) && (qmap_entry->reported == 0)) { in generate_flush_cqes()
861 qmap_entry->reported = 1; in generate_flush_cqes()
Dehca_classes.h166 u8 reported; member
/linux-4.4.14/Documentation/sound/alsa/
Dtimestamping.txt29 When timestamps are enabled, the avail/delay information is reported
69 audio time it wants reported by selecting the relevant settings in
99 or reported as is (the latter being useful to compare progress of
110 The accuracy is reported in nanosecond units (using an unsigned 32-bit
122 The ALSA API only allows for a single audio timestamp to be reported
127 timestamp is reported. Applications that need different timestamps
DAudiophile-Usb.txt112 One exception is the hw:1,2 port which was reported to be Little Endian
115 is reported to be big endian in this default driver mode.
174 the devices where reported to be Big-Endian when in fact they were Little-Endian
Dhdspm.txt276 reported.
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/
Dmax17042_battery.txt13 If skipped the condition won't be reported.
/linux-4.4.14/Documentation/x86/x86_64/
Dfake-numa-for-cpusets23 A machine may be split as follows with "numa=fake=4*512," as reported by dmesg:
56 Notice the difference between the system memory usage as reported by
Dmachinecheck29 subevent will not be reported.
45 check errors (but some corrected errors might be still reported
Dboot-options.txt21 Don't make logs for corrected errors. All events reported
27 and CMCI. All events reported as corrected are not cleared
/linux-4.4.14/Documentation/devicetree/bindings/input/
Dads7846.txt55 ti,pressure-min Minimum reported pressure value
57 ti,pressure-max Maximum reported pressure value (u16).
Dlpc32xx-key.txt13 - linux,keymap: the key-code to be reported when the key is pressed
Dsamsung-keypad.txt33 - linux,code: the key-code to be reported when the key is pressed
/linux-4.4.14/Documentation/misc-devices/
Dbh1770glc.txt102 i.e. when proximity on has been reported.
106 i.e. when proximity off has been reported.
Dics932s40122 All frequencies are reported in KHz.
Dlis3lv02d69 For better compatibility between the various laptops. The values reported by
72 * When the laptop is horizontal the position reported is about 0 for X and Y
/linux-4.4.14/arch/m68k/fpsp040/
Dgen_except.S25 | reported if ovfl occurs and the ovfl enable bit is not
124 | Frame is idle, so check for exceptions reported through
221 | No exceptions are to be reported. If the instruction was
239 | An fmoveout that results in an overflow is reported this way.
241 | An fmoveout that results in an underflow is reported this way.
Dkernel_ex.S5 | fpu for exceptional cases detected or reported within the
Dx_unfl.S92 | Inexact enabled and reported, and we must take an inexact exception
Dx_operr.S332 | Inexact enabled and reported, and we must take an inexact exception.
Dx_snan.S68 | Inexact enabled and reported, and we must take an inexact exception.
Ddecbin.S494 | it will be inex2, but will be reported as inex1 by get_op.
Dskeleton.S12 | exception is one that must be reported then there will be a
Ddo_func.S502 | stacked FPSR to be correctly reported.
/linux-4.4.14/Documentation/devicetree/bindings/x86/
Dce4100.txt33 If the OS is using the IO-APIC for interrupt routing then the reported
/linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/
Dtouchscreen.txt8 - touchscreen-max-pressure : maximum reported pressure (arbitrary range
/linux-4.4.14/Documentation/laptops/
Dsonypi.txt80 reported to the user. This parameter is required for
125 - several users reported that this driver disables the BIOS-managed
133 - some users reported that the laptop speed is lower (dhrystone
Dasus-laptop.txt58 should be reported via netlink events. You can check with
61 Hotkeys are also reported as input keys (like keyboards) you can check
Dsony-laptop.txt14 reported both through the ACPI subsystem as acpi events and through the INPUT
Dthinkpad-acpi.txt285 based on the capabilities reported by the ACPI firmware,
289 polled for in NVRAM, and reported as hotkey events if
298 events are reported by the firmware and can behave
310 to never be reported.
878 2: System board, left side (near PCMCIA slot), reported as HDAPS temp
906 thinkpad-acpi thermal sensors are reported through the hwmon
Dlaptop-mode.txt12 to conserve battery power on laptops. It has been reported to cause significant
71 * It has been reported that some versions of the mutt mail client use file access
/linux-4.4.14/drivers/net/wireless/realtek/rtl8xxxu/
DKconfig32 author or reported to be working by third parties.
/linux-4.4.14/tools/perf/Documentation/
Dperf-mem.txt22 Note that on Intel systems the memory latency reported is the use-latency,
/linux-4.4.14/drivers/net/wireless/libertas/
DREADME129 If it is set to 0, then the event is reported only once, and then
131 reported every time it occurs. If it is set to N, then the event is
132 reported every Nth time it occurs.
/linux-4.4.14/Documentation/device-mapper/
Dstatistics.txt17 argument is used, the 14th parameter is reported that represents the
21 The reported times are in milliseconds and the granularity depends on
23 reported times are in nanoseconds.
Dswitch.txt117 No status line is reported.
/linux-4.4.14/
DREPORTING-BUGS41 bug report. Some maintainers prefer bugs to be reported via bugzilla
42 (https://bugzilla.kernel.org), while others prefer that bugs be reported
70 If you haven't reported a bug before, please read:
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Dmips-gic.txt22 the base address reported by the hardware GCR_GIC_BASE will be used.
/linux-4.4.14/Documentation/s390/
Dqeth.txt38 or deregistered from the HiperSockets channel. Not reported if the
/linux-4.4.14/crypto/asymmetric_keys/
DKconfig22 ENOPKG will be reported if the requisite algorithm is unavailable.
/linux-4.4.14/Documentation/fb/
Dpvr2fb.txt45 but there is reported minor incompatibility between GUS DMA and
Dtgafb.txt56 The XFree86 FBDev server has been reported not to work, since tgafb doesn't do
Dapi.txt23 Device and driver capabilities are reported in the fixed screen information
63 Padding at end of lines may be present and is then reported through the fixed
127 Each pixel value is stored in the number of bits reported by the variable
Dframebuffer.txt152 work 100% with XF68_FBDev: the reported clock values are always incorrect.
/linux-4.4.14/Documentation/sound/oss/
DVIBRA1611 to setup because the kernel reported a lot of DMA errors and wouldn't
/linux-4.4.14/fs/quota/
DKconfig26 hardlimit, etc.) will be reported through netlink interface. If unsure,
/linux-4.4.14/scripts/coccinelle/iterators/
Duse_after_iter.cocci6 //#reported reference is at the label of this goto. Some flag tests
/linux-4.4.14/Documentation/watchdog/
Dpcwd-watchdog.txt47 This returns the status of the card that was reported
Dwatchdog-kernel-api.txt78 * bootstatus: status of the device after booting (reported with watchdog
157 status of the device is reported with watchdog WDIOF_* status flags/bits.
/linux-4.4.14/Documentation/scsi/
Dadvansys.txt67 assertions encountered should be reported to the person
215 Ken Mort <ken@mort.net> reported a DEBUG compile bug fixed
224 Dave Jones <dave@denial.force9.co.uk> reported the compiler
DChangeLog.sym53c8xx98 SCRIPTS. These errors are now immediately reported to
255 - Work-around PCI chips being reported twice on some platforms.
285 (A problem has been reported on PPC with that code).
342 (Btw, only problems with Toshiba 3401B had been reported).
Daha152x.txt132 cylinders by dividing the capacity reported by the disk by 64*32 (1 MB).
DBusLogic.txt53 include with the bug report the complete configuration messages reported by the
97 reported for each target device, as well as the status of Tagged Queuing.
131 are reported as "Enabled", Disabled", or a sequence of "Y" and "N" letters.
Dosst.txt157 have been sent, but mostly reported success or only minor trouble.
DChangeLog.megaraid22 Customer reported "garbage in file on x86_64 platform".
145 Customer reported "Unable to handle kernel NULL pointer dereference
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-pyra7 setting reported by the mouse. This number has to be further
32 firmware reported by the mouse. Using the integer value eases
Dsysfs-driver-hid-roccat-kovaplus46 firmware reported by the mouse. Using the integer value eases
Dsysfs-driver-hid-roccat-koneplus28 firmware reported by the mouse. Using the integer value eases
/linux-4.4.14/Documentation/isdn/
DREADME.diversion66 All incoming calls matching a rule except the ignore rule a reported and
118 If a call is reported as proceeding an external program or client may
DREADME.gigaset10 connection. The following devices are reported to be compatible:
302 3.1. Solutions to frequently reported problems
/linux-4.4.14/Documentation/networking/
Dcxacru.txt93 Changes in adsl/line state are reported via kernel log messages:
D3c509.txt140 receives packets (as reported by /proc/net/dev or 'ifconfig') you likely
Dtimestamping.txt106 The other three bits control which timestamps will be reported in a
109 are only reported for packets that also have the relevant timestamp
DREADME.sb1000202 the SB1000 users who reported and helped debug the common problems listed
DREADME.ipw2100248 xxxx/yyyy will be replaced with 'off' -- the level reported will be the active
/linux-4.4.14/lib/
DKconfig.kmemcheck47 In one-shot mode, only the first error detected is reported before
DKconfig.debug311 reported at least twice.
313 the section mismatches that are reported.
773 enabled then all held locks will also be reported. This
927 deadlocks (lockups) to be detected and reported automatically.
944 reported.
1005 reported by the kernel (once the event is observed that
/linux-4.4.14/Documentation/thermal/
Dnouveau_thermal72 [PWM_min, PWM_max] range, the reported fan speed (RPM) may not be accurate
/linux-4.4.14/Documentation/power/
Dbasic-pm-debugging.txt105 reported.
134 should be reported. In that case you can also try to switch the nonboot CPUs
141 reported.
/linux-4.4.14/Documentation/mmc/
Dmmc-dev-attrs.txt36 reported by the card. Note that "erase_size" does not apply
/linux-4.4.14/Documentation/video4linux/bttv/
DPROBLEMS24 Frank Kapahnke <frank@kapahnke.prima.ruhr.de> also reported that problems
/linux-4.4.14/Documentation/dmaengine/
Ddmatest.txt37 emitted. After that only test failure messages are reported until the test
Dprovider.txt128 - Granularity of the transfer residue reported to dma_set_residue.
243 implement, obviously depend on the transaction types you reported as
/linux-4.4.14/Documentation/nfc/
Dnfc-hci.txt266 must be reported such that upper layers don't stay ignorant that something
280 connection, the error is reported through the connect completion.
282 - HCI: if an internal HCI error happens (frame is lost), or HCI is reported an
/linux-4.4.14/drivers/memory/
DKconfig99 Coherency Fabric. Errors reported include accesses to
/linux-4.4.14/Documentation/security/
DIMA-templates.txt11 templates. For example, information that could be possibly reported are
/linux-4.4.14/Documentation/early-userspace/
Dbuffer-format.txt96 (GNU cpio is reported to attach the data to the last instance of a
/linux-4.4.14/security/selinux/
DKconfig103 by SELinux to be set to a particular value. This value is reported
/linux-4.4.14/arch/sh/kernel/cpu/sh3/
Dentry.S488 * but is unfortunately reported through INTEVT rather than
/linux-4.4.14/Documentation/video4linux/
Dradiotrack.txt11 Frans Brinkman (brinkman@esd.nl) in 1996. The results reported here are from
/linux-4.4.14/arch/powerpc/kvm/
DKconfig121 together with the number of executions are reported in debugfs in
/linux-4.4.14/Documentation/RCU/
Dtrace.txt90 has already reported a quiescent state for the last RCU grace
98 CPU has not yet reported that fact, (2) some other CPU has not
99 yet reported for this grace period, or (3) both.
404 a quiescent state, but not yet reported it to RCU.
/linux-4.4.14/Documentation/i2c/
Dfault-codes51 fault is only reported on read transactions; the SMBus slave
/linux-4.4.14/Documentation/vm/
Didle_page_tracking.txt30 and hence such pages are never reported idle.
Dhwpoison.txt11 * High level machine check handler. Handles pages reported by the
/linux-4.4.14/Documentation/rapidio/
Dsysfs.txt80 linked to the ingress port (reported as "lprev"). This is an array
/linux-4.4.14/Documentation/pcmcia/
Ddriver-changes.txt123 driver was reported to rely on them:
/linux-4.4.14/drivers/net/ethernet/mellanox/mlx4/
Dcmd.c2223 int reported = 0; in mlx4_master_comm_channel() local
2232 ++reported; in mlx4_master_comm_channel()
2256 if (reported && reported != served) in mlx4_master_comm_channel()
2258 reported, served); in mlx4_master_comm_channel()
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-class-tpm185 were scaled by the driver to be reported in usec from msecs.
/linux-4.4.14/arch/m68k/ifpsp060/
Dfplsp.doc109 entry. If an exception should be reported, then the package forces
/linux-4.4.14/drivers/usb/storage/
DKconfig90 Devices reported to work with this driver include:
/linux-4.4.14/Documentation/networking/caif/
Dspi_porting.txt53 Only active edges are mandatory to be reported.
/linux-4.4.14/Documentation/cdrom/
Dcdrom-standard.tex429 common). It has been reported that these drives can make reading
643 in a number of i/o errors reported by the VFS to the kernel when an
913 or data tracks on it, it will be reported as $CDS_AUDIO$. If it has
916 CD-I tracks on it, it will be reported as $CDS_XA_2_2$. Failing
918 reported as $CDS_XA_2_1$. Finally, if the CD in question has any
919 data tracks on it, it will be reported as a data CD ($CDS_DATA_1$).
/linux-4.4.14/Documentation/pps/
Dpps.txt74 the USB stack. Users has reported clock instability around +-1ms when
/linux-4.4.14/Documentation/serial/
Dmoxa-smartio422 log reported by this driver whenever it's activated.
443 Rx/Tx throughputs per second are also reported in interval basis (e.g.
/linux-4.4.14/arch/blackfin/
DKconfig.debug43 be reported multiple cycles after the error happens. This delay
/linux-4.4.14/fs/affs/
DChanges280 - Errors and warnings are now reported via a
/linux-4.4.14/Documentation/hid/
Dhiddev.txt151 report id as reported by the device -- or relative --
/linux-4.4.14/Documentation/ia64/
Daliasing.txt96 an attribute reported as being supported in the EFI memory map.
/linux-4.4.14/Documentation/blockdev/
Dfloppy.txt232 line. If the reported problem happens when mounting floppy disks, be
/linux-4.4.14/Documentation/wimax/
DREADME.i2400m211 The numbers reported are
/linux-4.4.14/Documentation/filesystems/
Doverlayfs.txt82 such as metadata and extended attributes are reported for the upper
Dxfs.txt116 If "nolargeio" is specified, the optimal I/O reported in
/linux-4.4.14/arch/powerpc/platforms/
DKconfig270 halfway between the upper and lower bounds, will be reported in
/linux-4.4.14/drivers/iommu/
DKconfig140 These DMA remapping devices are reported via ACPI tables
/linux-4.4.14/Documentation/virtual/kvm/
Dmsr.txt233 reported as steal time.
/linux-4.4.14/drivers/edac/
DKconfig17 These are low-level errors that are reported in the CPU or
/linux-4.4.14/Documentation/x86/
Dmtrr.txt91 that reported by the X server.
Dintel_mpx.txt178 93 short _addr_lsb; /* LSB of the reported address */
/linux-4.4.14/Documentation/cpu-freq/
Dgovernors.txt180 The frequency sensitivity is a hardware reported (on AMD Family 16h
/linux-4.4.14/net/ipv4/
DKconfig279 If you are SYN flooded, the source address reported by the kernel is
280 likely to have been forged by the attacker; it is only reported as
/linux-4.4.14/Documentation/sysctl/
Dfs.txt110 reported with printk, look for "VFS: file-max limit <number>
/linux-4.4.14/Documentation/PCI/
Dpcieaer-howto.txt233 A: Fatal error recovery will fail if the errors are reported by the
/linux-4.4.14/drivers/thermal/
DKconfig390 trip points. The temperature reported by the thermal sensor reflects the

12