| /system/fidl/fuchsia-sysmem/ |
| A D | image_formats.fidl | 7 // Describes how an image is represented.
60 // Describes how the pixels within an image are represented.
69 // The ordering of the channels in the format name reflects how
82 // Describes how the pixels within an image are meant to be presented.
|
| A D | allocator.fidl | 14 // |bufferCount| indicates how many buffers to allocate, between 1 and 64.
17 // |usage| describes how the client intends to access the buffers.
37 // |bufferCount| indicates how many buffers to allocate, between 1 and 64.
76 // account how the client intends to use the buffers.
78 // |usage| describes how the client intends to access the buffers.
|
| A D | formats.fidl | 7 // Describes how the contents of buffers are represented.
|
| A D | usages.fidl | 7 // Describes how a client will access the contents of a buffer.
|
| A D | collections.fidl | 13 // Describes how the contents of buffers are represented.
|
| /system/uapp/trace-example/ |
| A D | README.md | 5 just to show how it's done.
|
| /system/utest/perftest/ |
| A D | README.md | 10 For examples of how to use the testing framework, as well as coding guidelines,
|
| /system/uapp/trace-benchmark/ |
| A D | README.md | 4 Measures how long it takes to perform certain time-sensitive operations related
|
| /system/banjo/ddk-protocol-badblock/ |
| A D | bad-block.banjo | 15 /// equal to 0 in order to determine how large the |bad_blocks| is.
|
| /system/ulib/unittest/ |
| A D | README.md | 37 Unittest do their own parsing, one issue is how to support both Unittest
51 If `--foo` is a Unittest option, how does the testcase know to
|
| /system/ulib/fdio/ |
| A D | null.c | 121 zx_status_t fdio_default_shutdown(fdio_t* io, int how) { in fdio_default_shutdown() argument
|
| A D | private.h | 75 zx_status_t (*shutdown)(fdio_t* io, int how);
225 zx_status_t fdio_default_shutdown(fdio_t* io, int how);
|
| A D | socket.c | 326 static zx_status_t fdio_socket_shutdown(fdio_t* io, int how) { in fdio_socket_shutdown() argument
332 switch (how) { in fdio_socket_shutdown()
|
| A D | zxio.c | 822 static zx_status_t fdio_zxio_pipe_shutdown(fdio_t* io, int how) { in fdio_zxio_pipe_shutdown() argument
824 switch (how) { in fdio_zxio_pipe_shutdown()
|
| /system/dev/nand/aml-rawnand/ |
| A D | README | 5 specifics on how to do that). The controller driver uses polling with
|
| /system/fidl/fuchsia-crash/ |
| A D | crash.fidl | 44 // The |language| might influenced how the exception message or stack trace
|
| /system/fidl/fuchsia-hardware-nand/ |
| A D | ram-nand.fidl | 42 // Defines how a newly created ram-nand volume should operate.
|
| /system/fidl/fuchsia-ldsvc/ |
| A D | ldsvc.fidl | 31 // configuration. This is intended to affect how later
|
| /system/fidl/fuchsia-hardware-tee/ |
| A D | tee.fidl | 50 // calculate how large that output buffer should be, they can attempt the operation with a
|
| /system/fidl/fuchsia-hardware-display/ |
| A D | display-controller.fidl | 76 // An ImageConfig accompanies image data and defines how to interpret that data.
184 // SetLayerImage for details on how the active image is defined. Note the
274 // See the documentation on SetLayerImage for details on how this method
311 // See the documentation on SetLayerImage for details on how this method
|
| /system/fidl/fuchsia-tracelink/ |
| A D | tracelink.fidl | 24 // records get dropped depends on how fast TraceManager is able to save
|
| /system/ulib/cobalt-client/ |
| A D | README.md | 20 // The collector also needs to define how it should behave when attempting
|
| /system/ulib/zircon-internal/include/lib/zircon-internal/device/cpu-trace/ |
| A D | skylake-misc-events.inc | 105 // Not sure how to display it (could split it into individual pieces but
|
| /system/fidl/fuchsia-io/ |
| A D | io.fidl | 45 // Describes how the connection to the Object should be handled, as well as
46 // how to interpret the optional handle.
|
| /system/fidl/fuchsia-device-manager/ |
| A D | coordinator.fidl | 144 // TODO(teisenbe): We should revisit how these are carried over.
|