Home
last modified time | relevance | path

Searched full:faulty (Results 1 – 25 of 153) sorted by relevance

1234567

/OK3568_Linux_fs/kernel/drivers/md/
H A Dmd-faulty.c3 * faulty.c : Multiple Devices driver for Linux
12 * The "faulty" personality causes some requests to fail.
30 * persisting-faulty blocks. When a new fault is requested that would
336 .name = "faulty",
361 MODULE_ALIAS("md-personality-10"); /* faulty */
362 MODULE_ALIAS("md-faulty");
H A Dmd.h75 * Not working: faulty==1 in_sync==0
76 * Fully working: faulty==0 in_sync==1
79 * faulty==0 in_sync==0
81 * It can never have faulty==1, in_sync==1
143 Faulty, /* device is known to have a fault */ enumerator
195 * this device was known to be faulty,
577 /* error_handler must set ->faulty and clear ->in_sync
772 int faulty = test_bit(Faulty, &rdev->flags); in rdev_dec_pending() local
773 if (atomic_dec_and_test(&rdev->nr_pending) && faulty) { in rdev_dec_pending()
H A DMakefile29 faulty-y += md-faulty.o
42 obj-$(CONFIG_MD_FAULTY) += faulty.o
H A Draid10.c471 * When the device is faulty, it is not necessary to in raid10_end_write_request()
474 if (!test_bit(Faulty, &rdev->flags)) in raid10_end_write_request()
499 * rebuilding or Faulty. This is because we cannot use in raid10_end_write_request()
506 !test_bit(Faulty, &rdev->flags)) in raid10_end_write_request()
753 if (rdev == NULL || test_bit(Faulty, &rdev->flags) || in read_balance()
757 test_bit(Faulty, &rdev->flags)) in read_balance()
888 if (test_bit(Faulty, &rdev->flags)) { in flush_pending_writes()
1081 if (test_bit(Faulty, &rdev->flags)) { in raid10_unplug()
1364 if (rdev && (test_bit(Faulty, &rdev->flags))) in raid10_write_request()
1366 if (rrdev && (test_bit(Faulty, &rrdev->flags))) in raid10_write_request()
[all …]
H A Dmd-multipath.c39 !test_bit(Faulty, &rdev->flags)) { in multipath_map()
181 set_bit(Faulty, &rdev->flags); in multipath_error()
207 i,!test_bit(Faulty, &tmp->rdev->flags), in print_multipath_conf()
389 if (!test_bit(Faulty, &rdev->flags)) in multipath_run()
H A Draid1.c473 * When the device is faulty, it is not necessary to in raid1_end_write_request()
476 if (!test_bit(Faulty, &rdev->flags)) in raid1_end_write_request()
503 * rebuilding or Faulty. This is because we cannot use in raid1_end_write_request()
510 !test_bit(Faulty, &rdev->flags)) in raid1_end_write_request()
644 || test_bit(Faulty, &rdev->flags)) in read_balance()
800 if (test_bit(Faulty, &rdev->flags)) { in flush_bio_list()
1385 if (!rdev || test_bit(Faulty, &rdev->flags)) { in raid1_write_request()
1622 set_bit(Faulty, &rdev->flags); in raid1_error()
1655 !test_bit(Faulty, &rdev->flags), in print_conf()
1694 && !test_bit(Faulty, &repl->flags) in raid1_spare_active()
[all …]
H A Dmd.c580 !test_bit(Faulty, &rdev->flags)) { in submit_flushes()
961 if (!test_bit(Faulty, &rdev->flags) in super_written()
990 if (test_bit(Faulty, &rdev->flags)) in md_super_write()
1325 clear_bit(Faulty, &rdev->flags); in super_90_validate()
1420 set_bit(Faulty, &rdev->flags); in super_90_validate()
1533 test_bit(Faulty, &rdev2->flags)) in super_90_sync()
1549 if (test_bit(Faulty, &rdev2->flags)) in super_90_sync()
1567 /* now set the "removed" and "faulty" bits on any missing devices */ in super_90_sync()
1839 clear_bit(Faulty, &rdev->flags); in super_1_validate()
1961 case MD_DISK_ROLE_FAULTY: /* faulty */ in super_1_validate()
[all …]
/OK3568_Linux_fs/kernel/drivers/staging/media/omap4iss/
H A Diss_ipipeif.h43 * @fpc_en: Faulty pixels correction enabled (1) or disabled (0)
46 * @fpc: Faulty pixels correction configuration
/OK3568_Linux_fs/buildroot/boot/grub2/
H A D0040-mmap-Don-t-register-cutmem-and-badram-commands-when-.patch55 - N_("Declare memory regions as faulty (badram)."));
61 + N_("Declare memory regions as faulty (badram)."));
/OK3568_Linux_fs/kernel/drivers/gpu/arm/bifrost/jm/
H A Dmali_kbase_jm_defs.h149 * completed after the faulty atom but before the
150 * debug data for faulty atom was dumped.
155 * completed after the faulty atom.
156 * @job_fault_work: work item, queued only for the faulty atom, which waits for
158 * of job done for the atoms which followed the faulty atom.
160 * faulty atoms or context specific list of atoms which got
163 * for the faulty atom.
/OK3568_Linux_fs/kernel/drivers/media/platform/omap3isp/
H A Dispccdc.h110 * @fpc_en: Faulty pixels correction enabled (1) or disabled (0)
113 * @fpc: Faulty pixels correction configuration
/OK3568_Linux_fs/kernel/Documentation/admin-guide/
H A Dmd.rst195 raid5, linear, multipath, faulty.
254 For arrays with data redundancy (i.e. not raid0, linear, faulty,
455 faulty
474 it were not faulty are blocked.
499 Writing ``faulty`` simulates a failure on the device.
528 This file responds to select/poll. Any change to ``faulty``
/OK3568_Linux_fs/kernel/drivers/gpu/arm/bifrost/backend/gpu/
H A Dmali_kbase_model_error_generator.c56 /* pick up a faulty mmu address space */ in gpu_generate_error()
154 /* found a faulty atom matching with the in midgard_set_error()
H A Dmali_kbase_model_dummy.h101 * the function below is used to trigger the simulation of a faulty
124 /* struct to track faulty atoms */
/OK3568_Linux_fs/u-boot/drivers/crypto/fsl/
H A Dfsl_hash.c188 printf("CAAM was not setup properly or it is faulty\n"); in hw_sha256()
195 printf("CAAM was not setup properly or it is faulty\n"); in hw_sha1()
/OK3568_Linux_fs/u-boot/drivers/crypto/
H A Dace_sha.c107 debug("ACE was not setup properly or it is faulty\n"); in hw_sha256()
114 debug("ACE was not setup properly or it is faulty\n"); in hw_sha1()
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/power/supply/
H A Drohm,bd99954.yaml102 # battery is expected to be faulty if battery voltage exceeds this limit.
103 # Charger will then enter to a "battery faulty" -state
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-benchmark/memtester/
H A Dmemtester_4.5.1.bb1 SUMMARY = "Utility to test for faulty memory subsystem"
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/linux/raid/
H A Dmd_p.h78 #define MD_DISK_FAULTY 0 /* disk is faulty / operational */
303 * into the 'roles' value. If a device is spare or faulty, then it doesn't
306 __le16 dev_roles[0]; /* role in array, or 0xffff for a spare, or 0xfffe for faulty */
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/linux/raid/
H A Dmd_p.h78 #define MD_DISK_FAULTY 0 /* disk is faulty / operational */
303 * into the 'roles' value. If a device is spare or faulty, then it doesn't
306 __le16 dev_roles[0]; /* role in array, or 0xffff for a spare, or 0xfffe for faulty */
/OK3568_Linux_fs/kernel/include/uapi/linux/raid/
H A Dmd_p.h78 #define MD_DISK_FAULTY 0 /* disk is faulty / operational */
303 * into the 'roles' value. If a device is spare or faulty, then it doesn't
306 __le16 dev_roles[0]; /* role in array, or 0xffff for a spare, or 0xfffe for faulty */
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/location/declarativemaps/
H A Dqdeclarativegeomapitemutils.cpp73 // is faulty -- probably best thing to do is abort in wrapPath()
118 // is faulty -- probably best thing to do is abort in wrapPath()
/OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/netronome/
H A Dnfp.rst170 alignment errors. The cause is usually faulty cables or SFPs.
214 * An error on the MAC/physical layer. Usually due to faulty cables or
/OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/dpkg/dpkg/
H A Darch_pm.patch3 because of faulty code added to Arch.pm in the latest
/OK3568_Linux_fs/u-boot/post/drivers/
H A Dmemory.c17 * This sequence also helps isolate and identify what is faulty.
82 * map (related by the faulty address line) mapping to one physical
109 * not "mirrored" onto the base address due to a faulty address line.

1234567