<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/atf/lib/extensions/spe, 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-01-04T10:43:17Z</updated>
<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>Fix MISRA defects in extension libs</title>
<updated>2018-10-29T14:41:48Z</updated>
<author>
<name>Antonio Nino Diaz</name>
</author>
<published>2018-10-25T15:52:26Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=40daecc1be51383c806c0ac953303e47026abcac'/>
<id>urn:sha1:40daecc1be51383c806c0ac953303e47026abcac</id>
<content type='text'>
No functional changes.

Change-Id: I2f28f20944f552447ac4e9e755493cd7c0ea1192
Signed-off-by: Antonio Nino Diaz &lt;antonio.ninodiaz@arm.com&gt;
</content>
</entry>
<entry>
<title>Merge pull request #1282 from robertovargas-arm/misra-changes</title>
<updated>2018-02-28T18:53:30Z</updated>
<author>
<name>davidcunado-arm</name>
</author>
<published>2018-02-28T18:53:30Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=73a9605197ba04aaf02d436a2a4ad56e695b426c'/>
<id>urn:sha1:73a9605197ba04aaf02d436a2a4ad56e695b426c</id>
<content type='text'>
Misra changes</content>
</entry>
<entry>
<title>Fix MISRA rule 8.4 in common code</title>
<updated>2018-02-28T17:18:46Z</updated>
<author>
<name>Roberto Vargas</name>
</author>
<published>2018-02-12T12:36:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=7fabe1a89903cab4919304faa085ee6eaaec5c9d'/>
<id>urn:sha1:7fabe1a89903cab4919304faa085ee6eaaec5c9d</id>
<content type='text'>
Rule 8.4: A compatible declaration shall be visible when
          an object or function with external linkage is defined.

Change-Id: I26e042cb251a6f9590afa1340fdac73e42f23979
Signed-off-by: Roberto Vargas &lt;roberto.vargas@arm.com&gt;
</content>
</entry>
<entry>
<title>MISRA fixes for AMU/SPE and SVE</title>
<updated>2018-02-27T12:05:59Z</updated>
<author>
<name>Dimitris Papastamos</name>
</author>
<published>2018-02-26T17:56:31Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=700efdd17c16d2c1c3143f3f10da7278075edcf6'/>
<id>urn:sha1:700efdd17c16d2c1c3143f3f10da7278075edcf6</id>
<content type='text'>
Change-Id: I38470528111410cf12b187eb1397d87b812c9416
Signed-off-by: Dimitris Papastamos &lt;dimitris.papastamos@arm.com&gt;
</content>
</entry>
<entry>
<title>Implement {spe,sve}_supported() helpers and refactor code</title>
<updated>2018-02-27T12:05:59Z</updated>
<author>
<name>Dimitris Papastamos</name>
</author>
<published>2018-02-19T14:52:19Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=2ff8fbf3b0d1403afab9b5316fd7ea40859c889c'/>
<id>urn:sha1:2ff8fbf3b0d1403afab9b5316fd7ea40859c889c</id>
<content type='text'>
Implement helpers to test if the core supports SPE/SVE.  We have a
similar helper for AMU and this patch makes all extensions consistent
in their implementation.

Change-Id: I3e6f7522535ca358259ad142550b19fcb883ca67
Signed-off-by: Dimitris Papastamos &lt;dimitris.papastamos@arm.com&gt;
</content>
</entry>
<entry>
<title>Refactor Statistical Profiling Extensions implementation</title>
<updated>2017-11-20T09:55:01Z</updated>
<author>
<name>Dimitris Papastamos</name>
</author>
<published>2017-10-13T11:06:06Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=281a08cc6438d868bd1b0bcf19bc6c95207b42ac'/>
<id>urn:sha1:281a08cc6438d868bd1b0bcf19bc6c95207b42ac</id>
<content type='text'>
Factor out SPE operations in a separate file.  Use the publish
subscribe framework to drain the SPE buffers before entering secure
world.  Additionally, enable SPE before entering normal world.

A side effect of this change is that the profiling buffers are now
only drained when a transition from normal world to secure world
happens.  Previously they were drained also on return from secure
world, which is unnecessary as SPE is not supported in S-EL1.

Change-Id: I17582c689b4b525770dbb6db098b3a0b5777b70a
Signed-off-by: Dimitris Papastamos &lt;dimitris.papastamos@arm.com&gt;
</content>
</entry>
</feed>
