commit | 99ed3be31c1f974bdd722570a38281585c29a31e | [log] [tgz] |
---|---|---|
author | Jocelyn Dang <jocelyndang@google.com> | Fri Jan 25 16:25:22 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jan 29 00:20:01 2019 +0000 |
tree | 8096a6e7845b5e937d2000f98defdc92da5e93c6 | |
parent | 4b1dfd3f0508b009695d60bdde09ed73c39da296 [diff] |
[usb-bus] Opt out of USB callbacks part 1 Handles the simple case where all requests complete successfully. Remove old batch_cb API. Also modifies testing so we can specify when we want to set or expect a callback. Currently those fields are equal in the tests, but will not necessarily be when we start testing with set_error=true. Part 2 will track queued / silently completed requests and handle callbacks for the error cases. ZX-932 #comment TEST= plug in FX3 and run: fx shell usb-fwloader && runtests -t usb-test Change-Id: I596c18b3e0edac25638214977e3668b4efccbe38
Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
The Zircon Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.