| commit | 2eba1fc659515b5a8c87492954c21a6feb98867c | [log] [tgz] |
|---|---|---|
| author | Yvonne Yip <yky@google.com> | Thu Jun 14 19:30:03 2018 -0700 |
| committer | Yvonne Yip <ykyyip@google.com> | Fri Jun 15 17:24:41 2018 +0000 |
| tree | 7b6e037bc89f7379e16b7c28a014820371553803 | |
| parent | 02fdd8c3715419e55bed16d28216d3ed2be20164 [diff] |
[dev][intel-hda][dsp] keep FW pinned until it is loaded The FW VMO was getting unpinned while the code loader DMA was in progress, because the PinnedVmo object was destroyed on function return from IntelDspCodeLoader::TransferFirmware() which is not responsible for DMA completion wait. Move the PinnedVmo object to the function that waits for firmware load success (implies DMA completion), so the memory stays pinned. Change-Id: I207a7ca6a68a448011eea6829251c2040d29d986
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
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/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.