| 707e301de8b52780a7f0e88e6f25ac919c23671f |
|
08-Nov-2012 |
Eino-Ville Talvala <etalvala@google.com> |
Revert "CameraHal: Sync AF cancel with incoming OMX events"
This reverts commit b96dffd40e25d29a61f9fbd7f2e5968b5335b957.
Bug: 7495861
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| b96dffd40e25d29a61f9fbd7f2e5968b5335b957 |
|
22-Oct-2012 |
Emilian Peev <epeev@mm-sol.com> |
CameraHal: Sync AF cancel with incoming OMX events
- Cancel AF is made to wait on incoming OMX events
when AF status changes. An AF timeout is introduced
in order not to block this call indefinitely.
- Additionally calls to 'autoFocus()' will immediately
trigger AF callbacks if fixed modes are being used.
Bug: 6949572
Change-Id: I5f240fb6fc7fe53aecaff76d75d608dd522c1e27
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| d8bf3dc07ef357eb0761cfdacab458f2358907aa |
|
02-May-2012 |
Emilian Peev <epeev@mm-sol.com> |
CameraHal: Do full AF sweep during lost AF status
- Previously only "OMX_FocusStatusUnableToReach" status
was activating the full AF scan. Currently with CAF
callbacks updates in Ducati, this is no longer the case
and "OMX_FocusStatusLost" should be considered as well.
Bug: 6378194
Change-Id: Ib296c6d7197cd275a9e5106f791451f4179be3e9
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 96f2b555d2200fca7d8399c4c9a968590637aa31 |
|
30-Nov-2011 |
Emilian Peev <epeev@mm-sol.com> |
CameraHAL: Fix for CTS test #testFocusDistances
- The 'focusStatus' variable in 'doAutoFocus()'
is uninitialized in the case where the camera
client sets focus lock in CAF mode. Depending
on the current stack content this method might
try to set CAF focus again and wait for a focus
callback, which will inevitably timeout.
- Fix for random fails during CTS test
#testFocusDistances.
Change-Id: Iafa84bbf5b7119d77f1f666a6a88c613b657541e
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 796f0f82433a3040198f216d15fd9ce17c04f360 |
|
19-Mar-2012 |
Emilian Peev <epeev@mm-sol.com> |
CameraHal: Remove excessive focus mode configurations
- This change should improve overall stability during
image capture. Configuring focus mode while image
capture is active is always going to result in
'OMX_ErrorBadParameter'.
Bug: 6026480
Change-Id: I735c5d25adc293d163f77488c0dc6d30a636544b
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 484116750df56d0805d5f5727ad94701f916e8c6 |
|
21-Mar-2012 |
Emilian Peev <epeev@mm-sol.com> |
CameraHal: Don't signal off AF status events to 'doAutoFocus()'
- In dark lighting conditions and when AF assist is active
sometimes the OMX camera component changes the AF status
to off and generates and OMX event. Currently this is being
interpreted as cancel AF.
Bug: 6197932
Change-Id: Ibddd0033eecd186c1bfc90530af651f1c0223a25
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 5703f6d63cead1c511f23531cfb13c5ba6de576b |
|
14-Feb-2012 |
Emilian Peev <epeev@mm-sol.com> |
CameraHal: Workaround for delayed AF events
Addresses a corner case with b/5534973
- If the OMX Camera component delays ( for whatever reason )
the AF status notification during cancelAF, then there is
a chance that the AF callback timeout inside 'doAutoFocus()'
might expire and an incorrect failed AF callback might be
generated to the client. What this change does is to
immediately unblock the thread waiting for AF status after
the configuration for stopping AF. This way we are
effectively skipping the wait on the OMX component.
Change-Id: Ieda419b3ceee20eee80b543a00cd59b8f51d1cbe
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| ac0cf36b98237ec911f49e7b1b93ef6464666e48 |
|
07-Feb-2012 |
Emilian Peev <epeev@mm-sol.com> |
CameraHal: Various AF related fixes
- In case of AF timeout the focus callback was being
disabled. This callback will not get re-enabled
again until preview is restarted.
- Cancel AF is not working properly. Depending on the
timing the off status event might not reach 'doAutoFocus()'.
- This change also replaces the 'mDoAFSem' semaphore with
a condition variable.
Change-Id: I2ab7d87a05d97435aa6e67a122cc37a975794fc2
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.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/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 7a1746145a89cca0dafe26478a7675c15d5623a3 |
|
23-Nov-2011 |
Akwasi Boateng <akwasi.boateng@ti.com> |
CameraHAL: Fixes a couple of corner cases with AF and capture
- On some occasions during monkey tests, both the AF callback
and the shutter callback can be delayed just enough to
encounter the OMX component in loaded state. Usually this happens
when the camera is getting closed and this scenario should be
properly handled by exiting immediately without trying to trigger
any callbacks to the client.
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: Ia18faf471a8e10579b09973178d73e69e782c63c
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| b92d77425f939a35c0404a5317c3dcd6c2008ecb |
|
30-Nov-2011 |
Milen Mitkov <mmitkov@mm-sol.com> |
CameraHAL: Perform focus even if CAF has failed
Fixes b/5534973
Used to force focus if CAF has failed (before capture). CAF's state is
'failed' even if a scene change is detected only.
Change-Id: I0878a9f862b7800b566e578efdfa62baec7e5889
Signed-off-by: Milen Mitkov <mmitkov@mm-sol.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 05ea07dfe04d915b4288d3e71afbf70f8082fea4 |
|
16-Nov-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Use Different Timeout for Video Mode
Select AF timeout based on whether or not we are in
video mode.
b/5492725
Change-Id: I2fa722e6a3a7c149488ddb29ce44262914d19e38
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 2136042f80a20aeeef3ece24bab027c401426334 |
|
24-Oct-2011 |
Milen Mitkov <mmitkov@mm-sol.com> |
CameraHAL: Setting focus mode shouldnt start focus scanning
Part of the fix for b/5591797.
Use the new index OMX_TI_IndexAutofocusEnable to control
the AF algorithm when it should start scanning.
Until now, setting the focus to almost any mode
caused (unwanted) scanning.
Also, "Infinity" focus should actually have the
ability to perform scanning.
Change-Id: Iaa0f46a17d63acdd8f43b4b2b011f68fc7506165
Signed-off-by: Milen Mitkov <mmitkov@mm-sol.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 3c272a993dfc4ca153b09e5ec1e651f75eab90c4 |
|
28-Oct-2011 |
Milen Mitkov <mmitkov@mm-sol.com> |
CameraHAL: Return status after CAF finishes
If the user initiates autofocus while CAF
is scanning (e.g. when capturing),
wait until CAF finishes and just then
notify the focus subscribers.
bug:5514415
Change-Id: I971783c74f9977755cc93cdba964e4fcd3a2ab0a
Signed-off-by: Milen Mitkov <mmitkov@mm-sol.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 030e1a5962195aa5914e76e3d071669869555a9f |
|
26-Oct-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Check state in doAutoFocus
Check the state in doAutoFocus and return if we are not in the
AF_STATE. If user/monkey is pressing all over the screen, this
will result in multiple autoFocus/cancelAutoFocus calls until
the last autoFocus call comes when the user/monkey stop pressing
preview window. This will result in multiple CAMERA_PERFORM_AUTOFOCUS
commands being queued in OMXCameraAdapter's CommandHandler that will
all eventually need to be serviced which will result in multiple
doAutoFocus calls. This is the reason why we need to check the
state in the beginning of the function and return if we are not
focusing.
Change-Id: If245751a296604bca511ad237b769be24175cbc6
Signed-off-by: Tyler Luu <tluu@ti.com>
related-to-bug: 5472396
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| b192289737a7616f76a1cc236ed3cbc704696c03 |
|
27-Oct-2011 |
Akwasi Boateng <akwasi.boateng@ti.com> |
Only return error for Invalid state
Return error only for when component is in
Invalid state and we make any focus calls
Change-Id: I2efc3fb7859eca713b0ad738b7122ea8f36561c2
Signed-off-by: Akwasi Boateng <akwasi.boateng@ti.com>
related-to-bug: 5472396
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| fd705eb8b757a4f3d1d80b736cf20cade04524d7 |
|
21-Oct-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Fixes for #testFocusDistance
1. Seperate OMXCameraAdapter cancelAutoFocus with unsetting focus
lock. Adding new internal parameter to unlock focus from the
cancelAutoFocus in CameraHal. We need to cancel auto focus during
stop preview in case it is still running. If we do the unlock in
OMXCameraAdapter then, focus distance can change after stopPreview.
2. If autoFocus or takePicture comes after startPreview but before
the first preview frame comes, then sometimes the focus distance
queried after the calls won't be correct since OMX camera might
still be transitioning.
3. Update focus distances when focus is running.
b/5473673
Change-Id: I5a27d78aef437a1601a68e8c08fa860f04fc0c55
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 8a35a0ca4d30702b693c92f8cee360a8d102f49e |
|
18-Oct-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Re-apply CAF after canceling auto focus
Sometimes CAF is not restarted after canceling AF, go ahead
and re-apply CAF for this case.
b/5475271
Change-Id: I425bd94401aa6b9dcd5eed5c7294d7d88ddddfc0
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 5458bdc45048501d1919b14d22456de91f7e8950 |
|
06-Oct-2011 |
Tyler Luu <tluu@ti.com> |
omap4xxx: camera: only set CameraAreas if changed
Partial fix for b/5371242
Add logic to compare areas for metering and focus before calling
SetConfig for the respective indices so we only set the areas if
the areas have changed
Change-Id: Id6b55e3d8e78557f45b92a5afefdb8298450da61
Signed-off-by: Tyler Luu <tluu@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| f2ac1cc4c58440d94972f0015f50bcbb13838611 |
|
03-Sep-2011 |
Atanas Stefov <astefov@mm-sol.com> |
omap4xxx: camera: update Focus areas in setParameters, not in setFocusMode
Fixes b/5429270
When you touch to focus, the camera app calls setParameters to pass the focus
areas to the Ducati, followed by a call to autoFocus to start AF. Because the
focus areas were not getting updated instantly in the camera HAL before AF
began, on the one hand, and because the Ducati locks the focus regions after AF
begins, the AF region settings were being ignored.
This patch allows focus areas to be set immediately. Region priority is set in
doAutoFocus() when non-zero area is set in FOCUS_REGION.
Change-Id: I90c86f9de0d090f24b8595b325dbf06f1f718630
Signed-off-by: Iliyan Malchev <malchev@google.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| f50bf42f39a1d1ca8505d198b41c557e8ca83668 |
|
05-Oct-2011 |
Heechan Park <heech.park@samsung.com> |
Enabling Fast Shot2shot by disabling AF scan in the CAF mode
bug:5219431
Signed-off-by: Heechan Park <heech.park@samsung.com>
Change-Id: I5659f94273e6e4b79395742edb00799a64ecfd46
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| bbdc0fa0b8720bcfcf602861f62802c1fa1995c4 |
|
23-Sep-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Timing issue in returning focus callback
If the CommandHandler thread in OMXCameraAdapter preempts
the main thread before the AF state can be commited, there
was a chance that we would never send a focus callback.
This patch makes returnFocusStatus check for next state as
well as current state.
Change-Id: I7dfd68061ab5391bea1d12f5c978dba7544bfc9a
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 0e2a9f1fabc12a1a1123f8374d0e4d6faf5a2d62 |
|
20-Sep-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Changes to 3A lock implementation
1) Only take user set values for AE and AWB locks. Decouple
interaction between AE/AWB locks and AF/takePicture/stopPreview
2) When in CAF mode, if we query AF and see that focus is already
locked, we do not have to call SetConfig for OMX_IndexConfigFocusControl.
Just return the status to upper layers instead.
3) If user doesn't call cancelAutoFocus after a doAutoFocus call, we
need to forcefully unlock AF to ensure we do a scan. This would also
essentially render CAF as normal auto AF.
bug:5356404
Change-Id: I5bb840ca0122d8a9387f72290d2b421703dba23d
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 2f15c6a9f1d24904705ddab6a6c005126e8846dd |
|
21-Sep-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL: CTS fixes related to #testMeteringAreas
- The status of "parseAreas()" should always be checked
in order to return proper error code in case of invalid
input arguments.
- If the input metering areas are more than the supported
ones, then always return an error.
- 'parseAreas()' expects the buffer size, not the string
length.
- Refactors "parseFocusAreas()' to the more general
'parseAreas()'.
Change-Id: I4c70bcaa3c676f525b721916cc39c66db5e0fc17
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 9dc08c5fb736308cfca6659f66b14165b265baeb |
|
19-Sep-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Lock focus after AF completion
1) Add API to use OMX_IndexConfigImageFocusLock to lock autofocus
2) Remove FIXME to always return true status when CAF is set
Change-Id: Ie195206243bc1f750954def5f4f9f4466295bc7c
b/5338488
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 7d56715ab78f6b4be347597dc439d598cfe47dc9 |
|
14-Sep-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL:CTS: Lock AE,AWB irrespective of focus lock status
This is needed to pass testAutoWhiteBalanceLock and testAutoExposureLock
CTS tests
Change-Id: I96a88a72d6b5b3503ff9d215ba56746576892cdf
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.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/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| ba027fc89ec3950e1ac2f95fcc3f1002442ddabb |
|
12-Sep-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL CTS: Fix for #testAutoExposureLock, #testAutoWhiteBalanceLock
Locks were not retained if the user forces the lock to true
before calling autoFocus. This patch addresses this scenario.
Change-Id: I2b5161806f8123b3042d46bc856773f0d4701458
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 9b981b1785b6758b2dc8b147587188e5cf0d893d |
|
09-Sep-2011 |
Akwasi Boateng <akwasi.boateng@ti.com> |
Destroy and recreate semaphore in case of timeout
Destroy and recreate semaphor during timeout
and remove event from event queue.
Change-Id: Id9428ff58a55f90a6807776327bfba1961d9089d
Signed-off-by: Akwasi Boateng <akwasi.boateng@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| f5f41aa7943adde4e7bfb3fc181de154c4b0b9b0 |
|
30-Aug-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL: Re-enable CAF status query from Ducati
This requires ducati fixes for CAF to be present.
Change-Id: I6a43c30be2d293f42d4761989b3b70aa1444f7f5
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 708ed7306c85286aa50d05ba15e0c33106e52ed0 |
|
08-Sep-2011 |
Iliyan Malchev <malchev@google.com> |
Revert "Revert "CameraHAL : Multiple focus and exposure areas support""
This reverts commit 72bac2af47f73167bd288bc7278e5496ccabe6f4.
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 72bac2af47f73167bd288bc7278e5496ccabe6f4 |
|
07-Sep-2011 |
Iliyan Malchev <malchev@google.com> |
Revert "CameraHAL : Multiple focus and exposure areas support"
This reverts commit bd9754a1b2c8d5e0a8788d0e42d018857bfef7a7.
Conflicts:
camera/inc/OMXCameraAdapter/OMXCameraAdapter.h
Change-Id: Iad51c457b05de9b5492061b8402e508a6c5b42bf
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| bd9754a1b2c8d5e0a8788d0e42d018857bfef7a7 |
|
26-Aug-2011 |
Milen Mitkov <mmitkov@mm-sol.com> |
CameraHAL : Multiple focus and exposure areas support
Adds support for multiple focus and exposure areas and
also correctly returning the number of maximum supported
focus and exposure areas.
- Patch set 4: converting the coordinates,
which are sent to 3A in the range 0 - 255. Both Focus
and Exposure algorithms use this range
- Patch set 5: Handling special area (0, 0, 0, 0, 0),
rebasing and also memory allocation alignment to 4K chunks.
- Patch set 6: Freeing the alloc'd buffer in case of error.
Change-Id: I45bdd4309b75ac4d50deb05e97120362cdb1937b
Signed-off-by: Milen Mitkov <mmitkov@mm-sol.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 97e6bcc45eb2161c10761abc4fbf12ce3e1d52c8 |
|
31-Aug-2011 |
Tyler Luu <tluu@ti.com> |
CameraHAL: Fixes memory leaks inside ANativeWindowDisplayAdapter
- Every call to 'allocateBuffer()' is allocating a
'buffers' array on the heap, which is never used
and never released.
- Every call to 'setFrameProvider()' is instantiating a
new FrameProvider instance, which is never released.
Change-Id: I73ee9d35d9cb32709078334d199932fe78c2b7bb
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/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| d55379a7e975f992db1d10bba425f456447d14a8 |
|
30-Aug-2011 |
Tyler Luu <tluu@ti.com> |
CameraHAL: Adds locking when accessing 'mFocusAreas'
- This is due to the access pattern of 'mFocusAreas.
Currently both 'setFocusMode()' and
'setParametersFocus()' can in parallel try to
write/read from this Vector. A race condition is
possible, in which the former method can clear a
focus area, while the latter method is trying to
increment its strong pointer. This will inevitably
result in a segfault.
Change-Id: I0e94d18326b85c20f73296d31d980b9c39685c32
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/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 85c859b69b3c003b8db810371e24fe41599fc7de |
|
26-Aug-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL: Adds support for 'autoFocus()' calls during CAF
- Previously during CAF any calls for doing AF were
immediately returning status. The patch will check if
CAF has succeeded in locking and if this is not the case
it will temporarily switch to 'auto' triggering a full
AF sweep. CAF is again restored afterwards.
- Additionally this patch adds support for canceling AF
during 'PREVIEW_STATE' state, which is needed in order
to release the 3A lock after AF
Change-Id: Ie8c9b77fb134e63ed668a22453c1672b34488d94
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 8cb48e582f4f3c93aa25159c1116a7c83bfa388a |
|
25-Aug-2011 |
Sundar Raman <sunds@ti.com> |
Camera HAL: Fixes for Face prioritized 3A, cancelAF
1. Face prioritized 3A is enabled for AF, AE (for AE it is disabled)
2. White balance modes, exposure are allowed to be changed when face detection is ON
3. Focus metering area is ignored when face detection is ON
4. CancelAF is fixed to not retain the focus mode for CAF and infinity modes
Change-Id: I43650069d4de95815381974072f5b9afabf4fc46
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 00479a8f1d791824870513b8b0b9edd67d2560ff |
|
25-Aug-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL: OMX algo priority re-design
- Allows stacking of different algorithm priorities.
- Resolves an issue with AF not functioning after
one iteration.
- Contains a couple of fixes related to WB and
Exposure priority modes.
Signed-off-by: Emilian Peev <epeev@mm-sol.com>
Change-Id: I9c2848e776c727cd9cc3691221621f895dc5507b
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| c492aa718bc3f43eaf689b72595352f5348a0c39 |
|
12-Aug-2011 |
Tyler Luu <tluu@ti.com> |
Unlock AE/AWB locks during cancel AF
Change-Id: I1320bb9dbdf92ad1f194b32ff78aef7088d326ff
Original-author: Akwasi Boateng <akwasi.boateng@ti.com>
Signed-off-by: Akwasi Boateng <akwasi.boateng@ti.com>
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| e9ab1f4f653c21c2b526af02ceed12ecb935752c |
|
24-Aug-2011 |
Sundar Raman <sunds@ti.com> |
CameraHAL: Add support for FOCUS_MODE_CONTINUOUS_PICTURE
This patch adds HAL support for FOCUS_MODE_CONTINUOUS_PICTURE
which is needed for enabling CAF in still image preview.
Although the HAL behavior is same for both VIDEO and STILL
CAF, by setting EFocusControlAuto for ducati, the ducati
distinguishes STILL and VIDEO CAF internally based on
Operating mode (pipeline that is selected - video or zsl)
Change-Id: I808d41620caacca94dd65985c467f41417dee6d8
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| aa6e62e279cb54ae76c55ba9f8d02da230ce34e7 |
|
16-Aug-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Adjust FD callbacks to updated javadoc
FD callback behavior is updated in latest javadoc
patch "Improve camera face detection javadoc."
Change-Id: I963628ae55eec62083c25d34bbb380ae6673e431
Signed-off-by: Tyler Luu <tluu@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 9e5cb561cc54d061fe9f3d05eae78f6efb70f2c2 |
|
17-Aug-2011 |
Tyler Luu <tluu@ti.com> |
CameraHal: Fixes related to CTS test #testFocusAreas
- Sanity checks should be performed on the individual
areas for the test to pass.
- On invalid configuration CameraParameters should
revert to the last known good configuration.
Change-Id: I9026f287e884835a98c835e8f949ad4441c030bd
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/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|
| 80c50ac56bfa97be0cf04332ec1d314637c8770f |
|
09-Aug-2011 |
Sundar Raman <sunds@ti.com> |
Lock AE and AWB after AF
Change-Id: I12f1037be3d890b50c5413925d3084a2cf5256aa
Signed-off-by: Sundar Raman <sunds@ti.com>
/hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXFocus.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/omap4xxx/camera/OMXCameraAdapter/OMXFocus.cpp
|