On 29/07/15 11:52, Rohini Kulkarni wrote:
On Tue, Jul 28, 2015 at 12:24 PM, Sebastian Huber
<sebastian.hu...@embedded-brains.de
<mailto:sebastian.hu...@embedded-brains.de>> wrote:
Hello Rohini,
please use the devel list.
On 28/07/15 07:41, Rohini Kulkarni wrote:
Hi,
I wish to understand where the interprocessor interrupts are
used during the boot process. During final initialization of
SMP I can see
rtems_interrupt_handler_install(
ARM_GIC_IRQ_SGI_0,
"IPI",
RTEMS_INTERRUPT_UNIQUE,
bsp_inter_processor_interrupt,
NULL
);
Raspberry Pi 2 does not have the generic interrupt controller.
Interrupt routing will have to be handled differently. So I
wish to understand how/ where it is used. I suppose this might
be the problem.
Sorry, that the documentation is so scattered. I think we should
move everything into the CPU Architecture Supplement. It would be
nice if you can help to improve the documentation since you have a
different view point.
You must install the IPI during the system initialization. It is
raised via the _CPU_SMP_Send_interrupt() function, for an example
see arm-a9mpcore-smp.c.
I could locate the function in arm-a9mpcore-smp.c. but it would be
helpful if I can know where this being called from, a deeper call
hierarchy, so that I can ascertain this is a problem. I can see a
Send_messgae function call this. But don't know where the send message
is being called from.
You can run one of the SMP tests on the realview_pbx_a9_qemu_smp BSP on
Qemu and set a break point to _CPU_SMP_Send_interrupt() if you want to
know how it is used.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel