<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/atf/drivers/arm, 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-10-08T12:58:25Z</updated>
<entry>
<title>Correct UART PL011 initialization calculation</title>
<updated>2019-10-08T12:58:25Z</updated>
<author>
<name>Avinash Mehta</name>
</author>
<published>2019-10-08T11:09:04Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=38d5e150edc82570e1a3e9dc2e95dce96e6fd94e'/>
<id>urn:sha1:38d5e150edc82570e1a3e9dc2e95dce96e6fd94e</id>
<content type='text'>
Currently for Armv7 plaforms the quotient calculated in pl011
uart init code is moved to register r1.

This patch moves the quotient to register r2 as done for other
platforms in the udiv instruction. Value of register r2 is then
used to calculate the values for IBRD and FBRD register

Change-Id: Ie6622f9f0e6d634378b471df5d02823b492c8a24
Signed-off-by: Avinash Mehta &lt;avinash.mehta@arm.com&gt;
</content>
</entry>
<entry>
<title>Merge "GICv3 driver: Fix support for full SPI range" into integration</title>
<updated>2019-09-27T09:49:05Z</updated>
<author>
<name>Soby Mathew</name>
</author>
<published>2019-09-27T09:49:05Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=1ec391932653b2ac452834ed3317ff3bd3cac82f'/>
<id>urn:sha1:1ec391932653b2ac452834ed3317ff3bd3cac82f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>GICv3: Enable multi socket GIC redistributor frame discovery</title>
<updated>2019-09-26T03:01:28Z</updated>
<author>
<name>Madhukar Pappireddy</name>
</author>
<published>2019-05-15T23:25:41Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=ec834925f3cb5cb3934010bbc8077293e610d2ac'/>
<id>urn:sha1:ec834925f3cb5cb3934010bbc8077293e610d2ac</id>
<content type='text'>
This patch provides declaration and definition of new GICv3 driver
API: gicv3_rdistif_probe().This function delegates the responsibility
of discovering the corresponding Redistributor base frame to each CPU
itself. It is a modified version of gicv3_rdistif_base_addrs_probe()
and is executed by each CPU in the platform unlike the previous
approach in which only the Primary CPU did the discovery of all the
Redistributor frames for every CPU.

The flush operations as part of gicv3_driver_init() function are
made necessary even for platforms with WARMBOOT_ENABLE_DCACHE_EARLY
because the GICv3 driver data structure contents are accessed by CPU
with D-Cache turned off during power down operations.

Change-Id: I1833e81d3974b32a3e4a3df4766a33d070982268
Signed-off-by: Madhukar Pappireddy &lt;madhukar.pappireddy@arm.com&gt;
</content>
</entry>
<entry>
<title>GICv3 driver: Fix support for full SPI range</title>
<updated>2019-09-13T14:47:13Z</updated>
<author>
<name>Alexei Fedorov</name>
</author>
<published>2019-09-13T14:47:13Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=eb5f0ba41eaead241efad2bc1e0502211fdca93b'/>
<id>urn:sha1:eb5f0ba41eaead241efad2bc1e0502211fdca93b</id>
<content type='text'>
This patch fixes GICv3 driver bug which causes assertion
when full range of SPI INTIDs 32-1019 is supported in
GICv3 implementation.

Change-Id: Ib6da4b6eea868cff271cb32c7c7570bf5547ab47
Signed-off-by: Alexei Fedorov &lt;Alexei.Fedorov@arm.com&gt;
</content>
</entry>
<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>Replace __ASSEMBLY__ with compiler-builtin __ASSEMBLER__</title>
<updated>2019-08-01T20:14:12Z</updated>
<author>
<name>Julius Werner</name>
</author>
<published>2019-07-09T20:49:11Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=d5dfdeb65ff5b7f24dded201d2945c7b74565ce8'/>
<id>urn:sha1:d5dfdeb65ff5b7f24dded201d2945c7b74565ce8</id>
<content type='text'>
NOTE: __ASSEMBLY__ macro is now deprecated in favor of __ASSEMBLER__.

All common C compilers predefine a macro called __ASSEMBLER__ when
preprocessing a .S file. There is no reason for TF-A to define it's own
__ASSEMBLY__ macro for this purpose instead. To unify code with the
export headers (which use __ASSEMBLER__ to avoid one extra dependency),
let's deprecate __ASSEMBLY__ and switch the code base over to the
predefined standard.

Change-Id: Id7d0ec8cf330195da80499c68562b65cb5ab7417
Signed-off-by: Julius Werner &lt;jwerner@chromium.org&gt;
</content>
</entry>
<entry>
<title>Remove MULTI_CONSOLE_API flag and references to it</title>
<updated>2019-06-28T09:52:48Z</updated>
<author>
<name>Ambroise Vincent</name>
</author>
<published>2019-04-04T08:13:28Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=5b6ebeec9c99f8d6a539d3b15e5dfb827891174a'/>
<id>urn:sha1:5b6ebeec9c99f8d6a539d3b15e5dfb827891174a</id>
<content type='text'>
The new API becomes the default one.

Change-Id: Ic1d602da3dff4f4ebbcc158b885295c902a24fec
Signed-off-by: Ambroise Vincent &lt;ambroise.vincent@arm.com&gt;
</content>
</entry>
<entry>
<title>Console: removed legacy console API</title>
<updated>2019-06-26T09:52:23Z</updated>
<author>
<name>Ambroise Vincent</name>
</author>
<published>2019-03-27T10:22:10Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=51e24ec2c6f4d72df50cf62766311f3773d4e117'/>
<id>urn:sha1:51e24ec2c6f4d72df50cf62766311f3773d4e117</id>
<content type='text'>
This interface has been deprecated in favour of MULTI_CONSOLE_API.

Change-Id: I6170c1c8c74a890e5bd6d05396743fe62024a08a
Signed-off-by: Ambroise Vincent &lt;ambroise.vincent@arm.com&gt;
</content>
</entry>
<entry>
<title>Prevent pending G1S interrupt become G0 interrupt</title>
<updated>2019-06-05T03:05:05Z</updated>
<author>
<name>James kung</name>
</author>
<published>2019-05-31T07:40:05Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=acc29852687531a28906f77ef07c5b6eeb550636'/>
<id>urn:sha1:acc29852687531a28906f77ef07c5b6eeb550636</id>
<content type='text'>
According to Arm GIC spec(IHI0069E, section 4.6.1),
when GICD_CTLR.DS == 0, Secure Group 1 interrupts
are treated as Group 0 by a CPU interface if:
- The PE does not implement EL3.
- ICC_SRE_EL1(S).SRE == 0

When a cpu enter suspend or deep idle, it might be
powered off. When the cpu resume, according to
the GIC spec(IHI0069E, section 9.2.15, 9.2.16 and
9.2.22) the ICC_SRE_EL1.SRE reset value is 0 (if
write is allowed) and G0/G1S/G1NS interrupt of the
GIC cpu interface are all disabled.

If a G1S SPI interrupt occurred and the target cpu
of the SPI is assigned to a specific cpu which is
in suspend and is powered off, when the cpu resume
and start to initial the GIC cpu interface, the
initial sequence might affect the interrupt group
type of the pending interrupt on the cpu interface.

Current initial sequence on the cpu interface is:
1. Enable G0 interrupt
2. Enable G1S interrupt
3. Enable ICC_SRE_EL1(S).SRE

It is possible to treat the pending G1S interrupt
as G0 interrupt on the cpu interface if the G1S
SPI interrupt occurred between step2 and step3.

To prevent the above situation happend, the initial
sequence should be changed as follows:
1. Enable ICC_SRE_EL1(S).SRE
2. Enable G0 interrupt
3. Enable G1S interrupt

Change-Id: Ie34f6e0b32eb9a1677ff72571fd4bfdb5cae25b0
Signed-off-by: James Kung &lt;kong1191@gmail.com&gt;
</content>
</entry>
<entry>
<title>drivers: scmi: scmi_sq: Modify wrong payload length</title>
<updated>2019-05-23T05:41:35Z</updated>
<author>
<name>Masahisa Kojima</name>
</author>
<published>2019-05-23T05:41:35Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/atf/commit/?id=292bc551930f3472cce0930f392a6aeeca5eeb88'/>
<id>urn:sha1:292bc551930f3472cce0930f392a6aeeca5eeb88</id>
<content type='text'>
Payload length of the get dram mapping information message is 0.
The mbx_mem-&gt;len parameter should be 4, it only contains
message header.

Fixes: b67d202 ("plat/synquacer: enable SCMI support")
Signed-off-by: Masahisa Kojima &lt;masahisa.kojima@linaro.org&gt;
Change-Id: If1cd4c855da2dc5dc4b6da3bea152b8441971de7
</content>
</entry>
</feed>
