Searched refs:TSC (Results 1 – 25 of 29) sorted by relevance
12
| /Zephyr-latest/doc/project/ |
| D | working_groups.rst | 1 TSC Working Groups
7 The TSC, at its discretion, may establish working groups or subcommittees to
18 consultation with the TSC.
24 - All TSC members are eligible to join a working group as members, part of
25 the responsibilities being a TSC member.
41 responsible for leading meetings and representing the working group to the TSC.
63 - The elected Chair (and/or Co-Chair) is submitted to the TSC for confirmation.
64 - The TSC decides to accept the outcome or requests a new voting.
70 to the TSC.
73 shall raise the issue with the TSC or the relevant committee (Safety and
[all …]
|
| D | tsc.rst | 1 Technical Steering Committee (TSC)
4 TSC Member Role
7 The TSC role and its responsibilities is defined in the `Zephyr project charter`_.
12 A TSC member plays a pivotal role in shaping the technical direction of the
13 Zephyr Project. TSC members work collaboratively with other TSC members,
17 By fulfilling the rights and responsibilities below, TSC members contribute to
30 Exercise voting rights on important matters discussed within the TSC,
47 TSC members are expected to fulfill the following responsibilities, though it is
93 Appointed TSC Members
98 - Appointed TSC members have no term limits besides the term of their employment
[all …]
|
| D | project_roles.rst | 3 TSC Project Roles
9 TSC projects generally will involve *Maintainers*, *Collaborators*, and
12 **Maintainer**: lead Collaborators on an area identified by the TSC (e.g.
14 area’s representative on the TSC as needed. Maintainers may become voting
15 members of the TSC under the guidelines stated in the project Charter.
18 May become a Maintainer with approval of existing TSC voting members.
127 the TSC
137 Contributors nor Collaborators must be approved by the TSC before they can
149 may be requested by the TSC to retire from the role they are elected.
150 * Such a request needs to be raised as a motion in the TSC and be
[all …]
|
| D | code_flow.rst | 17 collaboration branch requires a justification and TSC approval. Collaboration branches
20 Zephyr, the introduction of fixes and new features, if approved by the TSC,
47 this timeline requires TSC approval.
|
| D | dev_env_and_tools.rst | 43 and a decision by the TSC or the Security working group. To summarize the above,
58 should belong to. A project maintainers or TSC member monitoring the inflow of
109 TSC and Working Groups
113 overall system works need to be reviewed by the TSC or the responsible Working
279 Note: Issue priorities are generally set or changed during the bug-triage or TSC
382 * - :guilabel:`TSC`
383 - TSC stands for Technical Steering Committee. The issue is to be discussed in the
384 following `TSC meeting`_ if time permits.
386 ….. _`TSC meeting`: https://github.com/zephyrproject-rtos/zephyr/wiki/Technical-Steering-Committee-…
|
| D | proposals.rst | 22 and must be vetted and discussed in the TSC before a target milestone is set.
40 If not though, an owner will be assigned after evaluation by the TSC.
45 - The TSC discusses new ``feature-request`` items regularly and triages them.
|
| D | release_process.rst | 80 occasions are rare and require a TSC approval and a justification. As a general
165 - TSC
362 Safety Working Groups and coordinated with the TSC.
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.x86 | 39 bool "Local APIC timer using TSC deadline mode"
44 Extremely simple timer driver based the local APIC TSC
51 choice for any x86 device with invariant TSC and TSC
55 bool "Local APIC timer using TSC time source"
61 If your CPU supports invariant TSC but no TSC deadline capability
62 then this choice will rely on the TSC as time source and the
64 You must know the ratio of the TSC frequency to the local APIC
87 int "TSC to local APIC timer frequency multiplier (N)"
91 int "TSC to local APIC timer frequency divisor (M)"
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 006_nomination.md | 12 The [TSC Project Roles] defines the main roles for the Zephyr Project, including
41 [TSC Project Roles]: <https://docs.zephyrproject.org/latest/project/project_roles.html>
|
| D | 008_bin-blobs.md | 5 labels: TSC
|
| D | 003_rfc-proposal.md | 13 This section targets end users, TSC members, maintainers and anyone else that might
|
| D | 007_ext-source.md | 5 labels: TSC
|
| /Zephyr-latest/boards/up-bridge-the-gap/up_squared/ |
| D | Kconfig.defconfig | 12 # TSC on this board is 1.5936 GHz, HPET and APIC are 19.2 MHz
|
| /Zephyr-latest/boards/intel/ehl/ |
| D | Kconfig.defconfig | 21 # TSC on this board is 1.9 GHz, HPET and APIC are 19.2 MHz
|
| /Zephyr-latest/doc/contribute/ |
| D | external.rst | 163 and accepted by the Technical Steering Committee (TSC) and, in some cases, by
173 detail, so that you are informed of the criteria used by the TSC and board in
178 TSC to assess the merit of the request. Optionally you can also create a Pull
181 #. Wait for feedback from the TSC, respond to any additional questions added as
184 If, after consideration by the TSC, the conclusion is that integrating external
192 #. The TSC chair will forward the link to the GitHub issue created during the
203 TSC approval or identify other approaches that can resolve the
206 #. On approval of the Zephyr TSC and governing board the submission process is
250 The TSC must approve every Pull Request that introduces a new external tooling
252 proposed addition by the TSC representatives.
[all …]
|
| D | bin_blobs.rst | 121 In case of disagreement, the TSC is the arbiter of whether a particular blob
233 reviewed and accepted by the Technical Steering Committee (TSC). This process is
244 detail, so that you are informed of the criteria used by the TSC in order to
249 TSC to assess the merit of the request. Additionally you must also create a Pull
252 #. Wait for feedback from the TSC, respond to any additional questions added as
255 If, after consideration by the TSC, the submission of the binary blob(s) is
|
| D | contributor_expectations.rst | 247 to the TSC and get a binding resolution in the TSC by adding the *TSC* label
|
| D | guidelines.rst | 1044 Steering Committee (TSC), but please avoid premature escalation to the TSC.
1061 can be merged (with escalation to the TSC if consensus is not reached at the
|
| /Zephyr-latest/boards/intel/adl/ |
| D | Kconfig.defconfig | 10 # TSC on this board is 1.9 GHz, HPET and APIC are 19.2 MHz
|
| /Zephyr-latest/boards/up-bridge-the-gap/up_squared_pro_7000/ |
| D | Kconfig.defconfig | 12 # TSC on this board is 1.9 GHz, HPET and APIC are 19.2 MHz
|
| /Zephyr-latest/boards/intel/rpl/ |
| D | Kconfig.defconfig | 11 # TSC on this board is 1.9 GHz, HPET and APIC are 19.2 MHz
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 195 for it to be discussed and ultimately even voted on in the `Zephyr TSC meeting`_.
272 .. _`Zephyr TSC meeting`: https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Wo…
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 241 Technical Steering Committee (TSC) in this area, monitoring the development process to ensure
250 Steering Committee (TSC) as appropriate, so that they can make a decision on the best course of
|
| /Zephyr-latest/dts/arm/st/g4/ |
| D | stm32g4.dtsi | 194 interrupt-names = "line0", "line1", "line2-TSC", "line3",
|
| /Zephyr-latest/modules/ |
| D | Kconfig.stm32 | 576 Enable STM32Cube Touch sensing controller (TSC) HAL module driver
|
12
