commit | ad54958afeb67a9bbb0e438b59dbac0079c4ad19 | [log] [tgz] |
---|---|---|
author | Braden Kell <bradenkell@google.com> | Fri Jan 25 12:05:23 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Jan 25 21:02:39 2019 +0000 |
tree | ab858479c55fd826382bffe469b9357c52f95f13 | |
parent | f6edcad5ceb768f3baa0979783ec7e2652fb3ad9 [diff] |
[mt8167][sdmmc] Set clock mode when initializing Set the clock mode to single data rate in Init(). After paving it could still be set to DDR which causes block reads to return garbage. Test: 'lsblk' works after paving. Test: runtests -t mtk-sdmmc-test Change-Id: I61d94b38e24e4c0788fb8ce63c5ce54f7ab77a2b
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.