zephyr: add soc overlay for i.MX8QM and i.MX8QXP #24
Conversation
|
Since they are using the same overlay, I would assume they are both using the same toolchain. If that is the case, you can do a SoC series and use |
LaurentiuM1234
force-pushed
the
imx8qm_qxp
branch
from
0829036
to
73d2726
Compare
Since the i.MX8 SoC will be split into 2 different SoCs: mimx8qm6 and mimx8qx6, the nxp_imx8 name can no longer be used. This is because the new SoCs will have different CONFIG_SOC values such that CONFIG_SOC != nxp_imx8. Despite this, we can take advantage of the fact that the 2 SoCs use the same toolchain. As such, rename nxp_imx8 to nxp_imx_adsp. This works because Zephyr looks for an overlay with the same name as the toolchain if one with the same name as the SoC doesn't exist. This won't break the current state of things because the i.MX8 SoC will also fallback to the nxp_imx_adsp overlay. Signed-off-by: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
You're right, they are using the same toolchain. Unfortunately, I can't get rid of |
|
@mmahadevan108 I think this should be ready for merge |
Since the i.MX8 Zephyr SoC will be split into two SoCs: mimx8qm6 and mimx8qx6, the xtensa HAL needs to provide two different overlays with the same name as the SoCs. As such, this commit takes the files from the nxp_imx8 SoC and duplicates them, resulting in the creation of mimx8qm6 and mimx8qx6.
As a sidenote: we can/should remove the nxp_imx8 entry once the Zephyr changes have been merged.
IMPORTANT: there's no difference between the files found in
nxp_imx8,mimx8qm6, andmimx8qx6.