Searched full:rules (Results 1 – 25 of 82) sorted by relevance
1234
/hal_espressif-3.4.0/.gitlab/ci/ |
D | README.md | 9 - [How to Develop With `rules.yml`?](#how-to-develop-with-rulesyml) 12 - [How to Add a New `Rules` Template?](#how-to-add-a-new-rules-template) 14 - [Naming Rules](#naming-rules) 15 - [Common Naming Rules](#common-naming-rules) 16 - [`if` Anchors Naming Rules](#if-anchors-naming-rules) 17 - [`rules` Template Naming Rules](#rules-template-naming-rules) 76 ## How to Develop With `rules.yml`? 97 .rules:build:docs: 98 rules: 112 - .rules:build:docs [all …]
|
D | rules.yml | 7 - "tools/ci/static-analysis-rules.yml" 201 # Rules # 203 .rules:protected: 204 rules: 207 .rules:protected-no_label: 208 rules: 211 .rules:dev: 212 rules: 216 .rules:tag:release: 217 rules: [all …]
|
D | build.yml | 48 - .rules:build:target_test 57 - .rules:build:integration_test 125 - .rules:build:unit_test-esp32 133 - .rules:build:unit_test-esp32s2 141 - .rules:build:unit_test-esp32s3 148 - .rules:build:unit_test-esp32c3 176 - .rules:build:example_test-esp32 218 - .rules:build:example_test-esp32 226 - .rules:build:example_test-esp32s2 234 - .rules:build:example_test-esp32s3 [all …]
|
D | target-test.yml | 50 - .rules:test:example_test-esp32 57 - .rules:labels:weekend_test 70 - .rules:test:example_test-esp32 75 - .rules:test:example_test-esp32s2 80 - .rules:test:example_test-esp32c3 85 - .rules:test:example_test-esp32s3 178 - .rules:labels:iperf_stress_test 315 - .rules:test:custom_test-esp32 320 - .rules:test:custom_test-esp32s2 325 - .rules:test:custom_test-esp32c3 [all …]
|
D | docs.yml | 32 .doc-rules:build:docs: 33 rules: 53 - .doc-rules:build:docs 80 - .doc-rules:build:docs 98 # Doc jobs have a lot of special cases, we specify rules here directly instead 103 rules: 118 rules: 138 rules: 173 rules: 196 rules: [all …]
|
D | pre_check.yml | 23 - .rules:protected 30 - .rules:dev 39 - .rules:protected 58 - .rules:patterns:python-files 115 - .rules:build 124 - .rules:build 133 - .rules:build 149 - .rules:build:target_test 181 - .rules:tag:release
|
D | assign-test.yml | 20 - .rules:build:example_test 42 - .rules:build:custom_test 64 - .rules:build:component_ut 90 - .rules:build:unit_test 110 - .rules:test:integration_test 134 extends: .rules:ref:master-schedule
|
D | static-code-analysis.yml | 5 - .rules:patterns:clang_tidy 15 RULES_FILE: ${CI_PROJECT_DIR}/tools/ci/static-analysis-rules.yml 31 - .rules:patterns:python-files 94 - .rules:patterns:static-code-analysis-preview 118 - .rules:protected
|
D | deploy.yml | 12 - .rules:protected-no_label 24 - .rules:ref:master-schedule-always 58 - .rules:test:submodule
|
D | host-test.yml | 2 extends: .rules:test:host_test 21 - .rules:labels:nvs_coverage 70 - .rules:labels:fuzzer_test-weekend_test
|
/hal_espressif-3.4.0/.gitlab/ci/dependencies/ |
D | README.md | 7 1. Auto-generate some labels/rules we need and update them in `rules.yml` 16 - `matrix`: An array of sub-arrays, used to replicate rules by formatting strings. You can use the … 19 …` names. It indicates the `labels` and `patterns` will be included in all specified `rules` as well 20 … strings, used to replicate rules by adding postfix `-<item in deploy array>`. It indicates the ex… 22 ## How to use this file to generate `rules.yml` 71 2. create rules by `included_in` 84 …n in `rules.yml` with `labels`, and `rules`. Each mapping will generate a `rule` and all the requi…
|
D | generate_rules.py | 95 .rules:{0}: 96 rules: 109 self.rules = self.expand_rules() 115 Expand the matrix into different rules 209 for k, v in sorted(self.rules.items()): 289 ….add_argument('rules_yml', nargs='?', default=os.path.join(IDF_PATH, '.gitlab', 'ci', 'rules.yml'), 290 help='rules.yml file path') 302 dep_tree_graph = build_graph(writer.rules)
|
/hal_espressif-3.4.0/tools/ldgen/ |
D | linker_script.py | 34 Marker = collections.namedtuple('Marker', 'target indent rules') 70 rules = member.rules 72 del rules[:] 74 rules.extend(mapping_rules[target]) 92 rules = member.rules 94 for rule in rules:
|
/hal_espressif-3.4.0/tools/ci/ |
D | check_rules_yml.py | 18 Check if all rules in rules.yml used or not in CI yaml files. 59 if not item.endswith('rules.yml'): 73 if item.startswith('.rules:'): 90 if line.startswith('.rules:'): 109 ….add_argument('rules_yml', nargs='?', default=os.path.join(IDF_PATH, '.gitlab', 'ci', 'rules.yml'), 110 help='rules.yml file path')
|
D | check_type_comments.py | 32 Run Mypy check with global rules on the given file, return TRUE if Mypy check passes 42 Run Mypy check with rules for ignore list on the given file, return TRUE if Mypy check passes 51 - new python file -> run Mypy check with global rules 52 - existed file on ignore list -> run Mypy check with Global rules: 54 global check FAILS -> run Mypy check with Ignored rules 55 Global rules: Enforce type annotations for all functions in file 56 Ignored rules: Do not enforce untyped functions, check only already typed
|
D | check_tools_files_patterns.py | 60 …parser = argparse.ArgumentParser(description='check if all tools files are in rules patterns or ex… 62 default=os.path.join(IDF_PATH, '.gitlab', 'ci', 'rules.yml'), 74 …s test is used for making sure of all the tools dir files are recorded in .gitlab/ci/rules.yml to ' 80 …print('Please add these files or glob patterns to ".gitlab/ci/rules.yml" and put related files und…
|
/hal_espressif-3.4.0/ |
D | .pre-commit-config.yaml | 76 - id: check-rules-yml 77 name: Check rules.yml all rules have at lease one job applied, all rules needed exist 84 - id: check-generated-rules 85 name: Check rules are generated (based on .gitlab/ci/dependencies/dependencies.yml) 88 files: '\.gitlab/ci/dependencies/.+|\.gitlab/ci/rules\.yml'
|
/hal_espressif-3.4.0/components/driver/include/driver/ |
D | adc_types_deprecated.h | 20 * @brief ADC digital controller (DMA mode) conversion rules setting. 59 …The pattern table that defines the conversion rules for each SAR ADC. Each table has 16 items, in … 60 …enuation are stored. When the conversion is started, the controller reads conversion rules from the 61 …ne by one. For each controller the scan sequence has at most 16 different rules before repeating i… 76 * @brief ADC digital controller (DMA mode) conversion rules setting. 129 …The pattern table that defines the conversion rules for each SAR ADC. Each table has 16 items, in … 130 …enuation are stored. When the conversion is started, the controller reads conversion rules from the 131 …ne by one. For each controller the scan sequence has at most 16 different rules before repeating i… 165 * @brief ADC digital controller (DMA mode) conversion rules setting. 188 …The pattern table that defines the conversion rules for each SAR ADC. Each table has 7 items, in w… [all …]
|
/hal_espressif-3.4.0/docs/en/api-guides/ |
D | linker-script-generation.rst | 18 … by the components are collected, parsed and processed; and the placement rules generated is used … 196 … placements' has been mentioned as fallback placements when the placement rules ``rtc`` and ``nofl… 198 …here exists a ``default`` scheme which defines what the default placement rules should be. As the … 219 …ch contain pieces of information which, when put together, form placement rules that tell where to… 383 … the name ``default``. This scheme is special because catch-all placement rules are generated from… 389 These catch-all rules then effectively serve as fallback rules for those whose mappings were not sp… 472 … by name. If both are specified, then the nested sorting follows the same rules discussed in https… 548 …ment rules are put into. It is an otherwise ordinary linker script, with a specific marker syntax … 550 To reference the placement rules collected under a ``target`` token, the following syntax is used: 607 …/* Placement rules generated from the processed fragments, placed where the marker was in the temp… [all …]
|
/hal_espressif-3.4.0/tools/ldgen/test/ |
D | test_generation.py | 103 rules = collections.defaultdict(list) 105 …rules['flash_text'].append(InputSectionDesc(ROOT, ['.literal', '.literal.*', '.text', '.text.*'], … 106 rules['flash_rodata'].append(InputSectionDesc(ROOT, ['.rodata', '.rodata.*'], [])) 107 rules['dram0_data'].append(InputSectionDesc(ROOT, ['.data', '.data.*'], [])) 108 rules['dram0_data'].append(InputSectionDesc(ROOT, ['.dram', '.dram.*'], [])) 109 rules['dram0_bss'].append(InputSectionDesc(ROOT, ['.bss', '.bss.*'], [])) 110 rules['dram0_bss'].append(InputSectionDesc(ROOT, ['COMMON'], [])) 111 rules['iram0_text'].append(InputSectionDesc(ROOT, ['.iram', '.iram.*'], [])) 112 rules['rtc_text'].append(InputSectionDesc(ROOT, ['.rtc.text', '.rtc.literal'], [])) 113 rules['rtc_data'].append(InputSectionDesc(ROOT, ['.rtc.data'], [])) [all …]
|
/hal_espressif-3.4.0/docs/en/api-reference/ |
D | kconfig.rst | 30 Kconfig Formatting Rules 50 rules. The checker checks all ``Kconfig`` and ``Kconfig.projbuild`` files in 53 checker cannot correct all rules and the responsibility of the developer is to
|
/hal_espressif-3.4.0/docs/en/contribute/ |
D | style-guide.rst | 10 Style guide is a set of rules which are aimed to help create readable, maintainable, and robust cod… 12 … try to keep rules simple enough, which means that they can not cover all potential cases. In some… 317 The same rules as for C apply. Where they are not enough, apply the following rules.
|
/hal_espressif-3.4.0/components/hal/esp32h2/include/hal/ |
D | adc_ll.h | 178 …* The pattern table that defines the conversion rules for each SAR ADC. Each table has 8 items, in… 179 …enuation are stored. When the conversion is started, the controller reads conversion rules from the 180 …* pattern table one by one. For each controller the scan sequence has at most 8 different rules be… 192 …* The pattern table that defines the conversion rules for each SAR ADC. Each table has 8 items, in… 193 …enuation are stored. When the conversion is started, the controller reads conversion rules from the 194 …* pattern table one by one. For each controller the scan sequence has at most 8 different rules be… 198 * @param pattern Stored conversion rules.
|
/hal_espressif-3.4.0/components/hal/esp32c3/include/hal/ |
D | adc_ll.h | 178 …* The pattern table that defines the conversion rules for each SAR ADC. Each table has 8 items, in… 179 …enuation are stored. When the conversion is started, the controller reads conversion rules from the 180 …* pattern table one by one. For each controller the scan sequence has at most 8 different rules be… 192 …* The pattern table that defines the conversion rules for each SAR ADC. Each table has 8 items, in… 193 …enuation are stored. When the conversion is started, the controller reads conversion rules from the 194 …* pattern table one by one. For each controller the scan sequence has at most 8 different rules be… 198 * @param pattern Stored conversion rules.
|
/hal_espressif-3.4.0/components/hal/esp32/include/hal/ |
D | adc_ll.h | 206 …* The pattern table that defines the conversion rules for each SAR ADC. Each table has 16 items, i… 207 …enuation are stored. When the conversion is started, the controller reads conversion rules from the 208 …* pattern table one by one. For each controller the scan sequence has at most 16 different rules b… 224 …* The pattern table that defines the conversion rules for each SAR ADC. Each table has 16 items, i… 225 …enuation are stored. When the conversion is started, the controller reads conversion rules from the 226 …* pattern table one by one. For each controller the scan sequence has at most 16 different rules b… 230 * @param pattern Stored conversion rules, see ``adc_digi_pattern_table_t``.
|
1234