Searched refs:failures (Results 1 – 19 of 19) sorted by relevance
| /rk3399_rockchip-uboot/drivers/i2c/ |
| H A D | i2c-gpio.c | 210 int failures = 0; in i2c_gpio_write_data() local
221 failures++; in i2c_gpio_write_data()
226 return failures; in i2c_gpio_write_data()
234 return failures; in i2c_gpio_write_data()
|
| H A D | soft_i2c.c | 407 int shift, failures = 0; in soft_i2c_write() local
429 failures++; in soft_i2c_write()
433 return(failures); in soft_i2c_write()
|
| /rk3399_rockchip-uboot/tools/buildman/ |
| H A D | buildman | 51 for test, err in result.failures:
|
| H A D | buildman.py | 51 for test, err in result.failures:
|
| H A D | README | 574 see which ones). But still we can see a few failures. The galaxy5200_LOWBOOT
|
| /rk3399_rockchip-uboot/tools/dtoc/ |
| H A D | dtoc.py | 53 for _, err in result.failures:
|
| H A D | dtoc | 53 for _, err in result.failures:
|
| /rk3399_rockchip-uboot/tools/binman/ |
| H A D | binman.py | 55 for test, err in result.failures:
|
| H A D | binman | 55 for test, err in result.failures:
|
| /rk3399_rockchip-uboot/drivers/bootcount/ |
| H A D | Kconfig | 42 default "/boot/failures"
|
| /rk3399_rockchip-uboot/tools/patman/ |
| H A D | patman.py | 101 for test, err in result.failures:
|
| H A D | patman | 101 for test, err in result.failures:
|
| /rk3399_rockchip-uboot/drivers/mtd/ubi/ |
| H A D | wl.c | 1445 int failures = 0; local
1475 if (failures++ > WL_MAX_FAILURES) {
1487 failures = 0;
|
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.memory-test | 52 failures (system crashes).
|
| H A D | README.generic-board | 125 ARM, PPC and x86 boards. There are a few failures due to errors in
|
| H A D | README.POST | 333 The Linux kernel will be modified to detect power failures and
|
| /rk3399_rockchip-uboot/drivers/misc/ |
| H A D | Kconfig | 216 Security Monitor can be transitioned on any security failures,
|
| /rk3399_rockchip-uboot/ |
| H A D | Kconfig | 269 failures.
|
| /rk3399_rockchip-uboot/arch/x86/ |
| H A D | Kconfig | 321 detecting obvious failures.
|