Land the Kconfig/hal_config module-selection system and templates #21
Labels
No labels
Category
App
Category
Documentation
Category
Firmware
Category
Hardware
Category
Qms
PR_Size
L
PR_Size
M
PR_Size
S
PR_Size
XL
PR_Size
XS
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Priority
Very Low Priority
Size
Epic
Size
Feature
Size
Task
Status
Blocked
Status
Draft
Status
Needs-review
Team
Board
Team
Dev
Team
Management
Type
Bug
Type
Capa
Type
Improvement
Type
New-feature
Type
Regulatory
Type
Usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
opendutchsolutions.public/hal_awr6843#21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Part of #16: tracks landing
zephyr/Kconfig,zephyr/CMakeLists.txt,hal/util/hal_config_mss.h,hal/util/hal_config_dss.h, andtemplate/hal_config_{mss,dss}_template.h— the Kconfig/hal_configmodule-selection system, split out from the individual driver-module PRs as its own reviewable piece.Use Case / Rationale
As a reviewer, I need the config-plumbing change (how modules get enabled/disabled) reviewed separately from driver logic, since it's a distinct concern even though every
hal/mss/hal/dssmodule header includeshal_config_mss.h/hal_config_dss.h.Acceptance Criteria
zephyr/Kconfigandzephyr/CMakeLists.txtare committedhal/util/hal_config_mss.handhal/util/hal_config_dss.hare committedtemplate/hal_config_mss_template.handtemplate/hal_config_dss_template.hare committedFunctional Impact
None yet — config headers only; the driver
.csourceszephyr/CMakeLists.txtreferences land in their own separate PRs.Regulatory Impact
None
QMS Impact
None
Risk Impact
No — existing risk coverage sufficient.
Related Issues / PRs
Relates to #16. Addressed by PR #19.