Searched hist:"311 b1773641674e4b498dbf577635d0c4c63ab48" (Results 1 – 2 of 2) sorted by relevance
| /rk3399_ARM-atf/drivers/arm/gic/v2/ |
| H A D | gicv2_main.c | 311b1773641674e4b498dbf577635d0c4c63ab48 Tue Feb 14 10:11:52 UTC 2017 Soby Mathew <soby.mathew@arm.com> Flush the GIC driver data after init
The GIC driver data is initialized by the primary CPU with caches
enabled. When the secondary CPU boots up, it initializes the
GICC/GICR interface with the caches disabled and there is a chance that
the driver data is not yet written back to the memory. This patch fixes
this problem by flushing the driver data after they have been
initialized.
Change-Id: Ie9477029683846209593ff005d2bac559bb8f5e6
Signed-off-by: Soby Mathew <soby.mathew@arm.com>
|
| /rk3399_ARM-atf/drivers/arm/gic/v3/ |
| H A D | gicv3_main.c | 311b1773641674e4b498dbf577635d0c4c63ab48 Tue Feb 14 10:11:52 UTC 2017 Soby Mathew <soby.mathew@arm.com> Flush the GIC driver data after init
The GIC driver data is initialized by the primary CPU with caches
enabled. When the secondary CPU boots up, it initializes the
GICC/GICR interface with the caches disabled and there is a chance that
the driver data is not yet written back to the memory. This patch fixes
this problem by flushing the driver data after they have been
initialized.
Change-Id: Ie9477029683846209593ff005d2bac559bb8f5e6
Signed-off-by: Soby Mathew <soby.mathew@arm.com>
|