diff options
| author | Christine Franks <christyfranks@google.com> | 2021-01-06 11:42:11 -0800 |
|---|---|---|
| committer | Christine Franks <christyfranks@google.com> | 2021-01-26 12:12:32 -0800 |
| commit | b77631381641d5fe1bd0552bb88215fee2e97d6a (patch) | |
| tree | b9d8cca42a46c8bc66684a4428cbb563b8f6a1dc /rs/java/android/renderscript/ProgramVertexFixedFunction.java | |
| parent | 7cdfcd8a87681ef83bade6647520271184ef83ce (diff) | |
Add configurable mapping between color modes
There are two categories of color modes: the standard color modes, which
are defined and implemented in AOSP, and a reserved range of vendor color
modes, which are defined and implemented by the vendor. Currently, there
is no way to distinguish between two vendor's color modes that use the
same value within the reserved range. This will allow OEMs to specify a
hint as to which vendor's color mode definitions were used on the
original device. If the hint from the restored device matches the hint
on the new device, the color mode from the restored device can still be
considered valid for the new device if it is within the vendor reserved
range. If it does not match, the restored device's color mode value is
invalid on the new device, and must be replaced by the default on the
new device.
Bug: 167449433
Test: builds
Change-Id: Ie5ac0a2d783e1ea703e0342f5cdb41dca07d04d4
Diffstat (limited to 'rs/java/android/renderscript/ProgramVertexFixedFunction.java')
0 files changed, 0 insertions, 0 deletions