Home
last modified time | relevance | path

Searched refs:diagnostic (Results 1 – 51 of 51) sorted by relevance

/linux-4.1.27/tools/build/feature/
Dtest-gtk2.c1 #pragma GCC diagnostic ignored "-Wstrict-prototypes"
3 #pragma GCC diagnostic error "-Wstrict-prototypes"
Dtest-gtk2-infobar.c1 #pragma GCC diagnostic ignored "-Wstrict-prototypes"
3 #pragma GCC diagnostic error "-Wstrict-prototypes"
/linux-4.1.27/tools/perf/ui/gtk/
Dgtk.h6 #pragma GCC diagnostic ignored "-Wstrict-prototypes"
8 #pragma GCC diagnostic error "-Wstrict-prototypes"
/linux-4.1.27/arch/arm/mach-tegra/
Dreset-handler.S133 mrc p15, 0, r0, c15, c0, 1 @ read diagnostic register
136 mcr p15, 0, r0, c15, c0, 1 @ write diagnostic register
146 mrc p15, 0, r0, c15, c0, 1 @ read diagnostic register
149 mcr p15, 0, r0, c15, c0, 1 @ write diagnostic register
/linux-4.1.27/net/x25/
Dx25_subr.c232 *dptr++ = x25->causediag.diagnostic; in x25_write_internal()
350 unsigned char diagnostic) in x25_disconnect() argument
361 x25->causediag.diagnostic = diagnostic; in x25_disconnect()
/linux-4.1.27/net/rose/
Drose_subr.c166 *dptr++ = rose->diagnostic; in rose_write_internal()
530 void rose_disconnect(struct sock *sk, int reason, int cause, int diagnostic) in rose_disconnect() argument
545 if (diagnostic != -1) in rose_disconnect()
546 rose->diagnostic = diagnostic; in rose_disconnect()
Drose_link.c239 …_request(struct rose_neigh *neigh, unsigned int lci, unsigned char cause, unsigned char diagnostic) in rose_transmit_clear_request() argument
259 *dptr++ = diagnostic; in rose_transmit_clear_request()
Drose_route.c677 unsigned char *diagnostic, int route_frame) in rose_get_neigh() argument
712 *diagnostic = 0; in rose_get_neigh()
715 *diagnostic = 0; in rose_get_neigh()
862 unsigned char cause, diagnostic; in rose_route_frame() local
920 rose->diagnostic = 0; in rose_route_frame()
1039 if ((new_neigh = rose_get_neigh(dest_addr, &cause, &diagnostic, 1)) == NULL) { in rose_route_frame()
1040 rose_transmit_clear_request(rose_neigh, lci, cause, diagnostic); in rose_route_frame()
Daf_rose.c721 unsigned char cause, diagnostic; in rose_connect() local
766 &diagnostic, 0); in rose_connect()
1328 rose_cause.diagnostic = rose->diagnostic; in rose_ioctl()
1337 rose->diagnostic = rose_cause.diagnostic; in rose_ioctl()
/linux-4.1.27/arch/arm/mm/
Dproc-v7.S388 mrcle p15, 0, r10, c15, c0, 1 @ read diagnostic register
390 mcrle p15, 0, r10, c15, c0, 1 @ write diagnostic register
396 mrceq p15, 0, r10, c15, c0, 1 @ read diagnostic register
399 mcreq p15, 0, r10, c15, c0, 1 @ write diagnostic register
403 mrceq p15, 0, r10, c15, c0, 1 @ read diagnostic register
405 mcreq p15, 0, r10, c15, c0, 1 @ write diagnostic register
410 mrclt p15, 0, r10, c15, c0, 1 @ read diagnostic register
412 mcrlt p15, 0, r10, c15, c0, 1 @ write diagnostic register
/linux-4.1.27/arch/arm/mach-imx/
Dheadsmp.S24 mcr p15, 0, r0, c15, c0, 1 @ write diagnostic register
/linux-4.1.27/arch/arm/lib/
Dxor-neon.c36 #pragma GCC diagnostic ignored "-Wunused-variable"
/linux-4.1.27/drivers/input/tablet/
Daiptek.c318 int diagnostic; /* tablet diagnostic codes */ member
477 aiptek->diagnostic = in aiptek_irq()
526 aiptek->diagnostic = AIPTEK_DIAGNOSTIC_SENDING_ABSOLUTE_IN_RELATIVE; in aiptek_irq()
529 aiptek->diagnostic = AIPTEK_DIAGNOSTIC_TOOL_DISALLOWED; in aiptek_irq()
611 aiptek->diagnostic = AIPTEK_DIAGNOSTIC_SENDING_ABSOLUTE_IN_RELATIVE; in aiptek_irq()
614 aiptek->diagnostic = AIPTEK_DIAGNOSTIC_TOOL_DISALLOWED; in aiptek_irq()
1036 aiptek->diagnostic = AIPTEK_DIAGNOSTIC_NA; in aiptek_program_tablet()
1350 switch (aiptek->diagnostic) { in show_tabletDiagnosticMessage()
1378 static DEVICE_ATTR(diagnostic, S_IRUGO, show_tabletDiagnosticMessage, NULL);
/linux-4.1.27/include/uapi/linux/
Dx25.h142 unsigned char diagnostic; member
Drose.h76 unsigned char diagnostic; member
/linux-4.1.27/arch/arm/mach-exynos/
Dsleep.S129 .long 0 @ cp15 diagnostic
/linux-4.1.27/tools/usb/
Dffs-test.c238 #pragma GCC diagnostic push in descs_to_legacy()
239 #pragma GCC diagnostic ignored "-Wdeprecated-declarations" in descs_to_legacy()
244 #pragma GCC diagnostic pop in descs_to_legacy()
/linux-4.1.27/Documentation/misc-devices/
Dlis3lv02d42 Selftest is meant only for hardware diagnostic purposes. It is not meant to be
51 Measurement values are provided to help HW diagnostic applications to make
/linux-4.1.27/Documentation/devicetree/bindings/ata/
Dapm-xgene.txt14 diagnostic memory resource.
/linux-4.1.27/include/net/
Drose.h136 unsigned char cause, diagnostic; member
/linux-4.1.27/Documentation/power/regulator/
Dmachine.txt57 for use in logging and other diagnostic output. Normally the name
/linux-4.1.27/arch/mips/include/asm/ip32/
Dmace.h177 volatile u64 diagnostic; /* RO: diagnostic register */ member
/linux-4.1.27/arch/arm/boot/dts/
Dimx51-babbage.dts119 led-diagnostic {
120 label = "diagnostic";
/linux-4.1.27/arch/powerpc/boot/dts/
Dmpc8544ds.dtsi51 label = "diagnostic-nor";
Dmpc8536ds.dtsi51 label = "diagnostic-nor";
Dp1022ds.dtsi52 label = "diagnostic-nor";
Dp2020ds.dtsi49 diagnostic@3000000 {
Dmpc8572ds.dtsi51 label = "diagnostic-nor";
/linux-4.1.27/Documentation/networking/
Dcs89x0.txt378 Once the adapter has been installed and configured, the diagnostic option of
406 The diagnostic self-test checks the adapter's basic functionality as well as
453 on the same network. (Note: the diagnostic network test should not be run
518 diagnostic self-test. Normally, the ISA resource in conflict will fail the
Dskfp.txt92 The adapter can be checked using the diagnostic program
Dvortex.txt434 3) Download you card's diagnostic tool from Donald
Darcnet.txt140 sniffing), extra diagnostic information, etc. Unfortunately, there is no
Darcnet-hardware.txt715 Two diagnostic LEDs are visible on the rear bracket of the board.
942 Two diagnostic LEDs are visible on the rear bracket of the board.
/linux-4.1.27/drivers/net/arcnet/
DKconfig113 extra diagnostic information.
/linux-4.1.27/Documentation/aoe/
Daoe.txt43 "cat /dev/etherd/err" blocks, waiting for error diagnostic output,
/linux-4.1.27/Documentation/
Dvgaarbiter.txt58 diagnostic only). "decodes" indicate what the card currently
DCodingStyle693 There are a number of driver model diagnostic macros in <linux/device.h>
Dkernel-parameters.txt2015 However, its intended as a diagnostic tool; if
/linux-4.1.27/drivers/parisc/
Dpdc_stable.c940 static PDCS_ATTR(diagnostic, 0400, pdcs_diagnostic_read, NULL);
/linux-4.1.27/Documentation/PCI/
Dpci-error-recovery.txt142 a chance to extract some diagnostic information (see
189 start operations again, only to peek/poke at the device, extract diagnostic
/linux-4.1.27/Documentation/RCU/
Dstallwarn.txt32 print out additional per-CPU diagnostic information, including
/linux-4.1.27/arch/arm/
DKconfig1089 the diagnostic register of the Cortex-A9 which causes the DMB
1104 accessing it. This workaround sets specific bits in the diagnostic
1139 corruption. This workaround sets a specific bit in the diagnostic
1202 in the diagnostic control register of the SCU.
/linux-4.1.27/Documentation/fmc/
Dcarrier.txt282 testpoints, so to make a carrier-dependent use of the diagnostic tools.
/linux-4.1.27/drivers/parport/
Dparport_ip32.c665 diag = readq(&mace->perif.ctrl.parport.diagnostic); in parport_ip32_dma_stop()
/linux-4.1.27/drivers/spi/
DKconfig662 exposing both switch control and diagnostic feedback.
/linux-4.1.27/Documentation/scsi/
DChangeLog.1992-1997219 NULL pointer panic on odd UDCs fixed, two bugs in diagnostic output
221 new memory allocation, extraneous diagnostic output suppressed,
DChangeLog.lpfc561 * Added slavecnt in lpfc_target for diagnostic purposes.
/linux-4.1.27/Documentation/block/
Dbiodoc.txt498 off the queue. Control or diagnostic functions might bypass block and directly
/linux-4.1.27/lib/
DKconfig.debug1306 period, print out additional per-CPU diagnostic information
/linux-4.1.27/arch/x86/
DKconfig1461 It is, however, intended as a diagnostic tool; if repeatable
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt3838 are diagnostic of this problem. This is a reiserfs bug which causes a