[Sound-open-firmware] Initial support for i.MX8 platform
Hi Liam / Pierre,
I've sent initial patches for i.MX8 FW [1]. There are still a lot of things to be done but I will to solve them step by step.
Appreciate any review and hope to get at least the basic support accepted then build on top of that.
Next steps:
1) Add CI support to compile for imx architecture (both FW/Linux) 2) Send Linux kernel side patches.
Can you guide me on how to deal with 1)?
thanks, Daniel.
Hi Daniel,
On Mon, 2019-05-20 at 14:26 +0000, Daniel Baluta wrote:
Hi Liam / Pierre,
I've sent initial patches for i.MX8 FW [1]. There are still a lot of things to be done but I will to solve them step by step.
Great !
Btw, I've not had time to check GH yet, been travelling last week and installing a new PC (as my previous machine suddenly died 2 hours before my travel). Should be back to normal tomorrow.....
Appreciate any review and hope to get at least the basic support accepted then build on top of that.
Next steps:
- Add CI support to compile for imx architecture (both FW/Linux)
Xiuli can you help with this. I gues we need to add imx compilers to the CI containers ?
- Send Linux kernel side patches.
Can you guide me on how to deal with 1)?
thanks, Daniel.
Liam
--------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
在 5/21/2019 00:26, Liam Girdwood 写道:
Hi Daniel,
On Mon, 2019-05-20 at 14:26 +0000, Daniel Baluta wrote:
Hi Liam / Pierre,
I've sent initial patches for i.MX8 FW [1]. There are still a lot of things to be done but I will to solve them step by step.
Great !
Btw, I've not had time to check GH yet, been travelling last week and installing a new PC (as my previous machine suddenly died 2 hours before my travel). Should be back to normal tomorrow.....
Appreciate any review and hope to get at least the basic support accepted then build on top of that.
Next steps:
- Add CI support to compile for imx architecture (both FW/Linux)
Xiuli can you help with this. I gues we need to add imx compilers to the CI containers ?
Yeah, I am here. We may need some guide about how to build the FW for the i.MX8 with imx compiler after the PR is merged.
To enable it in CI we will need to build manally first, then figure out how to intergrate it in the CI.
Thanks
Xiuli
- Send Linux kernel side patches.
Can you guide me on how to deal with 1)?
thanks, Daniel.
Liam
Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
在 5/27/2019 14:43, Pan, Xiuli 写道:
在 5/21/2019 00:26, Liam Girdwood 写道:
Hi Daniel,
On Mon, 2019-05-20 at 14:26 +0000, Daniel Baluta wrote:
Hi Liam / Pierre,
I've sent initial patches for i.MX8 FW [1]. There are still a lot of things to be done but I will to solve them step by step.
Great !
Btw, I've not had time to check GH yet, been travelling last week and installing a new PC (as my previous machine suddenly died 2 hours before my travel). Should be back to normal tomorrow.....
Appreciate any review and hope to get at least the basic support accepted then build on top of that.
Next steps:
- Add CI support to compile for imx architecture (both FW/Linux)
Xiuli can you help with this. I gues we need to add imx compilers to the CI containers ?
Yeah, I am here. We may need some guide about how to build the FW for the i.MX8 with imx compiler after the PR is merged.
I think it would be better if you can provide the build guide and compiler before this merge, so we can test before the PR is merged and enable it as the PR is merged.
Thanks
Xiuli
To enable it in CI we will need to build manally first, then figure out how to intergrate it in the CI.
Thanks
Xiuli
- Send Linux kernel side patches.
Can you guide me on how to deal with 1)?
thanks, Daniel.
Liam
Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
On Mon, May 27, 2019 at 9:52 AM Pan, Xiuli xiuli.pan@linux.intel.com wrote:
在 5/27/2019 14:43, Pan, Xiuli 写道:
在 5/21/2019 00:26, Liam Girdwood 写道:
Hi Daniel,
On Mon, 2019-05-20 at 14:26 +0000, Daniel Baluta wrote:
Hi Liam / Pierre,
I've sent initial patches for i.MX8 FW [1]. There are still a lot of things to be done but I will to solve them step by step.
Great !
Btw, I've not had time to check GH yet, been travelling last week and installing a new PC (as my previous machine suddenly died 2 hours before my travel). Should be back to normal tomorrow.....
Appreciate any review and hope to get at least the basic support accepted then build on top of that.
Next steps:
- Add CI support to compile for imx architecture (both FW/Linux)
Xiuli can you help with this. I gues we need to add imx compilers to the CI containers ?
Yeah, I am here. We may need some guide about how to build the FW for the i.MX8 with imx compiler after the PR is merged.
I think it would be better if you can provide the build guide and compiler before this merge, so we can test before the PR is merged and enable it as the PR is merged.
Hi Xiuli,
crosstool-ng [1] and xtensa-overlay [2] imx patches are already accepted to github repos.
The documentation patch is here:
https://github.com/thesofproject/sof-docs/pull/125/commits/56f74662e86fc873b...
Basically, it is the same procedure as for Intel architectures. I hope it works flawlessly on your machine. Let me know if is there anything I can help with.
thanks, Daniel.
[1] https://github.com/thesofproject/xtensa-overlay/commit/2d30f07842f73d9bf0749... [2] https://github.com/thesofproject/crosstool-ng/pull/2/commits/3bc97c223a0e2e1...
在 5/27/2019 16:27, Daniel Baluta 写道:
On Mon, May 27, 2019 at 9:52 AM Pan, Xiuli xiuli.pan@linux.intel.com wrote:
在 5/27/2019 14:43, Pan, Xiuli 写道:
在 5/21/2019 00:26, Liam Girdwood 写道:
Hi Daniel,
On Mon, 2019-05-20 at 14:26 +0000, Daniel Baluta wrote:
Hi Liam / Pierre,
I've sent initial patches for i.MX8 FW [1]. There are still a lot of things to be done but I will to solve them step by step.
Great !
Btw, I've not had time to check GH yet, been travelling last week and installing a new PC (as my previous machine suddenly died 2 hours before my travel). Should be back to normal tomorrow.....
Appreciate any review and hope to get at least the basic support accepted then build on top of that.
Next steps:
- Add CI support to compile for imx architecture (both FW/Linux)
Xiuli can you help with this. I gues we need to add imx compilers to the CI containers ?
Yeah, I am here. We may need some guide about how to build the FW for the i.MX8 with imx compiler after the PR is merged.
I think it would be better if you can provide the build guide and compiler before this merge, so we can test before the PR is merged and enable it as the PR is merged.
Hi Xiuli,
crosstool-ng [1] and xtensa-overlay [2] imx patches are already accepted to github repos.
The documentation patch is here:
https://github.com/thesofproject/sof-docs/pull/125/commits/56f74662e86fc873b...
I checked the doc, there are some minor detail need update also. Please see my comment in that PR
Basically, it is the same procedure as for Intel architectures. I hope it works flawlessly on your machine. Let me know if is there anything I can help with.
All thing gose well on my local machine, I will try to update our Docker image contains the cross-compilers first and try to update Travis and sof-ci scirpts later
Thanks
Xiuli
thanks, Daniel.
[1] https://github.com/thesofproject/xtensa-overlay/commit/2d30f07842f73d9bf0749... [2] https://github.com/thesofproject/crosstool-ng/pull/2/commits/3bc97c223a0e2e1...
On Tue, May 28, 2019 at 6:39 AM Pan, Xiuli xiuli.pan@linux.intel.com wrote:
在 5/27/2019 16:27, Daniel Baluta 写道:
On Mon, May 27, 2019 at 9:52 AM Pan, Xiuli xiuli.pan@linux.intel.com wrote:
在 5/27/2019 14:43, Pan, Xiuli 写道:
在 5/21/2019 00:26, Liam Girdwood 写道:
Hi Daniel,
On Mon, 2019-05-20 at 14:26 +0000, Daniel Baluta wrote:
Hi Liam / Pierre,
I've sent initial patches for i.MX8 FW [1]. There are still a lot of things to be done but I will to solve them step by step.
Great !
Btw, I've not had time to check GH yet, been travelling last week and installing a new PC (as my previous machine suddenly died 2 hours before my travel). Should be back to normal tomorrow.....
Appreciate any review and hope to get at least the basic support accepted then build on top of that.
Next steps:
- Add CI support to compile for imx architecture (both FW/Linux)
Xiuli can you help with this. I gues we need to add imx compilers to the CI containers ?
Yeah, I am here. We may need some guide about how to build the FW for the i.MX8 with imx compiler after the PR is merged.
I think it would be better if you can provide the build guide and compiler before this merge, so we can test before the PR is merged and enable it as the PR is merged.
Hi Xiuli,
crosstool-ng [1] and xtensa-overlay [2] imx patches are already accepted to github repos.
The documentation patch is here:
https://github.com/thesofproject/sof-docs/pull/125/commits/56f74662e86fc873b...
I checked the doc, there are some minor detail need update also. Please see my comment in that PR
Basically, it is the same procedure as for Intel architectures. I hope it works flawlessly on your machine. Let me know if is there anything I can help with.
All thing gose well on my local machine, I will try to update our Docker image contains the cross-compilers first and try to update Travis and sof-ci scirpts later
Perfect, thanks for help!
On 5/20/19 9:26 AM, Daniel Baluta wrote:
Hi Liam / Pierre,
I've sent initial patches for i.MX8 FW [1]. There are still a lot of things to be done but I will to solve them step by step.
Thanks, this is great news!
Appreciate any review and hope to get at least the basic support accepted then build on top of that.
Next steps:
- Add CI support to compile for imx architecture (both FW/Linux)
Maybe a clarification here.
For each PR, we also want to have quick feedback if compilation and QEMU-based tests fail, but we can't do hardware-based tests for every PR on all platforms.
In addition, for hardware tests, we don't have a centralized CI - similar to the majority of the open-source programs. The expectation is that every contributor company takes care in depth of their own platforms, using GitHub triggers to run the tests as needed. Intel folks are not going to run any tests on i.MX hardware nor would we expect anyone to run tests for each PR on Intel hardware, though it'd be nice to know if the tests fail with the results visible.
So short answer, we can add some compilation checks for i.MX8 on both Travis CI and the Intel-hosted one, but don't expect more.
Was this your understanding?
- Send Linux kernel side patches.
For the Linux part, we try to build from a minimal kernel, see the kconfig subproject on SOF. If we can have a similar solution for i.MX it'd be great. Maintaining entire configs is too complicated, using a default + SOF-required additions is a lot simpler.
Can you guide me on how to deal with 1)?
thanks, Daniel.
[1] https://github.com/thesofproject/sof/pull/1457 _______________________________________________ Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
On Mon, May 20, 2019 at 9:16 PM Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com wrote:
On 5/20/19 9:26 AM, Daniel Baluta wrote:
Hi Liam / Pierre,
I've sent initial patches for i.MX8 FW [1]. There are still a lot of things to be done but I will to solve them step by step.
Thanks, this is great news!
Appreciate any review and hope to get at least the basic support accepted then build on top of that.
Next steps:
- Add CI support to compile for imx architecture (both FW/Linux)
Maybe a clarification here.
For each PR, we also want to have quick feedback if compilation and QEMU-based tests fail, but we can't do hardware-based tests for every PR on all platforms.
In addition, for hardware tests, we don't have a centralized CI - similar to the majority of the open-source programs. The expectation is that every contributor company takes care in depth of their own platforms, using GitHub triggers to run the tests as needed. Intel folks are not going to run any tests on i.MX hardware nor would we expect anyone to run tests for each PR on Intel hardware, though it'd be nice to know if the tests fail with the results visible.
So short answer, we can add some compilation checks for i.MX8 on both Travis CI and the Intel-hosted one, but don't expect more.
Was this your understanding?
This is my understanding too. We need to add compilation check for i.MX the rest we will try to handle it internally.
- Send Linux kernel side patches.
For the Linux part, we try to build from a minimal kernel, see the kconfig subproject on SOF. If we can have a similar solution for i.MX it'd be great. Maintaining entire configs is too complicated, using a default + SOF-required additions is a lot simpler.
default + SOF required additions is good ans simple. The one problem is that arm64 use one single config for all supported boards, hence the compilation takes sometimes more than we want.
For me this is not a problem because I don't build from fresh code very often but for CI indeed I need to find a way to have a smaller config.
thanks, Daniel.
For each PR, we also want to have quick feedback if compilation and QEMU-based tests fail, but we can't do hardware-based tests for every PR on all platforms.
In addition, for hardware tests, we don't have a centralized CI - similar to the majority of the open-source programs. The expectation is that every contributor company takes care in depth of their own platforms, using GitHub triggers to run the tests as needed. Intel folks are not going to run any tests on i.MX hardware nor would we expect anyone to run tests for each PR on Intel hardware, though it'd be nice to know if the tests fail with the results visible.
So short answer, we can add some compilation checks for i.MX8 on both Travis CI and the Intel-hosted one, but don't expect more.
Was this your understanding?
This is my understanding too. We need to add compilation check for i.MX the rest we will try to handle it internally.
ok, we'll work with Xiuli to make it happen.
- Send Linux kernel side patches.
For the Linux part, we try to build from a minimal kernel, see the kconfig subproject on SOF. If we can have a similar solution for i.MX it'd be great. Maintaining entire configs is too complicated, using a default + SOF-required additions is a lot simpler.
default + SOF required additions is good ans simple. The one problem is that arm64 use one single config for all supported boards, hence the compilation takes sometimes more than we want.
For me this is not a problem because I don't build from fresh code very often but for CI indeed I need to find a way to have a smaller config.
Yes, I spent a bit of time to remove the stuff we didn't need for SOF in the x64_64_defconfig while still keeping the minimal support to actually test (network, i915, storage, etc). It's much faster to compile and load.
participants (5)
-
Daniel Baluta -
Daniel Baluta -
Liam Girdwood -
Pan, Xiuli -
Pierre-Louis Bossart