Home
last modified time | relevance | path

Searched full:good (Results 1 – 25 of 222) sorted by relevance

123456789

/Zephyr-latest/samples/drivers/soc_flash_nrf/
DREADME.rst50 Data read matches data written. Good!
54 Data read matches data written. Good!
58 Data read matches data written. Good!
62 Data read matches data written. Good!
71 Data read matches data written. Good!
75 Data read matches data written. Good!
79 Data read matches data written. Good!
83 Data read matches data written. Good!
92 Data read matches data written. Good!
96 Data read matches data written. Good!
[all …]
Dsample.yaml22 - "Data read matches data written. Good!"
25 - "Data read matches data written. Good!"
29 - "Data read matches data written. Good!"
/Zephyr-latest/scripts/tests/twister/
Dtest_quarantine.py183 'good scenario',
184 'good platform',
185 'good arch',
186 'good sim',
190 'good scenario',
192 'good arch',
193 'good sim',
198 'good platform',
199 'good arch',
205 'good platform',
[all …]
/Zephyr-latest/tests/drivers/charger/sbs_charger/src/
Dtest_sbs_charger.c42 zassert_equal(ret, -ENOTSUP, "Getting bad property %d has a good status.", prop); in ZTEST_USER_F()
53 zassert_equal(ret, 0, "Getting good property %d has a good status.", prop); in ZTEST_USER_F()
64 zassert_equal(ret, -ENOTSUP, "Setting bad property %d has a good status.", prop); in ZTEST_USER_F()
71 zassert_equal(ret, 0, "Enabling charge has a good status."); in ZTEST_USER_F()
/Zephyr-latest/tests/bsim/bluetooth/host/security/ccc_update/src/
Dperipheral.c174 /* wait for confirmation of subscribtion from good client */ in connect_pair_check_subscribtion()
179 FAIL("Good client did not subscribed\n"); in connect_pair_check_subscribtion()
184 /* confirm to good client that the subscribtion has been well registered */ in connect_pair_check_subscribtion()
226 /* wait for good client end of security update */ in connect_restore_sec_check_subscribtion()
231 FAIL("Good client is subscribed\n"); in connect_restore_sec_check_subscribtion()
234 /* confirm to good client that the subscribtion has been well restored */ in connect_restore_sec_check_subscribtion()
236 /* wait for confimation of unsubscribtion from good client */ in connect_restore_sec_check_subscribtion()
239 /* check that unsubscribtion request from good client has been registered */ in connect_restore_sec_check_subscribtion()
241 FAIL("Good client did not unsubscribe\n"); in connect_restore_sec_check_subscribtion()
/Zephyr-latest/tests/bsim/bluetooth/host/att/pipeline/dut/src/
Dmain.c268 LOG_DBG("Test 0 start: good peer"); in good_peer_procedure()
288 PASS("Good peer done\n"); in good_peer_procedure()
296 struct bt_conn *good, *bad; in dut_procedure() local
302 LOG_DBG("Central: Connect to good peer"); in dut_procedure()
303 good = connect(); in dut_procedure()
332 * The good peer uses the Zephyr host to send requests. in test_procedure_0()
337 * The connection with the good peer must remain stable. in test_procedure_0()
341 * - Good peer sends valid ATT write requests to DUT in test_procedure_0()
342 * - Good peer validates ATT responses from DUT in test_procedure_0()
346 * - no buffer allocation failures for responding to the good peer, in test_procedure_0()
/Zephyr-latest/scripts/pylib/pytest-twister-harness/tests/helpers/
Dshell_mcuboot_command_parser_test.py18 magic: good
47 magic: good
/Zephyr-latest/samples/subsys/usb/dfu/
DREADME.rst84 I: Primary image: magic=good, swap_type=0x3, copy_done=0x1, image_ok=0x1
85 I: Secondary image: magic=good, swap_type=0x2, copy_done=0x3, image_ok=0x3
101 I: Primary image: magic=good, swap_type=0x2, copy_done=0x1, image_ok=0x3
146 I: Primary image: magic=good, swap_type=0x4, copy_done=0x1, image_ok=0x1
147 I: Secondary image: magic=good, swap_type=0x3, copy_done=0x3, image_ok=0x1
/Zephyr-latest/boards/shields/waveshare_epaper/doc/
Dindex.rst50 | Good Display | HINK-E0213 | SSD1673 / | waveshare_epaper_gdeh0213b1 |
53 | Good Display | HINK-E0213A22 | SSD1675A / | waveshare_epaper_gdeh0213b72 |
56 | Good Display | E029A01 | SSD1608 / | waveshare_epaper_gdeh029a1 |
59 | Good Display | WFT0583CZ61 | UC8179 / | waveshare_epaper_gdew075t7 |
62 | Good Display | HINK-E0154A07 | SSD1681 / | waveshare_epaper_gdeh0154a07 |
65 | Good Display | WFT0420CZ15 | UC8176 / | waveshare_epaper_gdew042t2 |
68 | Good Display | FPC-A002 | SSD1680 / | waveshare_epaper_gdey0213b74 |
/Zephyr-latest/samples/drivers/mspi/mspi_flash/
Dsample.yaml21 - "Data read matches data written. Good!!"
/Zephyr-latest/tests/bsim/bluetooth/host/l2cap/reassembly/dut/
Dprj.conf28 # RX buffer pool, it is a good idea to constrain said buffer
/Zephyr-latest/include/zephyr/dt-bindings/usb/
Dusb.h10 * however, we dont have a good way to know how to name such an enum from
/Zephyr-latest/samples/drivers/spi_flash/
Dsample.yaml23 - "Data read matches data written. Good!!"
/Zephyr-latest/subsys/usb/device_next/class/
Dusbd_msc_scsi.c349 static size_t good(struct scsi_ctx *ctx, size_t data_in_bytes) in good() function
351 ctx->status = GOOD; in good()
409 return good(ctx, 0); in SCSI_CMD_HANDLER()
449 return good(ctx, length); in SCSI_CMD_HANDLER()
564 return good(ctx, ret); in SCSI_CMD_HANDLER()
587 return good(ctx, length); in SCSI_CMD_HANDLER()
615 return good(ctx, 0); in SCSI_CMD_HANDLER()
633 return good(ctx, 0); in SCSI_CMD_HANDLER()
663 return good(ctx, length); in SCSI_CMD_HANDLER()
684 return good(ctx, sizeof(r)); in SCSI_CMD_HANDLER()
[all …]
/Zephyr-latest/drivers/espi/
DKconfig.espi_emul18 specification for more details (it is good for the introduction as well)
/Zephyr-latest/dts/bindings/sensor/
Dwe,wsen-hids-2525020210002.yaml23 Defaults to mid, which is a good compromise between
Dti,ina23x-common.yaml24 while keeping a good measurement resolution. The units are in uA/LSB
/Zephyr-latest/scripts/pylib/pytest-twister-harness/tests/resources/
Dzen_of_python.py27 If the implementation is easy to explain, it may be a good idea.
/Zephyr-latest/include/zephyr/dt-bindings/battery/
Dbattery.h8 * but should provide a good baseline. These curves will also be affected by ambient temperature
/Zephyr-latest/doc/connectivity/networking/
Dqemu_user_setup.rst56 with good defaults that work for all. Therefore, Zephyr Implementation
78 good choice. However, it has several limitations
/Zephyr-latest/include/zephyr/linker/
Dkobject-text.ld27 second argument below, but to give the user a good error message
/Zephyr-latest/tests/drivers/can/timing/
DKconfig31 CiA 601-3 recommends the following CAN FD core clock frequencies for good node
/Zephyr-latest/subsys/modem/backends/
DKconfig34 A good value is ~90% the time it takes to fill half the receive buffer.
/Zephyr-latest/scripts/west_commands/zspdx/
Dsbom.py46 # directory exists, we're good
57 # file exists, we're good
/Zephyr-latest/doc/services/
Dnotify.rst9 often a good method, but some application architectures may be more

123456789