Difference between revisions of "STM32MP15 device tree"

[quality revision] [pending revision]
m (Purpose and scope: Add review comment: missing info about OP-TEE)
m
 

1 Purpose and scope[edit]

This article shows the structure of the device tree files as it is implemented in STM32MP15 for the following software components: Linux® kernel, U-Boot and , TF-A and OP-TEE.

The purpose of this article is not to explain the device tree concept and the device tree configuration supported by STM32MP15. A good knowledge of the concept is a prerequisite before reading this article. The articles regarding the configuration can be read afterwards.

2 Device tree structure for Linux, U-Boot and , TF-A and OP-TEE[edit]

2.1 Introduction STMicroelectronics software delivery[edit]

The device tree files are used during boot time by the FSBL (TF-A), the secure OS (OP-TEE), the SSBL (U-Boot) , and eventually by the Linux kernel.

These files are stored in different github repositories (one for each first level bullet below), but source code reuse is maximized from one repository to another:

  • The initial device tree files supporting STM32MP15 are created in the Linux kernel.
  • In U-Boot, Linux files are copied and overloaded with U-Boot properties (including DDR configuration).
    • The source code path is arch/arm/dts/stm32mp15* .
    • The U-Boot add-ons file, "<dts-file-name>-u-boot.dtsi", is automatically included at the end of "<dts-file-name>.dts" during device tree compilation (this is a generic U-Boot Makefile behavior).
  • In TF-A, Linux files are partly copied (for device tree blob size optimization) and , completed with the security configuration (firewalling) , and the DDR configuration is also added (same files as U-Boot). TF-A device tree bindings reading is needed to understand which parts of the Linux device tree must be kept or can be deleted during the partial copy.
  • In OP-TEE, TF-A files are reused, except the DDR configuration ones.

The figure below shows the device tree creation flow for Linux, U-Boot and , TF-A and OP-TEE:

Device tree for Linux U-Boot TF-A.pngDevice tree for Linux U-Boot TF-A OP-TEE.png

Color legend:

  •  Linux  in dark blue
  •  U-Boot  add-ons in green
  •  TF-A   DDR configuration  for TF-A and U-Boot in pink
  •  STM32CubeMX generated parts  in light blue (not used above but visible in STM32CubeMX section down in this article)
  • The hashed areas on Linux device tree files represent the fact that these files are modified, so partly copied and updated

The above color codes are used for all the figures included in this article.

2.2 Upstreamed device tree[edit]

2.2.1 Overview[edit]

As explained in the STM32 MPU Embedded Software Open Source Software (OSS) philosophy, STMicroelectronics maximizes the usage of open source software and the upstreaming to the communities.

So, the device tree files supporting the evaluation board and the Discovery discovery kit are upstreamed to their official respective repositories. But waiting for the upstream process completion, STMicroelectronics latest contributions are available in advance on github in Linux , U-Boot and , TF-A and OP-TEE repositories.

Info.png The figures shown below are reflecting the current implementation on github and they may be somehow in advance compare to the upstreamed version for all parts that are still under review.
Info.png For the sake of simplicity, the figures below only show the dtsi & dts files structure, without showing the h files that are also included.
Info.png The dtb files, resulting from the compilation with the dtc compiler, may be named differently when the compilation is launched with the Distribution Package.

2.2.2 Linux[edit]

Device tree Linux upstreamed.png
Device tree legend.png

2.2.3 U-Boot[edit]

Device tree U-Boot upstreamed.png
Device tree legend.png

Info.png '<board>-u-boot.dtsi' file inclusion at the end of '<board>.dts' file is not explicit (#include ...) but realized via an U-Boot generic mechanism (see README )

2.2.4 TF-A[edit]

Device tree TF-A upstreamed.png
Device tree legend.png

Note: The hashed areas on Linux device tree files represent the fact that these files are partly copied modified in TF-A.

2.2.5 OP-TEE[edit]

Device tree OP-TEE upstreamed.png
Device tree legend.png

Note: The hashed areas on Linux device tree files represent the fact that these files are modified in OP-TEE.


2.3 STM32CubeMX generated device tree[edit]

2.3.1 Overview[edit]

STM32CubeMX can be used to generate the device tree files for a given project. The tool generates the files  highlighted in light blue  in the following diagrams, including the upstreamed files shown in the previous chapter.

The device tree files generated by STM32CubeMX can be built with the Developer Package or Distribution Package:

2.3.2 Linux[edit]

Device tree Linux STM32CubeMX.png

2.3.3 U-Boot[edit]

Device tree U-Boot STM32CubeMX.png

2.3.4 TF-A[edit]

Device tree TF-A STM32CubeMX.png

2.3.5 OP-TEE[edit]

STM32CubeMX does not generate any device tree source files dedicated to OP-TEE, but these can be derived from the device tree source files generated for TF-A. In OP-TEE github release , OP-TEE files are the very TF-A source files with the DDR dtsi files removed since fully unused. However, one can copy TF-A device tree source files stm32mp15* to OP-TEE dts/   source directory and build OP-TEE with.


== Purpose and scope ==
This article shows the structure of the device tree files as it is implemented in STM32MP15 for the following software components: [[STM32MP15 Linux kernel overview|Linux<sup>&reg;</sup> kernel]], [[U-Boot overview|U-Boot]] and , [[TF-A overview|TF-A]].

{{ReviewsComments| Etienne Carriere
This article should mention OP-TEE since there is a specifc DT also in OP-TEE Core }}
 and [[OP-TEE overview|OP-TEE]].
The purpose of this article is not to explain the [[Device tree|device tree]] concept and the [[:Category:Device tree configuration|device tree configuration]] supported by STM32MP15. A good knowledge of the concept is a prerequisite before reading this article. The articles regarding the configuration can be read afterwards.

== Device tree structure for Linux, U-Boot and , TF-A ==

=== Introduction and OP-TEE ==
=== STMicroelectronics software delivery ===
The device tree files are used during [[Boot chainschain overview|boot time]] by the FSBL (TF-A), the SSBL (U-Boot),secure OS (OP-TEE), the SSBL (U-Boot) and eventually by the Linux kernel. <br />

These files are stored in different github repositories (one for each first level bullet below), but source code reuse is maximized from one repository to another:
* The initial device tree files supporting STM32MP15 are created in the '''Linux''' kernel.
** The source code path is {{CodeSource | Linux kernel | arch/arm/boot/dts/ | arch/arm/boot/dts/stm32mp15*}}.
* In '''U-Boot''', Linux files are copied and overloaded with U-Boot properties (including DDR configuration).
** The source code path is {{CodeSource | U-Boot | arch/arm/dts/ | arch/arm/dts/stm32mp15*}}.
** The U-Boot add-ons file, "<dts-file-name>-u-boot.dtsi", is automatically included at the end of "<dts-file-name>.dts" during device tree compilation (this is a generic U-Boot Makefile behavior).
* In '''TF-A''', Linux files are partly copied (for device tree blob size optimization) and , completed with the security configuration (firewalling), and the DDR configuration is also added (same files as U-Boot). {{CodeSource | TF-A | docs/devicetree/bindings/ | TF-A device tree bindings}} reading is needed to understand which parts of the Linux device tree must be kept or can be deleted during the partial copy.** The source code path is {{CodeSource | TF-A | fdts/ | fdts/stm32mp15*}}.<br />


The * In '''OP-TEE''', TF-A files are reused, except the DDR configuration ones.
** The source code path is {{CodeSource | OP-TEE_OS | core/arch/arm/dts/ | core/arch/arm/dts/stm32mp15*}}.
The figure below shows the device tree creation flow for Linux, U-Boot and TF-A, TF-A and OP-TEE:
[[File:Device_tree_for_Linux_U-Boot_TF-A_OP-TEE.png|center|link=]]
Color legend: 
* <span style="color:#FFFFFF; background:{{STDarkBlue}};">&nbsp;Linux&nbsp;</span> in dark blue
* <span style="color:#FFFFFF; background:{{STLightGreen}};">&nbsp;U-Boot&nbsp;</span> add-ons in green
* <span style="color:#FFFFFF; background:{{STPink}};">&nbsp;TF-ADDR configuration&nbsp;</span> for TF-A and U-Boot in pink
* <span style="color:#FFFFFF; background:{{STLightBlue}};">&nbsp;STM32CubeMX generated parts&nbsp;</span> in light blue The (not used above but visible in [[#STM32CubeMX_generated_device_tree|STM32CubeMX]] section down in this article)
* The '''hashed''' areas on Linux device tree files represent the fact that these files are modified, so partly copied and updated
The above color codes are used for all the figures included in this article.

=== Upstreamed device tree ===
==== Overview ====
As explained in the STM32 MPU Embedded Software [[STM32MPU_Embedded_Software_architecture_overview#Open_Source_Software_(OSS)_philosophy| Open Source Software (OSS) philosophy]], STMicroelectronics maximizes the usage of open source software and the upstreaming to the communities.

So, the device tree files supporting the [[STM32MP157x-EV1 - hardware description|evaluation board]] and the [[STM32MP157x-DKx - hardware description|Discoverydiscovery kit]] are '''upstreamed''' to their official respective repositories. But waiting for the upstream process completion, STMicroelectronics latest contributions are available in advance on github in {{CodeSource | Linux kernel | arch/arm/boot/dts/ | Linux}}, {{CodeSource | U-Boot | arch/arm/dts/ | U-Boot}} and , {{CodeSource | TF-A | fdts/ | TF-A}} and {{CodeSource | OP-TEE_OS | core/arch/arm/dts/ | OP-TEE}} repositories.

{{Info|The figures shown below are reflecting the '''current implementation on github''' and they may be somehow in advance compare to the '''upstreamed''' version for all parts that are still under review.}}
{{Info|For the sake of simplicity, the figures below only show the '''dtsi''' & '''dts''' '''files''' structure, without showing the '''h files''' that are also included.}}
{{Info|The '''dtb files''', resulting from the compilation with the dtc compiler, may be named differently when the compilation is launched with the [[Which STM32MPU Embedded Software Package better suits your needs|Distribution Package]].}}

==== Linux ====
[[File:Device tree Linux upstreamed.png|center|link=]]
[[File:Device tree legend.png|center|link=]]<br />


==== U-Boot ====
[[File:Device tree U-Boot upstreamed.png|center|link=]]
[[File:Device tree legend.png|center|link=]]<br />

{{Info|'<board>-u-boot.dtsi' file inclusion at the end of '<board>.dts' file is not explicit (#include ...) but realized via an U-Boot generic mechanism (see {{CodeSource | U-Boot | tools/binman/README | README}})}}

==== TF-A ====
[[File:Device tree TF-A upstreamed.png|center|link=]]
[[File:Device tree legend.png|center|link=]]<br />

Note: The hashed areas on Linux device tree files represent the fact that these files are partly copied modified in TF-A.<br />




==== OP-TEE ====
[[File:Device tree OP-TEE upstreamed.png|center|link=]]
[[File:Device tree legend.png|center|link=]]<br />

Note: The hashed areas on Linux device tree files represent the fact that these files are modified in OP-TEE.<br />


{{ReviewsComments|-- [[User:Etienne Carriere|Etienne Carriere]] ([[User talk:Etienne Carriere|talk]]) 17:33, 26 June 2020 (CEST)<br />The figure must be updated. OP-TEE current (v3.9.0) mainline DTS files are the Linux v5.6 DTS files with input configuration information removed and a bit of OP-TEE specific configuration changes. Note that the mainline evolves and OP-TEE mainline will soon sync with latest Linux DTS files.

I propose that you keep a simplified views (with few boards) and an explicit sentence. Modified files are SoC base 'stm32mp151.dtsi'
and the boards, for input config info removal. I propose you show only few board as example, i.e. only:
stm32mp151.dtsi   (Modified)
stm32mp157c-dk2.dts (Modified)
stm32mp157c-ev1.dts (Modified)
}}
=== STM32CubeMX generated device tree ===
==== Overview ====
[[STM32CubeMX]] can be used to '''generate''' the device tree files for a given project. The tool generates the files <span style="color:#FFFFFF; background:{{STLightBlue}};">&nbsp;highlighted in light blue&nbsp;</span> in the following diagrams, including the upstreamed files shown in the previous chapter.<br />
<br />

The device tree files generated by STM32CubeMX can be '''built''' with the [[Which STM32MPU Embedded Software Package better suits your needs#Developer Package|Developer Package]] or [[Which STM32MPU Embedded Software Package better suits your needs#Distribution_Package|Distribution Package]]:
* Use the '''Developer Package''' to store the STM32CubeMX-generated files in the folder of your choice. Then, manually copy or link them into Linux, U-Boot and TF-A device tree folders (see [[STM32MP15_device_tree#Introduction|introduction]]). Do not forget to add your device tree file name in '''../Makefile.sdk''' (for [[STM32MP1 Developer Package - TF-A|TF-A SDK]] and [[STM32MP1 Developer Package - U-Boot|U-Boot SDK]]) and in '''arch/arm/boot/dts/Makefile''' (for [[STM32MP1 Developer Package - Linux kernel|Linux kernel SDK]]), before compiling them as expalined in [[How to cross-compile with the Developer Package]].
* Use the '''Distribution Package''' to store the STM32CubeMX-generated files in '''meta-st/meta-st-stm32mp-addons/mx''', as explained in the [[How to create your own machine]] article. This article also describes how to build the complete image. Examples of Linux (device tree), U-Boot and TF-A individual compiling can be found in the [[How to cross-compile with the Distribution Package]] article.

==== Linux ====
[[File:Device tree Linux STM32CubeMX.png|center|link=]]<br />


==== U-Boot ====
[[File:Device tree U-Boot STM32CubeMX.png|center|link=]]<br />


==== TF-A ====
[[File:Device tree TF-A STM32CubeMX.png|center|link=]]<br />

==== OP-TEE ====
STM32CubeMX does not generate any device tree source files dedicated to OP-TEE, but these can be derived from the device tree source files generated for TF-A. In {{CodeSource | OP-TEE_OS | / | OP-TEE github release}}, OP-TEE files are the very TF-A source files with the DDR dtsi files removed since fully unused. However, one can copy TF-A device tree source files stm32mp15* to {{CodeSource | OP-TEE_OS | core/arch/arm/dts/ | OP-TEE dts/}}&nbsp; source directory and build OP-TEE with.
<noinclude>

[[Category:STM32MP15 platform configuration|6]]
{{PublicationRequestId | 14960 | 2019-01-31 | Previous PR: 10415 (AnneJ)}}</noinclude>
(38 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
== Purpose and scope ==
 
== Purpose and scope ==
This article shows the structure of the device tree files as it is implemented in STM32MP15 for the following software components: [[STM32MP15 Linux kernel overview|Linux<sup>&reg;</sup> kernel]], [[U-Boot overview|U-Boot]] and [[TF-A overview|TF-A]].
+
This article shows the structure of the device tree files as it is implemented in STM32MP15 for the following software components: [[STM32MP15 Linux kernel overview|Linux<sup>&reg;</sup> kernel]], [[U-Boot overview|U-Boot]], [[TF-A overview|TF-A]] and [[OP-TEE overview|OP-TEE]].
 
 
{{ReviewsComments| Etienne Carriere
 
This article should mention OP-TEE since there is a specifc DT also in OP-TEE Core }}
 
   
 
The purpose of this article is not to explain the [[Device tree|device tree]] concept and the [[:Category:Device tree configuration|device tree configuration]] supported by STM32MP15. A good knowledge of the concept is a prerequisite before reading this article. The articles regarding the configuration can be read afterwards.
 
The purpose of this article is not to explain the [[Device tree|device tree]] concept and the [[:Category:Device tree configuration|device tree configuration]] supported by STM32MP15. A good knowledge of the concept is a prerequisite before reading this article. The articles regarding the configuration can be read afterwards.
   
== Device tree structure for Linux, U-Boot and TF-A ==
+
== Device tree structure for Linux, U-Boot, TF-A and OP-TEE ==
  +
=== STMicroelectronics software delivery ===
  +
The device tree files are used during [[Boot chain overview|boot time]] by the FSBL (TF-A), the secure OS (OP-TEE), the SSBL (U-Boot) and eventually by the Linux kernel. <br />
   
 
+
These files are stored in different github repositories (one for each first level bullet below), but source code reuse is maximized from one repository to another:
=== Introduction ===
 
The device tree files are used during [[Boot chains overview|boot time]] by the FSBL (TF-A), the SSBL (U-Boot), and eventually by the Linux kernel. <br />
 
These files are stored in different repositories, but source code reuse is maximized from one repository to another:
 
 
* The initial device tree files supporting STM32MP15 are created in the '''Linux''' kernel.
 
* The initial device tree files supporting STM32MP15 are created in the '''Linux''' kernel.
 
** The source code path is {{CodeSource | Linux kernel | arch/arm/boot/dts/ | arch/arm/boot/dts/stm32mp15*}}.
 
** The source code path is {{CodeSource | Linux kernel | arch/arm/boot/dts/ | arch/arm/boot/dts/stm32mp15*}}.
Line 18: Line 14:
 
** The source code path is {{CodeSource | U-Boot | arch/arm/dts/ | arch/arm/dts/stm32mp15*}}.
 
** The source code path is {{CodeSource | U-Boot | arch/arm/dts/ | arch/arm/dts/stm32mp15*}}.
 
** The U-Boot add-ons file, "<dts-file-name>-u-boot.dtsi", is automatically included at the end of "<dts-file-name>.dts" during device tree compilation (this is a generic U-Boot Makefile behavior).
 
** The U-Boot add-ons file, "<dts-file-name>-u-boot.dtsi", is automatically included at the end of "<dts-file-name>.dts" during device tree compilation (this is a generic U-Boot Makefile behavior).
* In '''TF-A''', Linux files are partly copied (for device tree blob size optimization) and completed with the security configuration (firewalling), and the DDR configuration is also added (same files as U-Boot).
+
* In '''TF-A''', Linux files are partly copied (for device tree blob size optimization), completed with the security configuration (firewalling) and the DDR configuration (same files as U-Boot). {{CodeSource | TF-A | docs/devicetree/bindings/ | TF-A device tree bindings}} reading is needed to understand which parts of the Linux device tree must be kept or can be deleted during the partial copy.
 
** The source code path is {{CodeSource | TF-A | fdts/ | fdts/stm32mp15*}}.
 
** The source code path is {{CodeSource | TF-A | fdts/ | fdts/stm32mp15*}}.
<br />
+
* In '''OP-TEE''', TF-A files are reused, except the DDR configuration ones.
 
+
** The source code path is {{CodeSource | OP-TEE_OS | core/arch/arm/dts/ | core/arch/arm/dts/stm32mp15*}}.
The figure below shows the device tree creation flow for Linux, U-Boot and TF-A:
+
The figure below shows the device tree creation flow for Linux, U-Boot, TF-A and OP-TEE:
[[File:Device_tree_for_Linux_U-Boot_TF-A.png|center|link=]]
+
[[File:Device_tree_for_Linux_U-Boot_TF-A_OP-TEE.png|center|link=]]
 
Color legend:  
 
Color legend:  
 
* <span style="color:#FFFFFF; background:{{STDarkBlue}};">&nbsp;Linux&nbsp;</span> in dark blue
 
* <span style="color:#FFFFFF; background:{{STDarkBlue}};">&nbsp;Linux&nbsp;</span> in dark blue
* <span style="color:#FFFFFF; background:{{STLightGreen}};">&nbsp;U-Boot&nbsp;</span> in green
+
* <span style="color:#FFFFFF; background:{{STLightGreen}};">&nbsp;U-Boot&nbsp;</span> add-ons in green
* <span style="color:#FFFFFF; background:{{STPink}};">&nbsp;TF-A&nbsp;</span> in pink
+
* <span style="color:#FFFFFF; background:{{STPink}};">&nbsp;DDR configuration&nbsp;</span> for TF-A and U-Boot in pink
* <span style="color:#FFFFFF; background:{{STLightBlue}};">&nbsp;STM32CubeMX generated parts&nbsp;</span> in light blue
+
* <span style="color:#FFFFFF; background:{{STLightBlue}};">&nbsp;STM32CubeMX generated parts&nbsp;</span> in light blue (not used above but visible in [[#STM32CubeMX_generated_device_tree|STM32CubeMX]] section down in this article)
  +
* The '''hashed''' areas on Linux device tree files represent the fact that these files are modified, so partly copied and updated
 
The above color codes are used for all the figures included in this article.
 
The above color codes are used for all the figures included in this article.
   
Line 35: Line 32:
 
As explained in the STM32 MPU Embedded Software [[STM32MPU_Embedded_Software_architecture_overview#Open_Source_Software_(OSS)_philosophy| Open Source Software (OSS) philosophy]], STMicroelectronics maximizes the usage of open source software and the upstreaming to the communities.
 
As explained in the STM32 MPU Embedded Software [[STM32MPU_Embedded_Software_architecture_overview#Open_Source_Software_(OSS)_philosophy| Open Source Software (OSS) philosophy]], STMicroelectronics maximizes the usage of open source software and the upstreaming to the communities.
   
So, the device tree files supporting the [[STM32MP157x-EV1 - hardware description|evaluation board]] and the [[STM32MP157x-DKx - hardware description|Discovery kit]] are '''upstreamed''' to their official respective repositories. But waiting for the upstream process completion, STMicroelectronics latest contributions are available in advance on github in {{CodeSource | Linux kernel | arch/arm/boot/dts/ | Linux}}, {{CodeSource | U-Boot | arch/arm/dts/ | U-Boot}} and {{CodeSource | TF-A | fdts/ | TF-A}} repositories.
+
So, the device tree files supporting the [[STM32MP157x-EV1 - hardware description|evaluation board]] and the [[STM32MP157x-DKx - hardware description|discovery kit]] are '''upstreamed''' to their official respective repositories. But waiting for the upstream process completion, STMicroelectronics latest contributions are available in advance on github in {{CodeSource | Linux kernel | arch/arm/boot/dts/ | Linux}}, {{CodeSource | U-Boot | arch/arm/dts/ | U-Boot}}, {{CodeSource | TF-A | fdts/ | TF-A}} and {{CodeSource | OP-TEE_OS | core/arch/arm/dts/ | OP-TEE}} repositories.
   
 
{{Info|The figures shown below are reflecting the '''current implementation on github''' and they may be somehow in advance compare to the '''upstreamed''' version for all parts that are still under review.}}
 
{{Info|The figures shown below are reflecting the '''current implementation on github''' and they may be somehow in advance compare to the '''upstreamed''' version for all parts that are still under review.}}
Line 51: Line 48:
   
 
==== TF-A ====
 
==== TF-A ====
  +
[[File:Device tree TF-A upstreamed.png|center|link=]]
  +
[[File:Device tree legend.png|center|link=]]<br />
  +
Note: The hashed areas on Linux device tree files represent the fact that these files are modified in TF-A.
   
[[File:Device tree TF-A upstreamed.png|center|link=]]
+
==== OP-TEE ====
  +
[[File:Device tree OP-TEE upstreamed.png|center|link=]]
 
[[File:Device tree legend.png|center|link=]]<br />
 
[[File:Device tree legend.png|center|link=]]<br />
Note: The hashed areas on Linux device tree files represent the fact that these files are partly copied in TF-A.<br />
+
Note: The hashed areas on Linux device tree files represent the fact that these files are modified in OP-TEE.<br />
  +
 
  +
{{ReviewsComments|-- [[User:Etienne Carriere|Etienne Carriere]] ([[User talk:Etienne Carriere|talk]]) 17:33, 26 June 2020 (CEST)<br />The figure must be updated. OP-TEE current (v3.9.0) mainline DTS files are the Linux v5.6 DTS files with input configuration information removed and a bit of OP-TEE specific configuration changes. Note that the mainline evolves and OP-TEE mainline will soon sync with latest Linux DTS files.
  +
 
  +
I propose that you keep a simplified views (with few boards) and an explicit sentence. Modified files are SoC base 'stm32mp151.dtsi'
  +
and the boards, for input config info removal. I propose you show only few board as example, i.e. only:
  +
stm32mp151.dtsi  (Modified)
  +
stm32mp157c-dk2.dts (Modified)
  +
stm32mp157c-ev1.dts (Modified)
  +
}}
   
 
=== STM32CubeMX generated device tree ===
 
=== STM32CubeMX generated device tree ===
Line 72: Line 82:
 
==== TF-A ====
 
==== TF-A ====
 
[[File:Device tree TF-A STM32CubeMX.png|center|link=]]<br />
 
[[File:Device tree TF-A STM32CubeMX.png|center|link=]]<br />
  +
  +
==== OP-TEE ====
  +
STM32CubeMX does not generate any device tree source files dedicated to OP-TEE, but these can be derived from the device tree source files generated for TF-A. In {{CodeSource | OP-TEE_OS | / | OP-TEE github release}}, OP-TEE files are the very TF-A source files with the DDR dtsi files removed since fully unused. However, one can copy TF-A device tree source files stm32mp15* to {{CodeSource | OP-TEE_OS | core/arch/arm/dts/ | OP-TEE dts/}}&nbsp; source directory and build OP-TEE with.
   
 
<noinclude>
 
<noinclude>