Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hwmv2: atmel: The SOC_FAMILY_SAM do not follow <vendor>_<family> suffix #69046

Closed
nandojve opened this issue Feb 15, 2024 · 1 comment · Fixed by #69377
Closed

hwmv2: atmel: The SOC_FAMILY_SAM do not follow <vendor>_<family> suffix #69046

nandojve opened this issue Feb 15, 2024 · 1 comment · Fixed by #69377
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug platform: Microchip SAM Microchip SAM Platform (formerly Atmel SAM) priority: low Low impact/importance bug

Comments

@nandojve
Copy link
Member

Describe the bug

When porting the Atmel SoC's was detected at #68838 that SOC_FAMILY_SAM does not have the vendor as part of the suffix. On the PR was agreed that this could be made after the collab-hwm branch be merged, see #68838 (comment)

Expected behavior
Tree wide/hal upgrade from SOC_FAMILY_SAM/SOC_FAMILY_SAM0 to SOC_FAMILY_ATMEL_SAM/SOC_FAMILY_ATMEL_SAM0 to align with new HWMv2 model.

Impact
No impact is expected.

Additional context
This issue was created to allow easy track of the change.

@nandojve nandojve added the bug The issue is a bug, or the PR is fixing a bug label Feb 15, 2024
@nandojve nandojve self-assigned this Feb 15, 2024
This was referenced Feb 15, 2024
@henrikbrixandersen henrikbrixandersen added priority: low Low impact/importance bug platform: Microchip SAM Microchip SAM Platform (formerly Atmel SAM) labels Feb 16, 2024
nandojve added a commit to nandojve/zephyr that referenced this issue Feb 23, 2024
The newer HWMv2 impose a different semantic in the family names. This
update from SOC_FAMILY_SAMx to SOC_FAMILY_ATMEL_SAMx to comply with.

Fixes zephyrproject-rtos#69046

Signed-off-by: Gerson Fernando Budke <[email protected]>
@nandojve nandojve linked a pull request Feb 23, 2024 that will close this issue
nordicjm pushed a commit that referenced this issue Feb 23, 2024
The newer HWMv2 impose a different semantic in the family names. This
update from SOC_FAMILY_SAMx to SOC_FAMILY_ATMEL_SAMx to comply with.

Fixes #69046

Signed-off-by: Gerson Fernando Budke <[email protected]>
@nandojve
Copy link
Member Author

Closed by #69377

nordicjm pushed a commit that referenced this issue Feb 23, 2024
The newer HWMv2 impose a different semantic in the family names. This
update from SOC_FAMILY_SAMx to SOC_FAMILY_ATMEL_SAMx to comply with.

Fixes #69046

Signed-off-by: Gerson Fernando Budke <[email protected]>
nordicjm pushed a commit that referenced this issue Mar 1, 2024
The newer HWMv2 impose a different semantic in the family names. This
update from SOC_FAMILY_SAMx to SOC_FAMILY_ATMEL_SAMx to comply with.

Fixes #69046

Signed-off-by: Gerson Fernando Budke <[email protected]>
carlescufi pushed a commit that referenced this issue Mar 1, 2024
The newer HWMv2 impose a different semantic in the family names. This
update from SOC_FAMILY_SAMx to SOC_FAMILY_ATMEL_SAMx to comply with.

Fixes #69046

Signed-off-by: Gerson Fernando Budke <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug platform: Microchip SAM Microchip SAM Platform (formerly Atmel SAM) priority: low Low impact/importance bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants