/Zephyr-latest/subsys/usb/device_next/class/ |
D | usbd_msc_scsi.c | 349 static size_t good(struct scsi_ctx *ctx, size_t data_in_bytes) in good() function 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() 743 return good(ctx, 0); in SCSI_CMD_HANDLER() [all …]
|
/Zephyr-latest/samples/subsys/usb/dfu/ |
D | README.rst | 84 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/drivers/espi/ |
D | Kconfig.espi_emul | 18 specification for more details (it is good for the introduction as well)
|
/Zephyr-latest/include/zephyr/linker/ |
D | kobject-text.ld | 27 second argument below, but to give the user a good error message
|
/Zephyr-latest/tests/drivers/can/timing/ |
D | Kconfig | 31 CiA 601-3 recommends the following CAN FD core clock frequencies for good node
|
/Zephyr-latest/samples/net/lldp/ |
D | README.rst | 24 A good way to run this sample LLDP application is inside QEMU,
|
/Zephyr-latest/subsys/modem/backends/ |
D | Kconfig | 34 A good value is ~90% the time it takes to fill half the receive buffer.
|
/Zephyr-latest/doc/templates/ |
D | sample.tmpl | 3 :relevant-api: space-separated list of Doxygen groups of APIs this sample is a good showcase of
|
/Zephyr-latest/samples/net/stats/ |
D | README.rst | 24 A good way to run this sample application is with QEMU or native_sim board
|
/Zephyr-latest/doc/services/ |
D | notify.rst | 9 often a good method, but some application architectures may be more
|
/Zephyr-latest/doc/safety/ |
D | safety_requirements.rst | 91 Characteristics of a good requirement 117 * `EARS <https://alistairmavin.com/ears/>`_ is a good reference. Particularly if you are
|
/Zephyr-latest/doc/connectivity/networking/ |
D | qemu_user_setup.rst | 56 with good defaults that work for all. Therefore, Zephyr Implementation 78 good choice. However, it has several limitations
|
/Zephyr-latest/tests/bsim/bluetooth/host/att/pipeline/dut/src/ |
D | main.c | 296 struct bt_conn *good, *bad; in dut_procedure() local 303 good = connect(); in dut_procedure()
|
/Zephyr-latest/samples/net/ptp/ |
D | README.rst | 24 A good way to run this sample is to run this PTP application inside
|
/Zephyr-latest/tests/bsim/bluetooth/host/misc/sample_test/ |
D | CMakeLists.txt | 27 # It is a good idea to have one file per test role / entry point.
|
/Zephyr-latest/samples/net/vlan/ |
D | README.rst | 24 A good way to run this VLAN application is with QEMU as described in
|
/Zephyr-latest/samples/net/sockets/coap_server/ |
D | README.rst | 35 These resources allow a good part of the ETSI test cases to be run
|
/Zephyr-latest/drivers/watchdog/ |
D | Kconfig.nxp_fs26 | 40 also good, the fault error counter is decremented by 1. Each time
|
/Zephyr-latest/scripts/ |
D | checkpatch.pl | 4500 my $good = $fix_elements[$n] . $fix_elements[$n + 1]; 4562 $good = $fix_elements[$n] . trim($fix_elements[$n + 1]) . " "; 4580 $good = rtrim($fix_elements[$n]) . trim($fix_elements[$n + 1]); 4609 $good = rtrim($fix_elements[$n]) . trim($fix_elements[$n + 1]); 4611 $good = $fix_elements[$n] . trim($fix_elements[$n + 1]); 4614 $good .= " "; 4632 $good = $fix_elements[$n] . " " . ltrim($fix_elements[$n + 1]); 4643 $good = $fix_elements[$n] . rtrim($fix_elements[$n + 1]); 4656 $good = $fix_elements[$n] . trim($fix_elements[$n + 1]) . " "; 4664 $good = rtrim($fix_elements[$n]) . trim($fix_elements[$n + 1]); [all …]
|
/Zephyr-latest/boards/atmel/sam0/samr21_xpro/doc/ |
D | index.rst | 113 is a good value to start with. 156 Another good test can be done with IPv6 by using the server/client
|
/Zephyr-latest/cmake/modules/ |
D | user_cache.cmake | 81 # is good practice to have clean git repositories.
|
/Zephyr-latest/boards/m5stack/m5stack_atoms3/doc/ |
D | index.rst | 58 Before powering up your M5Stack AtomS3, please make sure that the board is in good
|
/Zephyr-latest/samples/bluetooth/extended_adv/ |
D | README.rst | 21 This sample handles all actions in a separate thread, to promote good design
|
/Zephyr-latest/boards/m5stack/m5stack_atom_lite/doc/ |
D | index.rst | 56 Before powering up your M5Stack ATOM Lite, please make sure that the board is in good
|
/Zephyr-latest/boards/m5stack/m5stack_atoms3_lite/doc/ |
D | index.rst | 56 Before powering up your M5Stack AtomS3 Lite, please make sure that the board is in good
|