<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/atf/plat/arm/board/juno/include, branch master</title>
<subtitle>Broadcom-s Trusted Firmware A</subtitle>
<id>https://git.openwrt.org/project/bcm63xx/atf/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/project/bcm63xx/atf/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/'/>
<updated>2019-08-01T20:45:03Z</updated>
<entry>
<title>Switch AARCH32/AARCH64 to __aarch64__</title>
<updated>2019-08-01T20:45:03Z</updated>
<author>
<name>Julius Werner</name>
</author>
<published>2019-07-09T21:02:43Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=402b3cf8766fe2cb4ae462f7ee7761d08a1ba56c'/>
<id>urn:sha1:402b3cf8766fe2cb4ae462f7ee7761d08a1ba56c</id>
<content type='text'>
NOTE: AARCH32/AARCH64 macros are now deprecated in favor of __aarch64__.

All common C compilers pre-define the same macros to signal which
architecture the code is being compiled for: __arm__ for AArch32 (or
earlier versions) and __aarch64__ for AArch64. There's no need for TF-A
to define its own custom macros for this. In order to unify code with
the export headers (which use __aarch64__ to avoid another dependency),
let's deprecate the AARCH32 and AARCH64 macros and switch the code base
over to the pre-defined standard macro. (Since it is somewhat
unintuitive that __arm__ only means AArch32, let's standardize on only
using __aarch64__.)

Change-Id: Ic77de4b052297d77f38fc95f95f65a8ee70cf200
Signed-off-by: Julius Werner &lt;jwerner@chromium.org&gt;
</content>
</entry>
<entry>
<title>n1sdp: add code for DDR ECC enablement and BL33 copy to DDR</title>
<updated>2019-06-26T13:07:51Z</updated>
<author>
<name>Manoj Kumar</name>
</author>
<published>2019-06-21T16:07:13Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=de8bc83ee9401acdab20fd8ae1f9cb9bf7ef7829'/>
<id>urn:sha1:de8bc83ee9401acdab20fd8ae1f9cb9bf7ef7829</id>
<content type='text'>
N1SDP platform supports RDIMMs with ECC capability. To use the ECC
capability, the entire DDR memory space has to be zeroed out before
enabling the ECC bits in DMC620. Zeroing out several gigabytes of
memory from SCP is quite time consuming so functions are added that
zeros out the DDR memory from application processor which is
much faster compared to SCP. BL33 binary cannot be copied to DDR memory
before enabling ECC so this is also done by TF-A from IOFPGA-DDR3
memory to main DDR4 memory after ECC is enabled.

Original PLAT_PHY_ADDR_SPACE_SIZE was limited to 36-bits with which
the entire DDR space cannot be accessed as DRAM2 starts in base
0x8080000000. So these macros are redefined for all ARM platforms.

Change-Id: If09524fb65b421b7a368b1b9fc52c49f2ddb7846
Signed-off-by: Manoj Kumar &lt;manoj.kumar3@arm.com&gt;
</content>
</entry>
<entry>
<title>plat/arm: mhu: make mhu driver generic</title>
<updated>2019-03-13T00:54:35Z</updated>
<author>
<name>Masahisa Kojima</name>
</author>
<published>2019-03-07T02:23:42Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=cf6c30e08ba54a22a0ce8abd6eac8b1d1ccad324'/>
<id>urn:sha1:cf6c30e08ba54a22a0ce8abd6eac8b1d1ccad324</id>
<content type='text'>
MHU doorbell driver requires arm platform specific
macro "PLAT_CSS_MHU_BASE".
Rename it to "PLAT_MHUV2_BASE", so that platforms other than arm
can use generic MHU doorbell driver.

Signed-off-by: Masahisa Kojima &lt;masahisa.kojima@linaro.org&gt;
</content>
</entry>
<entry>
<title>plat/arm: Move dynamic xlat enable logic to makefile</title>
<updated>2019-01-25T16:04:11Z</updated>
<author>
<name>Antonio Nino Diaz</name>
</author>
<published>2019-01-23T16:23:07Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=3661d8e7adbf83175a85e2498dbbef7b7a67e8d5'/>
<id>urn:sha1:3661d8e7adbf83175a85e2498dbbef7b7a67e8d5</id>
<content type='text'>
The PLAT_XLAT_TABLES_DYNAMIC build option, defined in platform_def.h
in Arm platforms, is checked by several headers, affecting their
behaviour. To avoid issues around the include ordering of the headers,
the definition should be moved to the platform's makefile.

Change-Id: I0e12365c8d66309122e8a20790e1641a4f480a10
Signed-off-by: Antonio Nino Diaz &lt;antonio.ninodiaz@arm.com&gt;
</content>
</entry>
<entry>
<title>plat/arm: Sanitise includes</title>
<updated>2019-01-25T16:04:10Z</updated>
<author>
<name>Antonio Nino Diaz</name>
</author>
<published>2019-01-25T14:30:04Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=bd9344f670a46125cdd8949ded75be124f34d587'/>
<id>urn:sha1:bd9344f670a46125cdd8949ded75be124f34d587</id>
<content type='text'>
Use full include paths like it is done for common includes.

This cleanup was started in commit d40e0e08283a ("Sanitise includes
across codebase"), but it only cleaned common files and drivers. This
patch does the same to Arm platforms.

Change-Id: If982e6450bbe84dceb56d464e282bcf5d6d9ab9b
Signed-off-by: Antonio Nino Diaz &lt;antonio.ninodiaz@arm.com&gt;
</content>
</entry>
<entry>
<title>plat/arm: Save BL2 descriptors to reserved memory.</title>
<updated>2019-01-23T16:01:19Z</updated>
<author>
<name>Sathees Balya</name>
</author>
<published>2018-11-15T14:22:30Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=5b8d50e40701ebb6a7ba548ccaa96ba879587fb9'/>
<id>urn:sha1:5b8d50e40701ebb6a7ba548ccaa96ba879587fb9</id>
<content type='text'>
On ARM platforms, the BL2 memory can be overlaid by BL31/BL32. The memory
descriptors describing the list of executable images are created in BL2
R/W memory, which could be possibly corrupted later on by BL31/BL32 due
to overlay. This patch creates a reserved location in SRAM for these
descriptors and are copied over by BL2 before handing over to next BL
image.

Also this patch increases the PLAT_ARM_MAX_BL2_SIZE for juno when TBBR
is enabled.

Fixes ARM-Software/tf-issues#626

Change-Id: I755735706fa702024b4032f51ed4895b3687377f
Signed-off-by: Sathees Balya &lt;sathees.balya@arm.com&gt;
</content>
</entry>
<entry>
<title>Sanitise includes across codebase</title>
<updated>2019-01-04T10:43:17Z</updated>
<author>
<name>Antonio Nino Diaz</name>
</author>
<published>2018-12-14T00:18:21Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=09d40e0e08283a249e7dce0e106c07c5141f9b7e'/>
<id>urn:sha1:09d40e0e08283a249e7dce0e106c07c5141f9b7e</id>
<content type='text'>
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 &lt;antonio.ninodiaz@arm.com&gt;
</content>
</entry>
<entry>
<title>Merge pull request #1699 from chandnich/sgi-mt-support</title>
<updated>2018-12-03T13:29:33Z</updated>
<author>
<name>Soby Mathew</name>
</author>
<published>2018-12-03T13:29:33Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=41771df84944f7739a5bff18b1207e1dc2d3cc59'/>
<id>urn:sha1:41771df84944f7739a5bff18b1207e1dc2d3cc59</id>
<content type='text'>
Add support to implement multi-threaded platforms for SGI</content>
</entry>
<entry>
<title>plat/css: allow platforms to define the system power domain level</title>
<updated>2018-11-27T05:02:55Z</updated>
<author>
<name>Chandni Cherukuri</name>
</author>
<published>2018-10-16T09:49:54Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=eff2f44430fcd452d2f5425566e109a8c517b1d1'/>
<id>urn:sha1:eff2f44430fcd452d2f5425566e109a8c517b1d1</id>
<content type='text'>
The CSS_SYSTEM_PWR_DMN_LVL macro that defines the system power domain
level is fixed at ARM_PWR_LVL2 for all CSS platforms. However, the
system power domain level can be different for CSS platforms that
use multi-threaded CPUs.

So, in preparation towards adding support for platforms that use
multi-threaded CPUs, refactor the definition of CSS_SYSTEM_PWR_DMN_LVL
such that CSS_SYSTEM_PWR_DMN_LVL is uniquely defined for each of the
CSS platform.

Change-Id: Ia837b13f6865e71da01780993c048b45b7f36d85
Signed-off-by: Chandni Cherukuri &lt;chandni.cherukuri@arm.com&gt;
</content>
</entry>
<entry>
<title>juno: Add romlib support</title>
<updated>2018-11-23T11:52:01Z</updated>
<author>
<name>Sathees Balya</name>
</author>
<published>2018-11-02T14:56:06Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=afa5cfea6079bf7a10db53edcc72e6b8fa05c600'/>
<id>urn:sha1:afa5cfea6079bf7a10db53edcc72e6b8fa05c600</id>
<content type='text'>
This patch adds support to build a combined BL1
and ROMLIB binary file with the right page
alignment in Juno. When USE_ROMLIB=1 is set for
Juno, it generates the combined file
bl1_romlib.bin which needs to be used instead of
bl1.bin

Change-Id: I407efbe48d3e522fa6ef855538a9587193cb1919
Signed-off-by: Sathees Balya &lt;sathees.balya@arm.com&gt;
</content>
</entry>
</feed>
