-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
soc: silabs: Facilitate non-Gecko SoC support #71938
soc: silabs: Facilitate non-Gecko SoC support #71938
Conversation
a411959
to
9bc9da8
Compare
Hello @rettichschnidi, I understand your point however, I have some concern with "gecko" naming. Currently, "gecko" include series 0, 1 and 2. However, future series 3 won't use "gecko" branding. In addition, series 0 and 1 are going to be deprecated by upstream. So, my initial goal was to get rid of "gecko" name because it is going to become confusing. One idea would be use Otherwise, since For What is your thoughts? |
Out of curiosity: What does deprecated buy upstream mean? Is there an issue for this?
👍
👍
Will give it a try, and update this PR then. |
Maybe deprecated is not the right word. If I understand right, series 0/1 will not new features. Thus, code for series 0/1 may diverge from the code for series 2+. However, Zephyr mostly imports low level driver that doesn't change so much. So, the impact for Zephyr is still a bit unclear. Let's just be prepared to support series 0/1 and series 2+ separately. |
This allows to remove SOC_VENDOR_SILABS in a later commit. Signed-off-by: Reto Schneider <[email protected]>
This allows to remove SOC_VENDOR_SILABS in a later commit. Signed-off-by: Reto Schneider <[email protected]>
9bc9da8
to
4177cf2
Compare
4177cf2
to
81623ec
Compare
Dismissed my assignment. I'm absolutely not familiar with silabs. |
Until now, the support for Silicon Labs SoCs is limited to the Gecko families. This commit allows upstreaming support for non-Gecko based SoCs produced by Silicon Labs (i.e. SiM3U1xx). Signed-off-by: Reto Schneider <[email protected]>
81623ec
to
64743ef
Compare
@jerome-pouiller I updated the PR. What do you think? |
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.
Fine for me.
This is the result of rebasing #64209 on the most recent main.
Putting those commits in a separate PR because I think it is the right thing to do, regardless of the SiM3U support.