| commit | 466813a041c29650848ec5327215ffbac167b4ae | [log] [tgz] |
|---|---|---|
| author | Mike Voydanoff <voydanoff@google.com> | Mon Mar 12 07:33:08 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Mar 15 01:20:48 2018 +0000 |
| tree | 1bd2803a26323aed1ac5e67cfe63956f2349a1d9 | |
| parent | 311695c35e32d33a4182e44ea67f78237c98d1b0 [diff] |
[ddk][serial] Move serial protocol support out of platform bus driver Instead of implementing UARTs as platform device resources in platform bus, We now have a generic serial driver that implements ZX_PROTOCOL_SERIAL on top of the lower level ZX_PROTOCOL_SERIAL_IMPL protocol. This allows the possibility of using the generic seral protocol support on x86 as well as SOC based platforms. In order to make this work, we add some new generic device properties to our binding rules: BIND_DEVICE_VID, BIND_DEVICE_PID and BIND_DEVICE_CLASS. In this CL we use BIND_DEVICE_CLASS to specify the serial port type (for example Bluetooth HCI versus generic serial port) and BIND_DEVICE_VID and BIND_DEVICE_PID to specify which Bluetooth firmware to use in the case of HCI. We also simplify the serial protocols by eliminating port numbers from the APIs. Now serial drivers support only one serial port each, so we now have separate driver instances per serial port. This is necessary to maintain the flexibility of running serial port clients in separate devhosts after decoupling from the platform bus. Change-Id: Ife2c611a1340ec99440595e45d79bdcf63979644
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.