-
Notifications
You must be signed in to change notification settings - Fork 349
Move the SOF app from zephyr to where it belongs #6004
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
Conversation
lgirdwood
left a comment
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.
LGTM - thank you @nashif
@marc-hb @keqiaozhang @wszypelt does anything need to be done for CI to use this update ?
@aborisovich good for you and Windows ?
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.
Quick review, two minor python issues.
Going to test Windows build in a minute,
As I understand the idea we are going to use overlays as common for everyone?
I am not sure this is right.
Yes we can do this for debug_overlay.conf but it does not make sense to use IPC4 overlay with anothing older than TGL - it probably won't even build and nobody did it before.
I would go back to old approach with platform names, something like this:

Then we can see which overlays are what for. Also please note that "platform" is better term here because we have some platforms in SOF that are build without Zephyr.
One more thing - I would change a name from "app" to "cSOF" maybe?
Like "Converged SOF" so it matches our official name :-)
704d6cf to
06ccfac
Compare
Sure, this can be put in a strucutre with platform names.
boards/ is a preset folder name in the zephyr build system, the right configuration file is pulled automatically based on what you are building, so, no need for overlay magic, very useful if you are not building using the python script.
app is just a placeholder, you guys decide what name to use... |
|
Thanks Anas for helping with this, much appreciated.
Sorry I don't know why the Zephyr build was successful in https://github.com/thesofproject/sof/runs/7322499212 but failed in https://sof-ci.01.org/sofpr/PR6004/build891/build (error below). The changes to @keqiaozhang, @XiaoyunWu6666 ? Jenkins does a bit more with |
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.
Sorry for delays in testing Windows build (i need to configure my environment).
I'll let you know as soon as its verified.
Meanwhile found one more thing to python (enable MTL build).
Rest of changes looks pretty good to me.
scripts/xtensa-build-zephyr.py
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.
You added configuration for MTL board, please add missing python dictionary so we can build it too:
{
"name": "mtl",
"PLAT_CONFIG": "intel_adsp_ace15_mtpm",
"XTENSA_CORE": "ace10_LX7HiFi4_RI_2020_5",
"XTENSA_TOOLS_VERSION": f"RI-2020.5{xtensa_tools_version_postfix}",
"RIMAGE_KEY": pathlib.Path("modules", "audio", "sof", "keys", "otc_private_key_3k.pem
},
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 will probably remove it and leave it to you to add this alongside other mtl related changes.
|
SOFCI TEST |
@marc-hb , this build failure is not caused by this PR. I checked the Jenkins log and found that our sofbld10 failed to clone zephyrporject, because there's |
Confirmed Windows build working (built TGL successfully). |
It may be my fault as I'm messing around with processes in PR6005, sorry. |
Thanks @aborisovich , very good catch I didn't realize 6005 could break CI even before getting merged but because of big west differences then yes of course it can! Ideally it shouldn't but in practice it can because our workers clean but don't clone everything from scratch. I prefixed the Github PR title with |
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.
https://sof-ci.01.org/sofpr/PR6004/build896/devicetest/ is all green expect one unrelated and unfortunately common suspend/resume failure.
The Python, CMake and C changes LGTM, thanks! The checkpatch warnings seem harmless, someone should check.
I don't know about the overlays and .conf files but I blindly trust @nashif with that :-) But @aborisovich must approve.
|
@aborisovich good for you now ? |
aborisovich
left a comment
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.
Never trust anyone blindly, we are all developers ;-)
I just wanted to remove boards/intel_adsp_ace15_mtpm.conf from this PR just for consistency (or add it to python so it is buildable). But maybe it does not matter that much.
Everything else looks perfect, windows build works too, approving.
removed |
Zephyr includes are now under a zephyr namespace, so use this. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Make the main SOF app part of SOF, where it belongs. No need for any overlays (which just duplicated the sample .conf anyways) and one place to build everything. This now does not depend on zephyr samples, which have a different purpose completely. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This allows building SOF from zephyr for CI and testing purposes. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Remove overlays as they are the same board configurations available in app/. Keep common overlays and change script to reflect those changes. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
|
@wszypelt can you check CI, this should not break runtime tests |
|
@lgirdwood |
Thanks for checking @wszypelt - I will rerun as the CI error log is still not loading for me. |
|
SOFCI TEST |
|
@wszypelt I've rerun the CI and still getting empty logs for the test failures. Are we good to merge ? |
|
@lgirdwood the magic comment "SOFCI TEST" is scanned by SOFCI TEST only, QB does not care. I looked at the internal 9877300 logs for https://sof-ci.01.org/sof-pr-viewer/#/build/PR6004/build9877263 and this can merged. I confirm that the build in QB was successful, only the deployment to 2 devices (TGL and WHL) failed: I doubt this PR even affects QB at all. (https://sof-ci.01.org/sofpr/PR6004/build906/devicetest/ is all green except for one unfortunately common suspend/resume failure.) |
This moves (not deleted in zephyr yet) the SOF app into SOF, where it belongs.
No need for duplicated overlays and one place to build everything.
You now use scripts or west directly to build this and able to make all changes needed in the configuration files without having go via zpehyr or go through the complexity of a second layer of configurations (overlays)