Lines Matching refs:ion
23 #include <ion/ion.h>
53 /* ========================================= ION HANDLE ======================================== */
55 * ION handle
57 * There can be only a sole ion client per process, this is captured in the ion fd that is passed
58 * to the constructor, but this should be managed by the ion buffer allocator/mapper.
60 * ion uses ion_user_handle_t for buffers. We don't store this in the native handle as
68 // ion handle owns ionFd(!) and bufferFd
84 int mBuffer; // shared ion buffer
120 // TODO: is the dup of an ion fd identical to ion_share?
122 /* ======================================= ION ALLOCATION ====================================== */
153 * Constructs an ion allocation.
155 * \note We always create an ion allocation, even if the allocation or import fails
158 * \param ionFd ion client (ownership transferred to created object)
162 * \param buffer ion buffer user handle (ownership transferred to created object). Must be
186 * Constructs an ion allocation by importing a shared buffer fd.
188 * \param ionFd ion client (ownership transferred to created object)
192 * \return created ion allocation (implementation) which may be invalid if the
198 * Constructs an ion allocation by allocating an ion buffer.
200 * \param ionFd ion client (ownership transferred to created object)
204 * \param flags ion allocation flags
206 * \return created ion allocation (implementation) which may be invalid if the
217 // actually unmap, so we end up remapping an ion buffer multiple times.
359 * Constructs an ion allocation for platforms with new (ion_4.12.h) api
361 * \note We always create an ion allocation, even if the allocation or import fails
364 * \param ionFd ion client (ownership transferred to created object)
486 /* ======================================= ION ALLOCATOR ====================================== */
498 Traits traits = { "android.allocator.ion", id, LINEAR, minUsage, maxUsage };
