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

mspm0: Add MSPM0 support #51

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

msp-ti
Copy link

@msp-ti msp-ti commented Feb 3, 2024

Added MSPM0 DriverLib and header files to be used for MSPM0 devices.
Also includes mspm0 pinctrl dtsi file to add support for LP_MSPM0G3507.

@vaishnavachath
Copy link
Collaborator

@msp-ti , Thank you for your PR, can you confirm if these sources are auto generated from a TI SDK? if yes, is there a way for you to upgrade to newer versions in a automated/semi-automated manner as present for simplelink devices.

  • What would be the strategy for fixes from going to TI SDK in

Also are you adding support for MSPM0L series support as well, seeing a lot of files in the PR for those devices as well, are they intentionally added?

@msp-ti
Copy link
Author

msp-ti commented Feb 27, 2024

Hi @vaishnavachath, we could do an update of the SDK components quarterly, we may use a submodule based on the SDK that is uploaded to github.

@msp-ti
Copy link
Author

msp-ti commented Feb 28, 2024

Upon consideration and management, we may stick to updating these in a script. In a future revision, we can add this process of updating to the readme such that a user can patch the hal with a specific SDK or changes should that become necessary

Copy link
Member

Choose a reason for hiding this comment

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

that's suspiciously specific, should/could be more generic? (the part number I mean)

Copy link
Author

Choose a reason for hiding this comment

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

So you would recommend not specifying the MSPM0G3507 part number in the commit message?

Copy link
Member

Choose a reason for hiding this comment

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

No I'm referring to the file name, maybe it should be matching to more parts in the family, like mspm0g3xxx or something

@vaishnavachath
Copy link
Collaborator

Hi @vaishnavachath, we could do an update of the SDK components quarterly, we may use a submodule based on the SDK that is uploaded to github.

@msp-ti Sounds good, it would be good to have a clear idea of this going forward as it will be difficult to fix this later. I don't have any other blocking comments.

@JFMSP
Copy link

JFMSP commented Apr 16, 2024

I've generalized the way we're creating pinctrl, based on soc family and splitting additional pinctrl into components. The final SOC will have a pinctrl that should only be made up of previous pinctrls

@fabiobaltieri
Copy link
Member

@JFMSP good job. Hey I see most files have a missing \n of EOF warning (GitHub marks them, the red thing at the end of the file). Could you check your editor and set it up to not do that and terminate the files correctly? Not having those causes extra noise in the diff when the file is updated.

@jadonk
Copy link

jadonk commented Jul 11, 2024

Hope this gets merged soon! cc @lorforlinux

Copy link
Collaborator

@vaishnavachath vaishnavachath left a comment

Choose a reason for hiding this comment

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

Pending comments needs to be addressed.

vaishnavachath
vaishnavachath previously approved these changes Sep 23, 2024
@vaishnavachath vaishnavachath self-requested a review September 23, 2024 13:10
@vaishnavachath vaishnavachath dismissed their stale review September 23, 2024 13:10

Self: Testing after account reset : please ignore

Drivers and other improvements that are TI-specific will be updated periodically.
These may change with new SDK releases as additional changes occur.

Please notify a TI Zephyr representative if additional changes are needed.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Not sure what the intent of this README is , if you want to add this , will recommend adding sections of the devices supported and the directory strtucture .etc for a top level overview.

This project is already listed as an entry here : https://github.com/zephyrproject-rtos/zephyr/blob/main/MAINTAINERS.yml#L4866

@@ -0,0 +1,27 @@
add_subdirectory(source/ti/devices)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Need a README under mspm0 directory detailing how these files were generated and how someone can update to a newer SDK , also please add details on what upstream SDK version these sources were generated, see
https://github.com/zephyrproject-rtos/hal_ti/blob/master/simplelink/README

Copy link
Member

Choose a reason for hiding this comment

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

+1

@vaishnavachath
Copy link
Collaborator

Upon consideration and management, we may stick to updating these in a script. In a future revision, we can add this process of updating to the readme such that a user can patch the hal with a specific SDK or changes should that become necessary

@msp-ti @JFMSP , will recommend adding the information how these files were generated (/corresponding SDK) versions information in this PR itself.

@vaishnavachath
Copy link
Collaborator

@msp-ti @JFMSP can you please let us know what will be the process for carrying fixes to SDK, will you be picking the fixes from this repo to your SDK releases? See an example : #47

@Quentis
Copy link

Quentis commented Nov 9, 2024

@msp-ti @JFMSP When do you plan to add Zephyr support for MSPM0? Is it going to be released with Zephyr 4.0?

@vaishnavachath
Copy link
Collaborator

@JFMSP can you please look at the latest comments

Copy link
Member

@parthitce parthitce left a comment

Choose a reason for hiding this comment

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

Thanks for your efforts. IMO it makes sense to split the whole changes in the 2 commits. One from the TI SDK/HAL and another specific to Zephyr (module.yml, CMake and so).

@@ -0,0 +1,246 @@
This file provides licensing information on the code provided in this repository.
Copy link
Member

Choose a reason for hiding this comment

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

Same license applies for simplelink as well?

@@ -0,0 +1,27 @@
add_subdirectory(source/ti/devices)
Copy link
Member

Choose a reason for hiding this comment

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

+1

zephyr_library_sources(
source/ti/driverlib/dl_uart.c
source/ti/driverlib/dl_common.c
source/ti/driverlib/dl_i2c.c
Copy link
Member

Choose a reason for hiding this comment

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

We don't have i2c in the zephyr PR. Should we rather limit this CMake specific to the ones already part of zephyr PR?

Copy link

Choose a reason for hiding this comment

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

I think it'd be better to generalize to exposing the whole SDK with a glob (done below)

Copy link
Member

Choose a reason for hiding this comment

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

NACK! See below for comment

Added MSPM0 DriverLib and header files to be used for MSPM0 devices.

Signed-off-by: Jackson Farley <[email protected]>
source/ti/driverlib/m0p/sysctl
)

file(GLOB driverlib source/ti/driverlib/*.c)
Copy link
Member

Choose a reason for hiding this comment

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

NACK! This must be conditional inclusion. Check other HAL for reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants