The APEX macros always rounded to int, losing too much precision. Ensure
that we always keep at least two decimal digits.
The more precise F-number comes from the value recorded by the camera
closed source driver.
Added a new macro APEX_SHUTTER_TO_EXPOSURE(x) (credit to tryptophane).
Change-Id: Ief43c15c6517d8dc48d4d4bc9e93df9eb01e6b91
This libsecion is reverse engineered from the libsecion.so blob and then
written based on the Exynos 5 libion available in AOSP.
Change-Id: Ibe69047c78491e3c7f3173b18fcabdf327fcfbd0
Signed-off-by: angelsl <hidingfromhidden@gmail.com>
* Tune the governor for better power usage and interactivity
* Reset tuning parameters if governor changes
* Cleanup
Change-Id: Ibe60ece836a0e56ba58e109bbea26cbd54d75421
Stock gralloc doesn't have these alignment hacks. In fact
they currently do nothing and won't until we fix HWC.
Change-Id: I3427cf3fed84a023ba6ed69b0e0fe0b63ea00886
This caused the ION pointer to get clobbered with a UMP
pointer when FIMC1 memory was requested.
After a while, camera would be unable to allocate buffers
due to ION memory not being freed properly.
Change-Id: I1ba1d27da924a0bb81631548e83c7f3e5789f319
Building libsecril-client from source works perfectly well
on the i815. It will probably work well with the gsm devices
as well.
Change-Id: I4f394555d82fb48a86ea52212d9fb56ca0e8acd3
Two reverts squashed, due to Mali-derping being fixed
in frameworks/native:
Revert "gralloc: avoid using framebuffer"
This reverts commit 5125ccc5b6.
Revert "gralloc: Send first 2 FB buffers to carveout and next to UMP"
This reverts commit d288deb284.
Change-Id: I530dc255b7543e03d0e8277d3ad12ed11d6649ab
Mobile's blobs behave this way, except they don't do the
4k alignment done by the FIMC1 allocs.
The 4k alignment should fix issues such as NHK World Live TV,
but fails to do so.
Change-Id: I1ee4cd13e23f9f2f6c6616ee9eed1096b571a82c
Mobile's blobs don't appear to have been compiled with this
present in their headers, and none of the Insignal sources
actually use this.
Change-Id: Ib8611f6da90ea78aa8eec451c76f56ddb32b45a4
This is the story of poor }. It is a painful saga.
Samsung left } floating inside the galaxy of framebuffer_alloc,
unable to join its brethren on the planet of STANDARD_LINUX_SCREEN
when they were shifted out of the #ifdef dimension.
codeworkx brutally eliminated poor } from the galaxy, it was
nowhere to be seen. codeworkx then took pity on the } and
placed it back on the planet of STANDARD_LINUX_SCREEN, but
placed it on a continent where it was all alone, unable to
ever see its mate {
Take pity on poor }, let it rejoin its people on the correct
continent of the planet STANDARD_LINUX_SCREEN, so they may
all shift out of the #ifdef dimension together.
Change-Id: I7a700b73ccd2c91f91d9af3704930759f46978c7
Daniel Hillenbrand