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

NXP S32 SoC improvements to accommodate new devices #64872

Merged
merged 3 commits into from
Nov 15, 2023
Merged

NXP S32 SoC improvements to accommodate new devices #64872

merged 3 commits into from
Nov 15, 2023

Conversation

manuargue
Copy link
Member

  1. Renaming directory for S32K1 support:
    The s32k directory, which currently supports the S32K3 series, is renamed to align with the respective series names and to accommodate S32K1 devices. This adjustment is necessary due to significant differences in core architecture, MPU, peripherals, and other key aspects between the two series.

  2. Streamlining Kconfig options:
    The S32K3 Kconfig options currently using the 'M7' suffix are simplified by removing this suffix, as all devices in the S32K3 series feature an Arm Cortex-M7 core. Also in order to remove redundancy, the part number configuration options are consolidated by keeping CONFIG_SOC_PART_NUMBER to store the part number as a string and CONFIG_SOC_PART_NUMBER_<part> to be selected by the boards.

@zephyrbot
Copy link
Collaborator

zephyrbot commented Nov 6, 2023

The following west manifest projects have been modified in this Pull Request:

Name Old Revision New Revision Diff

Note: This message is automatically posted and updated by the Manifest GitHub Action.

bperseghetti
bperseghetti previously approved these changes Nov 8, 2023
@manuargue
Copy link
Member Author

manuargue commented Nov 9, 2023

build failures should be fixed with #64995

@manuargue manuargue requested review from Dat-NguyenDuy and removed request for yvanderv November 10, 2023 04:19
@manuargue
Copy link
Member Author

rebased & fixed conflicts

bperseghetti
bperseghetti previously approved these changes Nov 12, 2023
decsny
decsny previously approved these changes Nov 13, 2023
@Dat-NguyenDuy
Copy link
Contributor

@manuargue pls rebase

@manuargue manuargue dismissed stale reviews from decsny and bperseghetti via 0835b2e November 14, 2023 13:46
@zephyrbot zephyrbot added area: CAN and removed DNM This PR should not be merged (Do Not Merge) labels Nov 14, 2023
bperseghetti
bperseghetti previously approved these changes Nov 14, 2023
Copy link
Member

@henrikbrixandersen henrikbrixandersen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 for CAN changes.

@mmahadevan108
Copy link
Collaborator

Kindly rebase.

To accommodate support for S32K1 devices, it is necessary to rename
the existing `s32k` directory, which currently houses support for
the S32K3 series, to align with the respective series names. This
adjustment is necessary given the distinct differences in core
architecture, MPU, peripherals, and other key aspects between
the two series.

Signed-off-by: Manuel Argüelles <[email protected]>
The existing S32K3 Kconfig options employ the `M7` suffix, which is
redundant given that all cores in this series utilize an Arm Cortex-M7
core. Therefore, we should remove it.

Signed-off-by: Manuel Argüelles <[email protected]>
Currently, the NXP S32 SoCs have three redundant Kconfig hidden
options to define the part number. To streamline this, we will
retain `CONFIG_SOC_PART_NUMBER` to store the part number as a
string and `CONFIG_SOC_PART_NUMBER_<part>` that can be selected
by the boards.

Furthermore, for drivers requiring conditional code compilation
based on the target SoC, they should utilize the series or SoC
config option as applicable, instead of the part number config.

Signed-off-by: Manuel Argüelles <[email protected]>
@mmahadevan108 mmahadevan108 merged commit 1a05cfc into zephyrproject-rtos:main Nov 15, 2023
22 checks passed
@manuargue manuargue deleted the manuargue-s32-soc branch November 15, 2023 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants