| commit | 3ab16f4f71a4c0d56719d9e8d7dfcd53e0003eee | [log] [tgz] |
|---|---|---|
| author | Andres Oportus <andresoportus@google.com> | Wed Sep 19 09:10:14 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Sep 19 23:03:08 2018 +0000 |
| tree | 5c2a6d9e870db769901cfa892db80b1c34441d52 | |
| parent | 0901c1cb4cc1ce4f3b2bb88590e6648e2af35eab [diff] |
[ddk][i2c] Refactor the I2C protocol This change is similar to "[gpio] Refactor the GPIO protocol" but for I2C channels: https://fuchsia-review.googlesource.com/c/zircon/+/199400 After this change an instance of the ZX_PROTOCOL_I2C protocol now represents a single I2C channel. The protocol remains the same, except the "uint32_t index" has been removed from all the protocol functions. For devices that have only one I2C channel assigned to them, the driver can simply call device_get_protocol() to access the I2C protocol for the channel. To support multiple channel, a new API in the platform bus called pdev_get_protocol() allows accessing the I2C channels protocols by index. ZX-2621 #comment Refactor the I2C protocol removing index. Test: Boot and I2C transactions work on astro and NXP IMX8 Change-Id: I55d08aa3d82024f6977646425fd3d75a378f2740
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.