summaryrefslogtreecommitdiffstats
path: root/include/camera
diff options
context:
space:
mode:
authorEino-Ville Talvala <etalvala@google.com>2011-04-21 09:23:15 -0700
committerEino-Ville Talvala <etalvala@google.com>2011-04-25 09:33:48 -0700
commit44ada657945587d74e0404fd093da8027b9fdc55 (patch)
treed279844012334d4b841b3be24fc65a485b3d8c78 /include/camera
parente2e3f479fe160e8ba00321ada2c61d4bcaf5be4d (diff)
downloadframeworks_av-44ada657945587d74e0404fd093da8027b9fdc55.zip
frameworks_av-44ada657945587d74e0404fd093da8027b9fdc55.tar.gz
frameworks_av-44ada657945587d74e0404fd093da8027b9fdc55.tar.bz2
Clarify the meaning of weight in the focus and metering area HAL.
Weigh values must be less than 1000, but have no restriction on their sum. Weights should be interpreted as per-pixel values, meaning larger areas will have more influence over focus/metering than smaller areas of the same weight. Change-Id: I988b74f988ddba2ff0c49d078ff3174b47cbae18
Diffstat (limited to 'include/camera')
-rw-r--r--include/camera/CameraParameters.h21
1 files changed, 12 insertions, 9 deletions
diff --git a/include/camera/CameraParameters.h b/include/camera/CameraParameters.h
index e272839..db81721 100644
--- a/include/camera/CameraParameters.h
+++ b/include/camera/CameraParameters.h
@@ -265,11 +265,12 @@ public:
// (-1000,-1000) is the upper left point. (1000, 1000) is the lower right
// point. The length and width of focus areas cannot be 0 or negative.
//
- // The fifth element is the weight. The weight ranges from 1 to 1000.
- // The sum of the weights of all focus areas must be 1000. Focus areas
- // can partially overlap and the driver will add the weights in the
- // overlap region. But apps should not set two focus areas that have
- // identical coordinates.
+ // The fifth element is the weight. Values for weight must range from 1 to
+ // 1000. The weight should be interpreted as a per-pixel weight - all
+ // pixels in the area have the specified weight. This means a small area
+ // with the same weight as a larger area will have less influence on the
+ // focusing than the larger area. Focus areas can partially overlap and the
+ // driver will add the weights in the overlap region.
//
// A special case of single focus area (0,0,0,0,0) means driver to decide
// the focus area. For example, the driver may use more signals to decide
@@ -327,10 +328,12 @@ public:
// is the lower right point. The length and width of metering areas cannot
// be 0 or negative.
//
- // The weight ranges from 1 to 1000. The sum of the weights of all metering
- // areas must be 1000. Metering areas can partially overlap and the driver
- // will add the weights in the overlap region. But apps should not set two
- // metering areas that have identical coordinates.
+ // The fifth element is the weight. Values for weight must range from 1 to
+ // 1000. The weight should be interpreted as a per-pixel weight - all
+ // pixels in the area have the specified weight. This means a small area
+ // with the same weight as a larger area will have less influence on the
+ // metering than the larger area. Metering areas can partially overlap and
+ // the driver will add the weights in the overlap region.
//
// A special case of all-zero single metering area means driver to decide
// the metering area. For example, the driver may use more signals to decide