diff options
| author | Thomas Petazzoni <[email protected]> | 2014-04-14 15:54:02 +0200 |
|---|---|---|
| committer | Jason Cooper <[email protected]> | 2014-05-08 14:42:00 +0000 |
| commit | d7df84b3cecad4c768e4065d1d61b2f8fd02b7fa (patch) | |
| tree | 64b55219237723b95291719c0fbe9a3f42efe9cf /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | ef37d337e1d37bd84ccaa5811a8d1f00f8b3677c (diff) | |
irqchip: irq-armada-370-xp: Use cpu notifier to initialize secondary CPUs
Some irqchip initialization must be done on secondary CPUs. On mvebu
platforms, this is currently achieved by having the
arch/arm/mach-mvebu/platsmp.c code directly call into a function
exported by the irqchip driver, which isn't really nice.
This commit changes this by using the same solution as the one used in
the GIC driver: the irqchip driver registers a CPU notifier, which is
used to do the secondary CPU IRQ initialization. This way, the irqchip
driver is completely autonomous, and the function no longer needs to
be exposed from the irqchip driver to the SoC code.
Signed-off-by: Thomas Petazzoni <[email protected]>
Link: https://lkml.kernel.org/r/1397483648-26611-6-git-send-email-thomas.petazzoni@free-electrons.com
Signed-off-by: Jason Cooper <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions