| f7a4d11e9f710e2cd0592310ac1baecccb85f1d1 |
|
18-Oct-2012 |
Jason Simmons <jsimmons@google.com> |
Snapshot of TI's camera HAL development with adjustments to build in our tree
The head of TI's hardware/ti/omap4xxx/camera repository at the time of the snapshot was:
commit 4447eaef6dc757aecab869054460ae87848e575e
Author: Vladimir Petrov <vppetrov@mm-sol.com>
Date: Thu Aug 16 19:13:03 2012 +0300
CameraHal: Add support to release tap in/outs
Change-Id: Ia6bfefb427fe171067eddcab6d896683ff2d149f
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| d822531f1f2b4c0fea1cd971d28bd1e552ed67ba |
|
07-May-2012 |
Emilian Peev <epeev@mm-sol.com> |
CameraHAL: Aligns UV planes during YV12 preview callbacks
- UV planes stride should be multiple of 16. The buffer
size should also be updated accordingly.
Bug: 6447707
Change-Id: If436801fbb2750523a3207878f611c8094667367
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| baed3f89bba1cbd3720656f7125f25705be38db7 |
|
01-May-2012 |
Emilian Peev <epeev@mm-sol.com> |
CameraHal: Add support for YUY2 preview callbacks
- The currently used Gralloc buffers for preview
are limited to only NV12 pixelformat. In order
to support this type of preview callbacks,
CameraHal will internally convert from NV12 to
YUY2.
Bug: 6419136
Change-Id: I879e32d4b2142bdd0a1f89fe7c5496d250039b73
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 2dc9bc1f87be40c2e4903b97a3df353d0f7c6781 |
|
22-Apr-2012 |
Emilian Peev <epeev@mm-sol.com> |
CameraHal: Fix for YV12 camera callbacks
- 'mPreviewPixelFormat' was being set incorrectly
for YV12 case.
Bug: 6325348
Change-Id: I80acc5cd721d317fac9525bdb734fe2e70df85bf
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 609bc02b21c725825bd469391e9ecd4e2d462fe1 |
|
15-Mar-2012 |
Tyler Luu <tluu@ti.com> |
camera: prevent possible deadlock scenario
Hold scope of returnFrame lock for just the calculation
of refCount. Otherwise, we could have a scenario where
endImageCapture and stopRecording could cause a deadlock
competing for mReturnFrameLock and mLock. Issue arises
mainly because endImageCapture is signalled from
fillThisBuffer which stopRecording will need to get into.
Make sure mEventQ has a message before calling get() since
read on the pipe will block with notifyEvent holding mLock.
Change-Id: I3a125711632fa311fd794e300cd5008321a84c40
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 41a31123a0fc59b8112460285d3f1ba73c5537c0 |
|
08-Feb-2012 |
Emilian Peev <epeev@mm-sol.com> |
CameraHal: Reduces Camera logcat prints
Change-Id: Id32ad1b882a76f091866583b15ae0ca2929bacef
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 057f4fd59ec05ded909e9eb9a3363d9ea345b0ca |
|
31-Jan-2012 |
Tyler Luu <tluu@ti.com> |
CameraHal: Implementation for CAF status callbacks
1. Remove internal handling of CAMERA_MSG_FOCUS. Before we were
enabling CAMERA_MSG_FOCUS only when application calls autoFocus().
No longer needed since the CAMERA_MSG_FOCUS can come just during
preview now.
2. Add handling of unregistered focus callbacks. Since OMXCamera
will send callbacks even when we are not waiting for one, add some
handling.
Signed-off-by: Tyler Luu <tluu@ti.com>
Change-Id: I457e67b33b2561dd0b1ce3863ce807a8c27f79f6
Conflicts:
camera/OMXCameraAdapter/OMXFocus.cpp
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| a6e104aadf560de4e33291c8e85f79acc8fb46c9 |
|
21-Nov-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Fix timing issue with focus msg disable
Disable focus message before sending notification because client
can immediately call focus again after receiving notification and
before we get a chance to disable the message. This will result in
the focus notificiation for the subsequent focus call to be missed.
Change-Id: I1367cdcebe490c32251e992b87ada3edf6b28036
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 0c7ae887ee41852f275887fd543fae810668e2d1 |
|
28-Oct-2011 |
Tyler Luu <tluu@ti.com> |
CameraHAL: Prevent deadlock in AppCallbackNotifier::stop()
There is a small chance that a stopPreview call can come from
CameraService right around the same time Encoder thread will
send a data callback for the video snapshot. Currently, we
are waiting for the encoder thread to join in AppCallbackNofier::
stop(), so we could deadlock if CameraService locks in
lockIfMessageWanted for the video snapshot.
Instead of waiting for Encoder thread to join, we can make
cancel() block until Encoder thread is done canceling the
encode. After cancel() returns, we can free up the cookies
that we passed to it, so Encoder thread does not need to call
the callback function to AppCallbackNotifier.
Change-Id: Ib453d49d91077925b143c812d43a7d1b782c181c
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| bf20bcd681ad3c466099f45334bf639da9baedd0 |
|
22-Nov-2011 |
Akwasi Boateng <akwasi.boateng@ti.com> |
CameraHAL: Exit Appcallback thread immediately.
Allow appcallback thread to exit immediately when exit command is processed.
Signed-off-by: Akwasi Boateng <akwasi.boateng@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
Change-Id: I83db309cf973e1ce9494c855430897a0c41704d8
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 80a2eeb9c95c24e0dd69e61c3f58e6da36cf703d |
|
29-Oct-2011 |
Akwasi Boateng <akwasi.boateng@ti.com> |
CameraHAL: Avoids a possible deadlock in AppCallbackNotifier
- 'disableMsgType()' was querying CameraHal for enabled message
types through 'msgTypeEnabled()'. This method will lock 'mLock'
in CameraHal. On the other hand 'takePicture()' inside CameraHal
will also lock 'mLock' before execution. If preview callbacks are
enabled before image capture, then 'takePicture()' will call
AppCallbackNotifier's 'disableMsgType()', which will try to
lock 'mLock' again. Solution, a query to CameraHal for enabled
message types is not needed inside 'disableMsgType()' because the
passed argument 'msgType' already contains all the needed
information.
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
Signed-off-by: Akwasi Boateng <akwasi.boateng@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
Change-Id: Ia4b7634ce21b8243f08d9124823c77e6bde84a8d
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| d9520b9de06f01b9411307040cf245e6fc7fe361 |
|
12-Oct-2011 |
Milen Mitkov <mmitkov@mm-sol.com> |
CameraHAL: Enable LDCNSF for Video snapshot
Enables LDCNSF for Video snapshot, also adds start_offset and right_crop fields
to the JPEG encoder wrapper, because the image with LDCNSF has artifacts on top
and right.
Change-Id: I1011252e3f8068083f9d057b7763b7f79c59a75d
Signed-off-by: Milen Mitkov <mmitkov@mm-sol.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| e46394481e771dbdc8683645c3740a3d262a3d0f |
|
17-Nov-2011 |
Iliyan Malchev <malchev@google.com> |
CameraHAL: clean up logs
-- introduce CAMHAL_LOGI so that we don't have to dump informational messages
as LOGE
-- convert some verbose messages to CAMHAL_LOGDB
-- convert most frequent non-error log messages to CAMHAL_LOGI
Change-Id: I8afc24aa17da2c157b7b37300a79b4cde81f87e5
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| cb1183d6c3c8894fa09ad3ff7952388f6e7bec94 |
|
11-Nov-2011 |
Akwasi Boateng <akwasi.boateng@ti.com> |
videosnapshot memory corruption fixes.
1. Fixes memory corruption of dst buffer in
nv21_to_yuv() convertion
2. Free malloced row_tmp buffer
3. Free params string in Appcallback
Change-Id: I2179f1158f6e72cca0f7e5c815b1cb576bfa925e
Signed-off-by: Akwasi Boateng <akwasi.boateng@ti.com>
related-to-bug: 5601247
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| f9df3ee5cfb3c3177bcc630abf6d756e8a60254c |
|
10-Nov-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL: Clear events queue fix, clear command queue on exit
Fix 2/3 for b/5593964.
1. The events queue wasn't being cleared correctly inside
OMXCameraAdapter as some items were being removed while the
index was being formulated based on the original size
2. The command queue should be cleared before posting the EXIT
message for the OMX adapter threads so as not to process those
messages since we are exiting
Change-Id: I0a5eaceb3d1504fee05b064ebb5fe888e129ad44
Signed-off-by: Sundar Raman <sunds@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 3ec18006399d61e97382601d14aaa43ee339c8b6 |
|
08-Nov-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL: Fixes for ANR and a setParameter issue
Fix 1/3 for b/5593964.
1. Ensure we don't race with stopImageCapture when stopPreview is called
2. Signal the shutter callback correctly
3. Do not crash the media server if focus APIs and image capture returns error
Still go ahead and perform de-init
4. Replace setParameter from CameraHAl to AppCallbackNotifier with getParameter
when needed.
Change-Id: I2b2745827d227a8d7927ce1611a84c29129e8891
Signed-off-by: Sundar Raman <sunds@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 3dcde7b7332edf04cd597b01d69950544dcd6589 |
|
25-Oct-2011 |
Akwasi Boateng <akwasi.boateng@ti.com> |
Fixes for MMS setparameter crashes
1. Fix native crash for set parameter when
zoom is applied in MMS mode and while
recording is in progress.
2. Don't allow restart of preview or preview
stop when recording is in progress.
3. Fix slow zoom when in MMS mode casued by
unnecessary preview restarts.
4. Fix initial jerky preview when you start
recording in MMS mode caused by having
to restart preview.
Change-Id: Ie64799974488caae5887e4c9f9072d74a12dd797
Signed-off-by: Akwasi Boateng <akwasi.boateng@ti.com>
related-to-bug: 5507018
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| c11c07d676f130e6e28ab1611f4862a01a160389 |
|
13-Oct-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Fixes for #testVideoSnapshot
1. Add raw notify callback for video snapshot
2. Add new state for video capture + AF
3. We were not populating focal length correctly for jhead. Need to send
focal length as a rational in this format "xx/yy"
4. Need to send GPSProcessingMethod as an UNDEFINED ASCII to jhead
b/5448171
Change-Id: Ie6be9ad821d1fa106d9c857681f2fa6427d4f283
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 8a01f97380aad5b6a30a2d248aa07af4d92373d0 |
|
26-Sep-2011 |
Tyler Luu <tluu@ti.com> |
omap4xxx: camera: re-enable postview callback
Fixes b/5370657... again
Change-Id: I998d2292d25b76b67b1fbd2ff6bd65e854c176c8
Signed-off-by: Tyler Luu <tluu@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 2ecb39c0ca21ce9ae00c4585e3f7002e8b4e6ca7 |
|
28-Sep-2011 |
Tyler Luu <tluu@ti.com> |
omap4xxx: camera: timing issue with autoFocus/cancelAutoFocus
Fixes b/5332895
If cancelAutoFocus comes when Ducati is already sending focus
callback, CameraHal will go ahead and send focus callback to
the application. This can cause the subsequent autoFocus call
to be acked almost immediately with the previous autoFocus call's
notification. Application will think autoFocus is done while
CamearHal is still focusing, takePicture from the application
will return an error.
To fix this issue, do not always send focus notification. We are
going to internally enable/disable auto focus message. Enable focus
message when autoFocus call comes and disable focus message after
notification or if cancelAutoFocus call comes. This will prevent us
from sending notify message if application calls cancelAutoFocus.
Change-Id: I8c8892f14894e23a9d73fa1c2b058389d196eefa
Signed-off-by: Tyler Luu <tluu@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 8e52e3bcc31f65a699c25557cf3026d324e631b4 |
|
07-Oct-2011 |
Tyler Luu <tluu@ti.com> |
omap4xxx: camera: cancel and flush for SW JPEG encoder
Fixes b/5378650
1. Add method to externally cancel Encoder class while in the middle of
encoding.
2. Add queue in AppCallbackNotifier to track all the encoding sessions. When
stopping AppCallbackNotifier if any encoding sessions are still ongoing,
cancel and wait for the threads to return. Previously, it was possible for
Encoder threads to still be running when the preview and images buffers were
freed.
Change-Id: Ib123d1644dfa7058a6f50f0001b4d05359853827
Signed-off-by: Tyler Luu <tluu@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| c160a1f85c70e49a7613d774e2d99035f3cb4851 |
|
04-Oct-2011 |
Tyler Luu <tluu@ti.com> |
omap4xxx: camera: EXIF thumbnail for video snapshot
Fixes b/5370657
1) Extend NV12 resizer to take stride insteadof hardcoding stride
2) Change Encoder class interface to support encoding a thumbnail and main jpeg
image. Encoder will resize/encodethumbnail in parallel while encoding the
main jpeg. Only NV21/NV12 resizing is supported. Thumbnail is created
withpost view frame.
3) Add interface in Encoder class to replace thumbnail with jhead.
4) Height and width fields of EXIF are not proper. Fixed.
Change-Id: I5d0063357e4e9e327d22805c2dddf8f630d22e7b
Signed-off-by: Raji Reddy Kandi<rajireddy.k@samsung.com>
Signed-off-by: Tyler Luu <tluu@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 72b0d2814165e633385bd87a838fc9c3a8250113 |
|
15-Sep-2011 |
Akwasi Boateng <akwasi.boateng@ti.com> |
omap4xxx: camera: send different preview and video buffers for MMS mode
Fixes b/5265389 b/5156090
1. Add support to send different preview and video buffers to framework in MMS
mode.
2. For resolutions less than or equal to QVGA, preview resolution will be
changed to a bigger resolution matching the aspect ratio of the preview
resolution.
3. During record the changed resolution will be resized to the original
resolution and sent to the encoder.
4. Modified NV12 resizer routine to account for frame offset and stride to
avoid double memcpy of the buffers
Change-Id: If66aa1fd861078d0a63b4a77a1bdc20d4c6bccda
Signed-off-by: Akwasi Boateng <akwasi.boateng@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 8e88af31129b8cc09675279ca2eac88256d8526b |
|
16-Sep-2011 |
Akwasi Boateng <akwasi.boateng@ti.com> |
Grallock lock and unlock fixes
1. Get and store Y and UV pointers from
all gralloc handles to be used for
preview callback and video frames.
2. Ensure gralloc lock is successfull
before frame return to OMXCameraAdapter
Change-Id: Ibeea6d00f2c1a1c45bcd2eafb22b90a795516e5c
Signed-off-by: Akwasi Boateng <akwasi.boateng@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 26d9a9166b81616d205eb9ebb49c18dac1f6c044 |
|
15-Sep-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Ensure frames are returned by AppCallbackNotifier
No bug filed for this, but it results in a crash. We can say it's a partial
fix for b/5316293
1. Clean-up notifyFrame a bit by using a common function
to send data callbacks. This ensures common functionality
for the all frame types.
2. Flush all the frames after stopping AppCallbackNotifier
to ensure notifyFrame doesn't operate on the buffers.
Change-Id: I4b0c8a595ea5474e8c8f5f98cfee16e6c1bde949
Signed-off-by: Tyler Luu <tluu@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 3f75fa6e5edf504c155a357494ab77c59b6887b8 |
|
13-Sep-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Modify exit behavior of notify thread
When the camera app dies, sometimes the release() call is coming
from the same thread as a callback instead of the main thread. When this
happens, it causes a segfault in AppCallbackNotifier because we end up
destroying AppCallbackNotifier without the NotificationThread knowing.
The subsequent waitForMsg() after release() will result in a segfault since
the message queues are deleted.
Instead of looping forever in a while loop in the notification thread,
return bool value in looper function. This gives the Thread class a chance
to exit in case of a requestExit() in the same thread. Looper function
will automatically will be called again if exit is not pending and
previous looper function call returned true.
Change-Id: I6bdc65df71e2c3ebcbd409654b828edef29b1a0e
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 7207ddb84b57c01ea50c5af85dc4a3984b364dea |
|
14-Sep-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL: MTS: Synchronize AppCallbackNotifier::stop with notifyFrame
AppCallbackNotifier::stop has to wait for any 2D copies to complete
before exiting because the tiler 2d memory might get released
by the destruction of the surface after stopPreview finishes.
This patch takes care of synchronizing any ongoing copies
from surface buffers with the stop method and effectively
avoids access after free issues.
Change-Id: Id7e5b6fab4a2a6b7fcce0ba8b9bd3ad315263eaa
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 0ff71809874c00d540af83c123f3dc34759f1871 |
|
14-Sep-2011 |
Sundar Raman <sunds@ti.com> |
Camera HAL: Crash media server in case of camera hardware errors
Applications do not handle errors other then CAMERA_SERVER_DIED.
So there is no way for the application to know about fatal errors
other than killing the media server when they happen.
So this patch aborts media server whenever the ducati throws a
fatal exception or when it hangs so that the apps notify the user
of the error and then close. The user will be able to restart the
application since the media server restarts automatically and the
ducati is also restored by syslink automatically.
Change-Id: Ic3e93130818edbe281affca99b808e09e08614c5
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| e6cf8e95b3192621d3b992fbb09df8c58b1a1e5f |
|
13-Sep-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL: Updates related to multiple MTS,CTS tests
- Test '#testTakePicture' in both the MTS suite and
the CTS package, require raw callbacks to be
generated when 'takePicture()' is provided with an
appropriate handler for it. Unfortunately, raw
data is not always provided by the CameraAdapters.
This modification adds the necessary functionality
in order to enable raw callbacks, when needed.
Change-Id: I1369f7a6edbc54195c5a71b35e0096c72d6ed368
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
Change-Id: I2b963f5c23d31b02f3d59e1ee8c36cf3cd195bb6
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 36e9bdd56757ff8048e08f6e52f234480c44f122 |
|
08-Sep-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Add Exif support to video snapshot
Use jhead library to insert Exif to jpeg stream
returned from libjpeg.
Change-Id: Ia6398180b7ef3c1b3ddcb35e489527289565fef5
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 6b5eaf29c3d17a24731bf9271bd0d199d433813e |
|
09-Sep-2011 |
Akwasi Boateng <akwasi.boateng@ti.com> |
Unblock semaphores during Fatal Errors
1. Remove all pending events and unblock
all waiting semaphore during Fatal error.
2. Exit execution when in invalid state.
3. Remove error nitiifcation from
Appcallback thread
Change-Id: I1612ff75e83ebf285d4cc168a829e0f81d4968b1
Signed-off-by: Akwasi Boateng <akwasi.boateng@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 941b79b3815eb5f41e0d194d6f65161d1e4a86d0 |
|
08-Sep-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Use the same gralloc usage bits for alloc and write
Change-Id: I013fd9ff40efb0ceaa1575a5af1c077d72e7921d
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| ee6bb64f60c228d711dc1d6875d8f4b0ed88b6cf |
|
01-Sep-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Initial support for video snapshot
Adds support for capturing an image while
recording in video mode. Sets up Ducati to
return a YUV422I buffer and encode is performed
in AppCallbackNotifier with Encoder_libjpeg class.
Change-Id: Ia351fc99dab63a12add8c6c960b186bbe5be275a
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| b2fb762fda58b35be6da475582e3f623f9f1e46a |
|
30-Aug-2011 |
Tyler Luu <tluu@ti.com> |
CameraHAL: Fixes for CTS test #testJpegCallbackStartPreview
- The camera client should be able to restart
the preview from within the context of a jpeg
callback. Depending on the binder ipc timing
this may not be possible, because image capture
is stopped right after the jpeg data callback.
Change-Id: Id006ecd4d9f82eaa74b38f921bed2543f8c0c217
Original-author: Emilian Peev <epeev@mm-sol.com>
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 6c73fda9fdca5431e4e7911bb3171e36088a861e |
|
27-Aug-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Lock buffers sent to FrameProvider
Use GraphicBufferMapper API to lock buffer
before sending to FrameProvider to ensure
there isn't simultaneous accesses to bufffer
by SGX
Change-Id: Ifbb5c88bac49b1b494bd984137b523d35f4a6f57
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| f8a689d36a1b20942e39d848712e99d4a000fa72 |
|
25-Aug-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL: fixes the UV buffer start address calculation.
Signed-off-by: Solaiyappan Saravanan <saravanan.s@ti.com>
Change-Id: Ie3ed733fb163ac686c9d42766923ccc7e3715a5e
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| 2e986e5e29b391b070f608d641538c14b778d4ba |
|
23-Aug-2011 |
Iliyan Malchev <malchev@google.com> |
omap4xxx: camera: lock gralloc buffers read-rarely/write-never
Change-Id: Iacf80f7485e78d20000df27bca9e57caafcea111
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|
| c322989ae6ff6769490828de1b5eda12b749cce9 |
|
08-Aug-2011 |
Iliyan Malchev <malchev@google.com> |
initial commit
Change-Id: I8f7a7eeece0e516efa486b77e9d97805c0e65d3e
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4-aah/camera/AppCallbackNotifier.cpp
|