-
Notifications
You must be signed in to change notification settings - Fork 48
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
base: master
Are you sure you want to change the base?
Conversation
@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.
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? |
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. |
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 |
1edfb66
to
6c7fd87
Compare
dts/ti/mspm0/mspm0g3507-pinctrl.dtsi
Outdated
There was a problem hiding this comment.
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)
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
@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. |
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 |
@JFMSP good job. Hey I see most files have a missing |
Hope this gets merged soon! cc @lorforlinux |
There was a problem hiding this 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.
Self: Testing after account reset : please ignore
a11116e
to
5ca0e4b
Compare
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. |
There was a problem hiding this comment.
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) |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
@msp-ti @JFMSP , will recommend adding the information how these files were generated (/corresponding SDK) versions information in this PR itself. |
@JFMSP can you please look at the latest comments |
There was a problem hiding this 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. |
There was a problem hiding this comment.
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) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
mspm0/CMakeLists.txt
Outdated
zephyr_library_sources( | ||
source/ti/driverlib/dl_uart.c | ||
source/ti/driverlib/dl_common.c | ||
source/ti/driverlib/dl_i2c.c |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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)
There was a problem hiding this comment.
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
5ca0e4b
to
1bceb95
Compare
Added MSPM0 DriverLib and header files to be used for MSPM0 devices. Signed-off-by: Jackson Farley <[email protected]>
1bceb95
to
65b33bd
Compare
source/ti/driverlib/m0p/sysctl | ||
) | ||
|
||
file(GLOB driverlib source/ti/driverlib/*.c) |
There was a problem hiding this comment.
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.
Added MSPM0 DriverLib and header files to be used for MSPM0 devices.
Also includes mspm0 pinctrl dtsi file to add support for LP_MSPM0G3507.