commit | 8ef8f00cc869658870099d98a815298eac53b847 | [log] [tgz] |
---|---|---|
author | Andres Oportus <andresoportus@google.com> | Mon Jan 28 13:56:37 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Jan 28 23:53:18 2019 +0000 |
tree | 84f85f1501b15ee08e451b445ee11ef8a6fb51c8 | |
parent | 104d10becc9f040939e6a3c1005bce1971ebf697 [diff] |
[mt8167][gpio] Move binding to use file for unit testing In order to use mt8167-gpio.cpp in unit tests, the binding for the regular devmgr needs to be done in a different file. Test: Boot on MT8167 ref board. Change-Id: I3fe3aa05bfae11c707199b2b970fbe1f526f5a1e
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.