/openbmc/linux/drivers/s390/scsi/ |
H A D | zfcp_diag.c | 5 * Functions to handle diagnostics. 23 * zfcp_diag_adapter_setup() - Setup storage for adapter diagnostics. 24 * @adapter: the adapter to setup diagnostics for. 26 * Creates the data-structures to store the diagnostics for an adapter. This 27 * overwrites whatever was stored before at &zfcp_adapter->diagnostics! 32 * &zfcp_adapter->diagnostics remains unchanged 63 adapter->diagnostics = diag; in zfcp_diag_adapter_setup() 68 * zfcp_diag_adapter_free() - Frees all adapter diagnostics allocations. 71 * Frees all data-structures in the given adapter that store diagnostics 72 * information. Can savely be called with partially setup diagnostics. [all …]
|
H A D | zfcp_diag.h | 5 * Definitions for handling diagnostics in the zfcp device driver. 41 * struct zfcp_diag_adapter - central storage for all diagnostics concerning an
|
H A D | zfcp_sysfs.c | 352 rc = scnprintf(buf, 20 + 2, "%lu\n", adapter->diagnostics->max_age); in zfcp_sysfs_adapter_diag_max_age_show() 374 adapter->diagnostics->max_age = max_age; in zfcp_sysfs_adapter_diag_max_age_store() 832 diag_hdr = &adapter->diagnostics->config_data.header; in zfcp_sysfs_adapter_diag_b2b_credit_show() 842 adapter->diagnostics->config_data in zfcp_sysfs_adapter_diag_b2b_credit_show() 882 diag_hdr = &adapter->diagnostics->port_data.header; \ 892 adapter->diagnostics->port_data.data._qtcb_member); \ 929 .name = "diagnostics",
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/conf/machine/ |
H A D | corstone1000-fvp.conf | 36 FVP_CONFIG[diagnostics] ?= "4" 56 FVP_CONFIG[board.msd_mmc.diagnostics] ?= "0" 65 FVP_CONFIG[board.msd_mmc_2.diagnostics] ?= "0"
|
/openbmc/linux/Documentation/trace/coresight/ |
H A D | coresight-tpda.rst | 4 The trace performance monitoring and diagnostics aggregator(TPDA) 13 TPDA - The trace performance monitoring and diagnostics aggregator or 15 performance monitoring and diagnostics network specification.
|
H A D | coresight-tpdm.rst | 4 Trace performance monitoring and diagnostics monitor(TPDM) 12 TPDM - The trace performance monitoring and diagnostics monitor or TPDM in
|
/openbmc/openbmc/meta-evb/meta-evb-arm/meta-evb-fvp-base/conf/machine/ |
H A D | fvp-config.inc | 39 FVP_CONFIG[bp.virtio_rng.diagnostics] = "1" 46 FVP_CONFIG[bp.mmc.diagnostics]="0x1"
|
/openbmc/linux/arch/sparc/kernel/ |
H A D | sbus.c | 41 #define IOMMU_TAGCMP (0x4408UL - 0x2400UL) /* TLB tag compare diagnostics */ 42 #define IOMMU_LRUDIAG (0x4500UL - 0x2400UL) /* IOMMU LRU queue diagnostics */ 43 #define IOMMU_TAGDIAG (0x4580UL - 0x2400UL) /* TLB tag diagnostics */ 44 #define IOMMU_DRAMDIAG (0x4600UL - 0x2400UL) /* TLB data RAM diagnostics */ 54 #define STRBUF_ERRDIAG (0x5400UL - 0x2800UL) /* error status diagnostics */ 55 #define STRBUF_PTAGDIAG (0x5800UL - 0x2800UL) /* Page tag diagnostics */ 56 #define STRBUF_LTAGDIAG (0x5900UL - 0x2800UL) /* Line tag diagnostics */ 632 /* Clear out the tags using diagnostics. */ in sbus_iommu_init()
|
/openbmc/linux/drivers/hid/ |
H A D | hid-elo.c | 25 #define ELO_DIAG 0x64 /* Diagnostics command */ 149 /* send Diagnostics command */ in elo_work() 153 dev_err(&dev->dev, "send Diagnostics Command failed, error %d\n", in elo_work() 161 dev_err(&dev->dev, "get Diagnostics Command response failed, error %d\n", in elo_work()
|
/openbmc/u-boot/cmd/ |
H A D | diag.c | 8 * Diagnostics support 52 "perform board diagnostics",
|
/openbmc/openbmc/poky/meta/recipes-devtools/icecc-toolchain/icecc-toolchain/ |
H A D | icecc-env.sh | 37 CFLAGS="$CFLAGS -fno-diagnostics-show-caret" 38 CXXFLAGS="$CXXFLAGS -fno-diagnostics-show-caret"
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/cirrus/ |
H A D | cs89x0.rst | 384 adapter and its network connection. Use the diagnostics 'Self Test' option to 386 assigned. You can use the diagnostics 'Network Test' to test the ability of the 393 The Setup Utility's diagnostics are designed to run in a 394 DOS-only operating system environment. DO NOT run the diagnostics 398 To run the diagnostics tests on the CS8900/20 adapter: 405 4. Select 'Diagnostics' (ALT-G) from the main menu. 486 and select 'Diagnostics -> Network Test -> Responder' from the main 537 resource in conflict. Run the diagnostics again to check for further IO 543 diagnostics self-test to ensure the new configuration is free of conflicts
|
/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | adi,adau1977.yaml | 7 title: Analog Devices ADAU1977/ADAU1978/ADAU1979 Quad ADC with Diagnostics 14 Analog Devices ADAU1977 and similar quad ADC with Diagnostics
|
/openbmc/linux/drivers/scsi/aic7xxx/ |
H A D | Kconfig.aic79xx | 79 bool "Decode registers during diagnostics" 84 contents in diagnostics. This make it much easier to understand debug
|
H A D | Kconfig.aic7xxx | 84 bool "Decode registers during diagnostics" 89 contents in diagnostics. This make it much easier to understand debug
|
/openbmc/qemu/hw/pci-host/ |
H A D | sabre.c | 187 case 0x5000 ... 0x51cf: /* PIO/DMA diagnostics */ in sabre_config_write() 188 case 0xa400 ... 0xa67f: /* IOMMU diagnostics */ in sabre_config_write() 189 case 0xa800 ... 0xa80f: /* Interrupt diagnostics */ in sabre_config_write() 230 case 0x5000 ... 0x51cf: /* PIO/DMA diagnostics */ in sabre_config_read() 231 case 0xa400 ... 0xa67f: /* IOMMU diagnostics */ in sabre_config_read() 232 case 0xa800 ... 0xa80f: /* Interrupt diagnostics */ in sabre_config_read()
|
/openbmc/openbmc/poky/meta/recipes-extended/tcp-wrappers/tcp-wrappers-7.6/ |
H A D | try-from.8 | 14 on top of IP heuristics work. Diagnostics are reported through
|
/openbmc/openpower-hw-diags/ |
H A D | README.md | 1 # Hardware Diagnostics for POWER Systems
|
/openbmc/linux/arch/powerpc/platforms/powernv/ |
H A D | Kconfig | 27 recovery diagnostics on OpenPower machines
|
/openbmc/linux/Documentation/networking/devlink/ |
H A D | devlink-health.rst | 34 * Diagnostics procedures 82 * Run diagnostics
|
/openbmc/u-boot/include/configs/ |
H A D | ap121.h | 40 * Diagnostics
|
H A D | ap143.h | 44 * Diagnostics
|
H A D | tplink_wdr4300.h | 54 * Diagnostics
|
/openbmc/u-boot/lib/libavb/ |
H A D | avb_version.h | 28 * Boot loaders should display this string in debug/diagnostics output
|
/openbmc/docs/ |
H A D | features.md | 38 - [Hardware Diagnostics][] for POWER Systems fatal hardware errors. 59 [hardware diagnostics]:
|