diff options
| author | Amy Zhang <amyjojo@google.com> | 2020-07-27 14:50:10 -0700 |
|---|---|---|
| committer | Amy Zhang <amyjojo@google.com> | 2020-10-13 14:28:31 -0700 |
| commit | b13e3042f3e7e3ef972b8c7cffb398477e8b6f05 (patch) | |
| tree | a1892f73a9766ba6af0cf240ec175faed9a970be /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | 782aa9006b054905ba094420e12f10c3f35f3af1 (diff) | |
Make Tuner java framework and Tuner JNI adopt Tuner HAL 1.1
Please see the Tuner HAL 1.1 design doc here:
go/android_tuner_hal_1.1
In this CL, the Tuner framework and JNI start to use the
@1.1::IFilter.getId64Bit() API and @1.1::IFilterCallback.
Currently the 1.1 IFilterCallback passes two new 1.1 record filter
events: DemuxFilterTsRecordEvent and DemuxFilterMmtpRecordEvent.
Tuner Framework exposes a new API: getId64Bit() which calls
the native getId64Bit. Also Filter java will be using long id
instead of the previous int id.
The FilterCallback interface remains unchanged but the TsRecordEvent
and the MmtpRecordEvent carry more variables to pass the extra info
in version 1.1.
When the HAL implementation is on version 1.0 and calls
onFilterEvent, it still uses the extended TsRecordEvent and
MmtpRecordEvent but the 1.1 field will be set to invalid.
Related HAL interface can be referred here:
hardware/interfaces/tv/tuner/1.1
Test: make -j44 dist, atest android.media.tv.tuner.cts
Bug: b/159058358
Bug: 158816517
Change-Id: I8d52c0b2031eed9c54909e5bf233137c56eeb78f
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions