1<?xml version="1.0" encoding="UTF-8" standalone="yes"?> 2<!-- Copyright (C) 2021 The Android Open Source Project 3 4 Licensed under the Apache License, Version 2.0 (the "License"); 5 you may not use this file except in compliance with the License. 6 You may obtain a copy of the License at 7 8 http://www.apache.org/licenses/LICENSE-2.0 9 10 Unless required by applicable law or agreed to in writing, software 11 distributed under the License is distributed on an "AS IS" BASIS, 12 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 13 See the License for the specific language governing permissions and 14 limitations under the License. 15--> 16 17<!-- The Sample Tuner Testing Configuration. 18 Name the customized xml with "tuner_vts_config.xml" and push into the device 19 "/vendor/etc" path. Please use "tuner_testing_dynamic_configuration.xsd" to verify the xml. 20 The version section contains a “version” tag in the form “major.minor” e.g version=”1.0” 21 This shows the tuner dynamic configuration version. --> 22<TunerConfiguration version="1.0" xmlns:xi="http://www.w3.org/2001/XInclude"> 23 <!-- Hardware Configuration section contains the configurations of all the hardwares 24 that would be used in the tests. In the "dataFlowConfiguration" section, each data flow 25 under test has its required/optional hardwares. The ids configured in the 26 "dataFlowConfiguration" would be used to connect the hardware to each data flow test. --> 27 <hardwareConfiguration> 28 <!-- Frontends section: 29 This section contains configurations of all the frontends that would be used 30 in the tests. 31 - This section is optional and can be skipped to use the default fe settings. 32 - The default settings can be found in the sample_tuner_vts_configurations.xml. 33 - The users can also override the default frontend settings using id="FE_DEFAULT". 34 - The users can configure 1 or more frontend elements in the frontends sections. 35 36 Each frontend element contain the following attributes: 37 "id": unique id of the frontend that could be used to connect to the test the 38 "dataFlowConfiguration" 39 "type": the frontend type. The enums are defined in the xsd. 40 "isSoftwareFrontend": if the test environment is using hardware or software 41 frontend. If using software, a ts input file path needs to be configured. 42 "softwareFeInputPath": used as the source of the software frontend. 43 "connectToCicamId": if the device supports frontend connecting to cicam, the target 44 cicam id needs to be configured here. Supported in Tuner 1.1 or higher. 45 "frequency": the frequency used to configure tune and scan. 46 "endFrequency": the end frequency of scan. Supported in Tuner 1.1 or higher. 47 48 Each frontend element also contains one and only one type-related "frontendSettings". 49 - The settings type should match the frontend "type" attribute. 50 - For example, when frontend type="DVBT", dvbtFrontendSettings can be configured. 51 - This is optional and skipping the settings would pass a setting with frequency 52 config only to the hal. 53 --> 54 <frontends> 55 <frontend id="FE_DEFAULT" type="DVBT" isSoftwareFrontend="true" 56 connectToCicamId="0" frequency="578000" endFrequency="800000"> 57 <dvbtFrontendSettings bandwidth="8" transmissionMode="128" isHighPriority="1"/> 58 </frontend> 59 <frontend id="FE_DVBS_0" type="DVBS" isSoftwareFrontend="true" 60 connectToCicamId="0" frequency="578000" endFrequency="800000"> 61 </frontend> 62 </frontends> 63 <!-- Filter section: 64 This section contains configurations of all the filters that would be used in the tests. 65 - This section is optional and can be skipped to use the default filter settings. 66 - The default settings can be found in the sample_tuner_vts_configurations.xml. 67 - The users can also override the default filter settings using 68 - id="FILTER_AUDIO_DEFAULT" or "FILTER_VIDEO_DEFAULT". 69 - The users can configure 1 or more filter elements in the filters sections. 70 71 Each filter element contain the following attributes: 72 "id": unique id of the filter that could be used to connect to the test the 73 "dataFlowConfiguration" 74 "mainType": the main filter type. The enums are defined in the xsd. 75 "subType": the sub filter type. The enums are defined in the xsd. 76 "bufferSize": the buffer size of the filter in hex. 77 "pid": the pid that would be used to configure the filter. 78 "useFMQ": if the filter uses FMQ. 79 80 Each filter element also contains at most one type-related "filterSettings". 81 - The settings type should match the filter "subType" attribute. 82 - For example, when filter subType is audio or video, the avFilterSettings can be 83 configured. 84 - This is optional and skipping the settings would pass a setting with tpid config 85 only to the hal. 86 --> 87 <filters> 88 <filter id="FILTER_AUDIO_DEFAULT" mainType="TS" subType="AUDIO" 89 bufferSize="16777216" pid="257" useFMQ="false" monitorEventTypes="3"> 90 <avFilterSettings isPassthrough="false"> 91 <audioStreamType>2</audioStreamType> 92 </avFilterSettings> 93 </filter> 94 <filter id="FILTER_VIDEO_DEFAULT" mainType="TS" subType="VIDEO" 95 bufferSize="16777216" pid="256" useFMQ="false" monitorEventTypes="3"> 96 <avFilterSettings isPassthrough="false"> 97 <videoStreamType>2</videoStreamType> 98 </avFilterSettings> 99 </filter> 100 <filter id="FILTER_TS_RECORD_0" mainType="TS" subType="RECORD" 101 bufferSize="16777216" pid="257" useFMQ="false"> 102 <recordFilterSettings tsIndexMask="1" scIndexType="NONE"/> 103 </filter> 104 <filter id="FILTER_IP_IP_0" mainType="IP" subType="IP" bufferSize="16777216" useFMQ="false"> 105 <ipFilterConfig ipCid="1"> 106 <srcIpAddress isIpV4="true" ip="192 168 1 1"/> 107 <destIpAddress isIpV4="true" ip="192 168 1 1"/> 108 </ipFilterConfig> 109 </filter> 110 </filters> 111 <!-- Dvr section: 112 This section contains configurations of all the dvrs that would be used in the tests. 113 - This section is optional and can be skipped if DVR is not supported. 114 - The users can configure 1 or more dvr elements in the dvrs sections. 115 116 Each dvr element contain the following attributes: 117 "id": unique id of the dvr that could be used to connect to the test the 118 "dataFlowConfiguration" 119 "type": the dvr type. 120 "bufferSize": the dvr buffer size. 121 "statusMask": register callbacks of specific status. 122 "lowThreshold": the dvr status low threshold. 123 "highThreshold": the dvr status high threshold. 124 "dataFormat": the dvr data format. 125 "packetSize": the dvr packet size. 126 "inputFilePath": the dvr playback input file path. Only required in playback dvr. 127 --> 128 <dvrs> 129 <dvr id="DVR_PLAYBACK_0" type="PLAYBACK" bufferSize="4194304" 130 statusMask="15" lowThreshold="4096" highThreshold="32767" 131 dataFormat="TS" packetSize="188" inputFilePath="/data/local/tmp/segment000000.ts"/> 132 <dvr id="DVR_RECORD_0" type="RECORD" bufferSize="4194304" 133 statusMask="15" lowThreshold="4096" highThreshold="32767" 134 dataFormat="TS" packetSize="188"/> 135 <dvr id="DVR_PLAYBACK_1" type="PLAYBACK" bufferSize="4194304" 136 statusMask="15" lowThreshold="4096" highThreshold="32767" 137 dataFormat="ES" packetSize="188" inputFilePath="/data/local/tmp/test.es"/> 138 </dvrs> 139 </hardwareConfiguration> 140 141 <!-- Data flow configuration section connects each data flow under test to the ids of the 142 hardwares that would be used during the tests. --> 143 <dataFlowConfiguration> 144 <clearLiveBroadcast frontendConnection="FE_DEFAULT" 145 audioFilterConnection="FILTER_AUDIO_DEFAULT" 146 videoFilterConnection="FILTER_VIDEO_DEFAULT" 147 ipFilterConnection="FILTER_IP_IP_0" 148 dvrSoftwareFeConnection="DVR_PLAYBACK_1"/> 149 <scan frontendConnection="FE_DEFAULT"/> 150 <dvrPlayback dvrConnection="DVR_PLAYBACK_1" 151 audioFilterConnection="FILTER_AUDIO_DEFAULT" 152 videoFilterConnection="FILTER_VIDEO_DEFAULT"/> 153 <dvrRecord hasFrontendConnection="true" 154 frontendConnection="FE_DEFAULT" 155 recordFilterConnection="FILTER_TS_RECORD_0" 156 dvrRecordConnection="DVR_RECORD_0" 157 dvrSoftwareFeConnection="DVR_PLAYBACK_1"/> 158 </dataFlowConfiguration> 159</TunerConfiguration> 160