bcm63xx/atf/plat/xilinx/zynqmp/include, branch master

zynqmp: add support for multi console interface

2019-07-01T06:05:34Z

This patch addds multi console interface for ZynqMP platform Change-Id: I508a61412df2b71d04bca6a1139c8f32cbd7dccd Signed-off-by: Ambroise Vincent Signed-off-by: Siva Durga Prasad Paladugu Tested-by: Siva Durga Prasad Paladugu

Arm platforms: Rename PLAT_ARM_NS_IMAGE_OFFSET

2019-02-01T09:48:34Z

PLAT_ARM_NS_IMAGE_OFFSET is in fact not an offset relative to some base address, it is an absolute address. Rename it to avoid any confusion. Change-Id: I1f7f5e8553cb267786afe7e5f3cd4d665b610d3f Signed-off-by: Sandrine Bailleux

xilinx: Move IPI functions to common file

2019-01-09T20:38:00Z

pm_service ipi functions can be used by other xilinx platforms. So move it to common directory. Also change node_id member type in pm_proc structure so it can be used for versal where device IDs are used instead of node IDs. To accommodate this change header files are re-organized. Signed-off-by: Tejas Patel Reviewed-by: Siva Durga Prasad Paladugu Signed-off-by: Jolly Shah

Move generic ipi_mb functions to common files

2019-01-09T20:15:10Z

ipi_mb functions can be used for other Xilinx platform. Move it to common file from platform specific files. Signed-off-by: Tejas Patel Reviewed-by: Siva Durga Prasad Paladugu Signed-off-by: Jolly Shah

xilinx: Remove platform specific dependency from IPI function

2019-01-09T20:12:18Z

ipi_mb function uses platform specific ipi configuration table. These ipi_mb functions can be used for other Xilinx platform. So, instead of using direct data structure, initialize IPI configuration data by passing platform specific ipi table. Macros are updated accordingly for this ipi table change. This change is done so that ipi_mb functions can be moved to common file without major changes. All common functions now would be moved to common file in next patch. Signed-off-by: Tejas Patel Reviewed-by: Siva Durga Prasad Paladugu Signed-off-by: Jolly Shah

xilinx: zynqmp: Move zynqmp_ipi.h to include directory

2019-01-09T20:07:06Z

Move zynqmp_ipi.h to platform specific include directory. Rename it to plat_ipi.h instead of platform name. So, it can be used to common source files which needs platform specific data. Signed-off-by: Tejas Patel Reviewed-by: Siva Durga Prasad Paladugu Signed-off-by: Jolly Shah

plat: xilinx: zynqmp: Move zynqmp_def.h to include directory

2019-01-09T20:05:56Z

Move zynqmp_def.h to platform specific include directory. Also, update source file to include header file from updated path of zynqmp_def.h Signed-off-by: Tejas Patel Reviewed-by: Siva Durga Prasad Paladugu Signed-off-by: Jolly Shah

plat: xilinx: zynqmp: Move zynqmp_private.h to include directory

2019-01-09T20:05:13Z

Move zynqmp_private.h to platform specific include directory. Also, rename it to plat_private.h instead of having platform name. So, it can be used to common source files which needs platform specific data. Signed-off-by: Tejas Patel Reviewed-by: Siva Durga Prasad Paladugu Signed-off-by: Jolly Shah

Sanitise includes across codebase

2019-01-04T10:43:17Z

Enforce full include path for includes. Deprecate old paths. The following folders inside include/lib have been left unchanged: - include/lib/cpus/${ARCH} - include/lib/el3_runtime/${ARCH} The reason for this change is that having a global namespace for includes isn't a good idea. It defeats one of the advantages of having folders and it introduces problems that are sometimes subtle (because you may not know the header you are actually including if there are two of them). For example, this patch had to be created because two headers were called the same way: e0ea0928d5b7 ("Fix gpio includes of mt8173 platform to avoid collision."). More recently, this patch has had similar problems: 46f9b2c3a282 ("drivers: add tzc380 support"). This problem was introduced in commit 4ecca33988b9 ("Move include and source files to logical locations"). At that time, there weren't too many headers so it wasn't a real issue. However, time has shown that this creates problems. Platforms that want to preserve the way they include headers may add the removed paths to PLAT_INCLUDES, but this is discouraged. Change-Id: I39dc53ed98f9e297a5966e723d1936d6ccf2fc8f Signed-off-by: Antonio Nino Diaz

Standardise header guards across codebase

2018-11-08T10:20:19Z

All identifiers, regardless of use, that start with two underscores are reserved. This means they can't be used in header guards. The style that this project is now to use the full name of the file in capital letters followed by 'H'. For example, for a file called "uart_example.h", the header guard is UART_EXAMPLE_H. The exceptions are files that are imported from other projects: - CryptoCell driver - dt-bindings folders - zlib headers Change-Id: I50561bf6c88b491ec440d0c8385c74650f3c106e Signed-off-by: Antonio Nino Diaz