diff options
| author | Umang Jain <umang.jain@ideasonboard.com> | 2021-09-23 14:07:47 +0530 |
|---|---|---|
| committer | Umang Jain <umang.jain@ideasonboard.com> | 2021-09-27 22:24:58 +0530 |
| commit | 67adaf5ebf4fd2cafc64fa5821246cc5a57d331c (patch) | |
| tree | f91f06fd6529a897417386b764c91a5481f3781b /test/media_device/media_device_acquire.cpp | |
| parent | 11e9d192885d94cbe1e5d850315b8f2b4032d804 (diff) | |
android: camera_capabilities: Clarify CameraMetadata allocation
CameraMetadata's constructor take in number of entries and number of
bytes to be allocated for those entries. However, CameraMetadata is
already capable of resizing its container on the fly, in case more
entries are added to it. Hence, the numbers passed in during the
construction acts as hint values for initialization.
Clarify this in CameraCapabilities::requestTemplatePreview() and
remove the \todo, as the arguments and the \todo gives the perspective
that we need to be quite accurate with the numbers of entries / bytes,
which is not the case.
Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
Reviewed-by: Paul Elder <paul.elder@ideasonboard.com>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Diffstat (limited to 'test/media_device/media_device_acquire.cpp')
0 files changed, 0 insertions, 0 deletions