Home
last modified time | relevance | path

Searched hist:"5135 d875e1457ef946a055003d8f80713e862135" (Results 1 – 3 of 3) sorted by relevance

/openbmc/linux/arch/arm/include/asm/
H A Dhardirq.hdiff 5135d875e1457ef946a055003d8f80713e862135 Tue Nov 27 20:54:41 CST 2012 Nicolas Pitre <nicolas.pitre@linaro.org> ARM: SMP: basic IPI triggered completion support

We need a mechanism to let an inbound CPU signal that it is alive before
even getting into the kernel environment i.e. from early assembly code.
Using an IPI is the simplest way to achieve that.

This adds some basic infrastructure to register a struct completion
pointer to be "completed" when the dedicated IPI for this task is
received.

Signed-off-by: Nicolas Pitre <nico@linaro.org>
H A Dsmp.hdiff 5135d875e1457ef946a055003d8f80713e862135 Tue Nov 27 20:54:41 CST 2012 Nicolas Pitre <nicolas.pitre@linaro.org> ARM: SMP: basic IPI triggered completion support

We need a mechanism to let an inbound CPU signal that it is alive before
even getting into the kernel environment i.e. from early assembly code.
Using an IPI is the simplest way to achieve that.

This adds some basic infrastructure to register a struct completion
pointer to be "completed" when the dedicated IPI for this task is
received.

Signed-off-by: Nicolas Pitre <nico@linaro.org>
/openbmc/linux/arch/arm/kernel/
H A Dsmp.cdiff 5135d875e1457ef946a055003d8f80713e862135 Tue Nov 27 20:54:41 CST 2012 Nicolas Pitre <nicolas.pitre@linaro.org> ARM: SMP: basic IPI triggered completion support

We need a mechanism to let an inbound CPU signal that it is alive before
even getting into the kernel environment i.e. from early assembly code.
Using an IPI is the simplest way to achieve that.

This adds some basic infrastructure to register a struct completion
pointer to be "completed" when the dedicated IPI for this task is
received.

Signed-off-by: Nicolas Pitre <nico@linaro.org>