| /rk3399_ARM-atf/plat/arm/board/fvp_ve/fdts/ |
| H A D | fvp_ve_tb_fw_config.dts | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| H A D | fvp_ve_fw_config.dts | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| /rk3399_ARM-atf/plat/arm/board/a5ds/fdts/ |
| H A D | a5ds_tb_fw_config.dts | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| H A D | a5ds_fw_config.dts | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| /rk3399_ARM-atf/plat/arm/board/juno/fdts/ |
| H A D | juno_tb_fw_config.dts | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| H A D | juno_fw_config.dts | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| /rk3399_ARM-atf/plat/arm/board/fvp_ve/ |
| H A D | platform.mk | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| /rk3399_ARM-atf/plat/arm/board/a5ds/ |
| H A D | platform.mk | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| /rk3399_ARM-atf/lib/fconf/ |
| H A D | fconf_dyn_cfg_getter.c | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| /rk3399_ARM-atf/plat/arm/board/fvp/fdts/ |
| H A D | fvp_tb_fw_config.dts | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| H A D | fvp_fw_config.dts | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| /rk3399_ARM-atf/plat/arm/board/juno/ |
| H A D | platform.mk | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|
| /rk3399_ARM-atf/plat/arm/board/fvp/ |
| H A D | platform.mk | 3cb84a54258e148ba0240fc5fbe4ef828339c13d Sun May 31 07:53:40 UTC 2020 Manish V Badarkhe <Manish.Badarkhe@arm.com> plat/arm: Rentroduce tb_fw_config device tree
Moved BL2 configuration nodes from fw_config to newly
created tb_fw_config device tree.
fw_config device tree's main usage is to hold properties shared
across all BLx images.
An example is the "dtb-registry" node, which contains the
information about the other device tree configurations
(load-address, size).
Also, Updated load-address of tb_fw_config which is now located
after fw_config in SRAM.
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
Change-Id: Ic398c86a4d822dacd55b5e25fd41d4fe3888d79a
|