blob: e369c0ee92046cea877c61ad7a8816e835325548 [file] [log] [blame]
James Dong334de522012-03-12 12:47:14 -07001/*
2 * Copyright (C) 2009 The Android Open Source Project
3 *
4 * Licensed under the Apache License, Version 2.0 (the "License");
5 * you may not use this file except in compliance with the License.
6 * You may obtain a copy of the License at
7 *
8 * http://www.apache.org/licenses/LICENSE-2.0
9 *
10 * Unless required by applicable law or agreed to in writing, software
11 * distributed under the License is distributed on an "AS IS" BASIS,
12 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13 * See the License for the specific language governing permissions and
14 * limitations under the License.
15 */
16
17#ifndef HARDWARE_API_H_
18
19#define HARDWARE_API_H_
20
Andreas Huber00e595f2013-06-25 10:08:42 -070021#include <media/hardware/OMXPluginBase.h>
22#include <media/hardware/MetadataBufferType.h>
James Dong334de522012-03-12 12:47:14 -070023#include <system/window.h>
24#include <utils/RefBase.h>
25
26#include <OMX_Component.h>
27
28namespace android {
29
30// A pointer to this struct is passed to the OMX_SetParameter when the extension
31// index for the 'OMX.google.android.index.enableAndroidNativeBuffers' extension
32// is given.
33//
34// When Android native buffer use is disabled for a port (the default state),
35// the OMX node should operate as normal, and expect UseBuffer calls to set its
36// buffers. This is the mode that will be used when CPU access to the buffer is
37// required.
38//
39// When Android native buffer use has been enabled for a given port, the video
40// color format for the port is to be interpreted as an Android pixel format
Lajos Molnar5f39f602013-07-17 14:55:55 -070041// rather than an OMX color format. Enabling Android native buffers may also
42// change how the component receives the native buffers. If store-metadata-mode
43// is enabled on the port, the component will receive the buffers as specified
44// in the section below. Otherwise, unless the node supports the
45// 'OMX.google.android.index.useAndroidNativeBuffer2' extension, it should
46// expect to receive UseAndroidNativeBuffer calls (via OMX_SetParameter) rather
47// than UseBuffer calls for that port.
James Dong334de522012-03-12 12:47:14 -070048struct EnableAndroidNativeBuffersParams {
49 OMX_U32 nSize;
50 OMX_VERSIONTYPE nVersion;
51 OMX_U32 nPortIndex;
52 OMX_BOOL enable;
53};
54
Lajos Molnar9f590df2015-05-15 20:31:57 -070055// A pointer to this struct is passed to OMX_SetParameter() when the extension index
56// "OMX.google.android.index.storeMetaDataInBuffers" or
57// "OMX.google.android.index.storeANWBufferInMetadata" is given.
James Dong334de522012-03-12 12:47:14 -070058//
59// When meta data is stored in the video buffers passed between OMX clients
60// and OMX components, interpretation of the buffer data is up to the
61// buffer receiver, and the data may or may not be the actual video data, but
62// some information helpful for the receiver to locate the actual data.
63// The buffer receiver thus needs to know how to interpret what is stored
64// in these buffers, with mechanisms pre-determined externally. How to
Lajos Molnar9f590df2015-05-15 20:31:57 -070065// interpret the meta data is outside of the scope of this parameter.
James Dong334de522012-03-12 12:47:14 -070066//
Lajos Molnar9f590df2015-05-15 20:31:57 -070067// Currently, this is used to pass meta data from video source (camera component, for instance) to
68// video encoder to avoid memcpying of input video frame data, as well as to pass dynamic output
69// buffer to video decoder. To do this, bStoreMetaData is set to OMX_TRUE.
Lajos Molnar5f39f602013-07-17 14:55:55 -070070//
Lajos Molnar9f590df2015-05-15 20:31:57 -070071// If bStoreMetaData is set to false, real YUV frame data will be stored in input buffers, and
72// the output buffers contain either real YUV frame data, or are themselves native handles as
73// directed by enable/use-android-native-buffer parameter settings.
74// In addition, if no OMX_SetParameter() call is made on a port with the corresponding extension
75// index, the component should not assume that the client is not using metadata mode for the port.
Lajos Molnar5f39f602013-07-17 14:55:55 -070076//
Lajos Molnar9f590df2015-05-15 20:31:57 -070077// If the component supports this using the "OMX.google.android.index.storeANWBufferInMetadata"
78// extension and bStoreMetaData is set to OMX_TRUE, data is passed using the VideoNativeMetadata
79// layout as defined below. Each buffer will be accompanied by a fence. The fence must signal
80// before the buffer can be used (e.g. read from or written into). When returning such buffer to
81// the client, component must provide a new fence that must signal before the returned buffer can
82// be used (e.g. read from or written into). The component owns the incoming fenceFd, and must close
83// it when fence has signaled. The client will own and close the returned fence file descriptor.
84//
85// If the component supports this using the "OMX.google.android.index.storeMetaDataInBuffers"
86// extension and bStoreMetaData is set to OMX_TRUE, data is passed using VideoGrallocMetadata
87// (the layout of which is the VideoGrallocMetadata defined below). Camera input can be also passed
88// as "CameraSource", the layout of which is vendor dependent.
89//
90// Metadata buffers are registered with the component using UseBuffer calls, or can be allocated
91// by the component for encoder-metadata-output buffers.
James Dong334de522012-03-12 12:47:14 -070092struct StoreMetaDataInBuffersParams {
93 OMX_U32 nSize;
94 OMX_VERSIONTYPE nVersion;
95 OMX_U32 nPortIndex;
96 OMX_BOOL bStoreMetaData;
97};
98
Lajos Molnar07d93d12013-05-03 13:20:53 -070099// Meta data buffer layout used to transport output frames to the decoder for
100// dynamic buffer handling.
Lajos Molnar9f590df2015-05-15 20:31:57 -0700101struct VideoGrallocMetadata {
102 MetadataBufferType eType; // must be kMetadataBufferTypeGrallocSource
103 buffer_handle_t hHandle;
104};
105
106struct VideoNativeMetadata {
107 MetadataBufferType eType; // must be kMetadataBufferTypeANWBuffer
108 struct ANativeWindowBuffer* pBuffer;
109 int nFenceFd; // -1 if unused
Lajos Molnar07d93d12013-05-03 13:20:53 -0700110};
111
Lajos Molnardde86f72013-05-03 13:22:13 -0700112// A pointer to this struct is passed to OMX_SetParameter() when the extension
113// index "OMX.google.android.index.prepareForAdaptivePlayback" is given.
114//
115// This method is used to signal a video decoder, that the user has requested
116// seamless resolution change support (if bEnable is set to OMX_TRUE).
117// nMaxFrameWidth and nMaxFrameHeight are the dimensions of the largest
118// anticipated frames in the video. If bEnable is OMX_FALSE, no resolution
119// change is expected, and the nMaxFrameWidth/Height fields are unused.
120//
121// If the decoder supports dynamic output buffers, it may ignore this
122// request. Otherwise, it shall request resources in such a way so that it
123// avoids full port-reconfiguration (due to output port-definition change)
124// during resolution changes.
125//
126// DO NOT USE THIS STRUCTURE AS IT WILL BE REMOVED. INSTEAD, IMPLEMENT
127// METADATA SUPPORT FOR VIDEO DECODERS.
128struct PrepareForAdaptivePlaybackParams {
129 OMX_U32 nSize;
130 OMX_VERSIONTYPE nVersion;
131 OMX_U32 nPortIndex;
132 OMX_BOOL bEnable;
133 OMX_U32 nMaxFrameWidth;
134 OMX_U32 nMaxFrameHeight;
135};
136
James Dong334de522012-03-12 12:47:14 -0700137// A pointer to this struct is passed to OMX_SetParameter when the extension
138// index for the 'OMX.google.android.index.useAndroidNativeBuffer' extension is
139// given. This call will only be performed if a prior call was made with the
140// 'OMX.google.android.index.enableAndroidNativeBuffers' extension index,
141// enabling use of Android native buffers.
142struct UseAndroidNativeBufferParams {
143 OMX_U32 nSize;
144 OMX_VERSIONTYPE nVersion;
145 OMX_U32 nPortIndex;
146 OMX_PTR pAppPrivate;
147 OMX_BUFFERHEADERTYPE **bufferHeader;
148 const sp<ANativeWindowBuffer>& nativeBuffer;
149};
150
151// A pointer to this struct is passed to OMX_GetParameter when the extension
152// index for the 'OMX.google.android.index.getAndroidNativeBufferUsage'
153// extension is given. The usage bits returned from this query will be used to
154// allocate the Gralloc buffers that get passed to the useAndroidNativeBuffer
155// command.
156struct GetAndroidNativeBufferUsageParams {
157 OMX_U32 nSize; // IN
158 OMX_VERSIONTYPE nVersion; // IN
159 OMX_U32 nPortIndex; // IN
160 OMX_U32 nUsage; // OUT
161};
162
163// An enum OMX_COLOR_FormatAndroidOpaque to indicate an opaque colorformat
164// is declared in media/stagefright/openmax/OMX_IVCommon.h
165// This will inform the encoder that the actual
166// colorformat will be relayed by the GRalloc Buffers.
167// OMX_COLOR_FormatAndroidOpaque = 0x7F000001,
168
Andreas Huber7682a9c2012-09-28 11:32:16 -0700169// A pointer to this struct is passed to OMX_SetParameter when the extension
170// index for the 'OMX.google.android.index.prependSPSPPSToIDRFrames' extension
171// is given.
172// A successful result indicates that future IDR frames will be prefixed by
173// SPS/PPS.
174struct PrependSPSPPSToIDRFramesParams {
175 OMX_U32 nSize;
176 OMX_VERSIONTYPE nVersion;
177 OMX_BOOL bEnable;
178};
James Dong334de522012-03-12 12:47:14 -0700179
Lajos Molnar524077c2014-07-25 07:53:56 -0700180// Structure describing a media image (frame)
181// Currently only supporting YUV
182struct MediaImage {
183 enum Type {
184 MEDIA_IMAGE_TYPE_UNKNOWN = 0,
185 MEDIA_IMAGE_TYPE_YUV,
186 };
187
188 enum PlaneIndex {
189 Y = 0,
190 U,
191 V,
192 MAX_NUM_PLANES
193 };
194
195 Type mType;
196 size_t mNumPlanes; // number of planes
Lajos Molnarea5da672015-01-30 10:36:11 -0800197 size_t mWidth; // width of largest plane (unpadded, as in nFrameWidth)
198 size_t mHeight; // height of largest plane (unpadded, as in nFrameHeight)
Lajos Molnar524077c2014-07-25 07:53:56 -0700199 size_t mBitDepth; // useable bit depth
200 struct PlaneInfo {
201 size_t mOffset; // offset of first pixel of the plane in bytes
202 // from buffer offset
203 size_t mColInc; // column increment in bytes
204 size_t mRowInc; // row increment in bytes
205 size_t mHorizSubsampling; // subsampling compared to the largest plane
206 size_t mVertSubsampling; // subsampling compared to the largest plane
207 };
208 PlaneInfo mPlane[MAX_NUM_PLANES];
209};
210
211// A pointer to this struct is passed to OMX_GetParameter when the extension
212// index for the 'OMX.google.android.index.describeColorFormat'
213// extension is given. This method can be called from any component state
214// other than invalid. The color-format, frame width/height, and stride/
215// slice-height parameters are ones that are associated with a raw video
216// port (input or output), but the stride/slice height parameters may be
Lajos Molnarea5da672015-01-30 10:36:11 -0800217// incorrect. bUsingNativeBuffers is OMX_TRUE if native android buffers will
218// be used (while specifying this color format).
219//
220// The component shall fill out the MediaImage structure that
Lajos Molnar524077c2014-07-25 07:53:56 -0700221// corresponds to the described raw video format, and the potentially corrected
222// stride and slice-height info.
223//
Lajos Molnarea5da672015-01-30 10:36:11 -0800224// The behavior is slightly different if bUsingNativeBuffers is OMX_TRUE,
225// though most implementations can ignore this difference. When using native buffers,
226// the component may change the configured color format to an optimized format.
227// Additionally, when allocating these buffers for flexible usecase, the framework
228// will set the SW_READ/WRITE_OFTEN usage flags. In this case (if bUsingNativeBuffers
229// is OMX_TRUE), the component shall fill out the MediaImage information for the
230// scenario when these SW-readable/writable buffers are locked using gralloc_lock.
231// Note, that these buffers may also be locked using gralloc_lock_ycbcr, which must
232// be supported for vendor-specific formats.
233//
234// For non-YUV packed planar/semiplanar image formats, or if bUsingNativeBuffers
235// is OMX_TRUE and the component does not support this color format with native
236// buffers, the component shall set mNumPlanes to 0, and mType to MEDIA_IMAGE_TYPE_UNKNOWN.
Lajos Molnar524077c2014-07-25 07:53:56 -0700237struct DescribeColorFormatParams {
238 OMX_U32 nSize;
239 OMX_VERSIONTYPE nVersion;
240 // input: parameters from OMX_VIDEO_PORTDEFINITIONTYPE
241 OMX_COLOR_FORMATTYPE eColorFormat;
242 OMX_U32 nFrameWidth;
243 OMX_U32 nFrameHeight;
244 OMX_U32 nStride;
245 OMX_U32 nSliceHeight;
Lajos Molnarea5da672015-01-30 10:36:11 -0800246 OMX_BOOL bUsingNativeBuffers;
Lajos Molnar524077c2014-07-25 07:53:56 -0700247
248 // output: fill out the MediaImage fields
249 MediaImage sMediaImage;
250};
251
Rachad7cb0d392014-07-29 17:53:53 -0700252// A pointer to this struct is passed to OMX_SetParameter or OMX_GetParameter
253// when the extension index for the
254// 'OMX.google.android.index.configureVideoTunnelMode' extension is given.
255// If the extension is supported then tunneled playback mode should be supported
256// by the codec. If bTunneled is set to OMX_TRUE then the video decoder should
257// operate in "tunneled" mode and output its decoded frames directly to the
258// sink. In this case nAudioHwSync is the HW SYNC ID of the audio HAL Output
259// stream to sync the video with. If bTunneled is set to OMX_FALSE, "tunneled"
260// mode should be disabled and nAudioHwSync should be ignored.
261// OMX_GetParameter is used to query tunneling configuration. bTunneled should
262// return whether decoder is operating in tunneled mode, and if it is,
263// pSidebandWindow should contain the codec allocated sideband window handle.
264struct ConfigureVideoTunnelModeParams {
265 OMX_U32 nSize; // IN
266 OMX_VERSIONTYPE nVersion; // IN
267 OMX_U32 nPortIndex; // IN
268 OMX_BOOL bTunneled; // IN/OUT
269 OMX_U32 nAudioHwSync; // IN
270 OMX_PTR pSidebandWindow; // OUT
271};
272
James Dong334de522012-03-12 12:47:14 -0700273} // namespace android
274
275extern android::OMXPluginBase *createOMXPlugin();
276
277#endif // HARDWARE_API_H_