OMAP4: IRQ line of CortexA9 performance monitor

OMAP4: IRQ line of CortexA9 performance monitor

[Ming Lei]

Hi,

>From chapter 17 of "Interrupt controller", OMAP4 TRM, I can't
find what is the interrupt line of CortexA9 performance monitor
in omap4. Seems without this information, we can't use perf on
omap4.

Any suggestions or ideas about it?

-- 
Lei Ming

Re: OMAP4: IRQ line of CortexA9 performance monitor

[Måns Rullgård]

Ming Lei <tom.leiming@gmail.com> writes:

> Hi,
>
> From chapter 17 of "Interrupt controller", OMAP4 TRM, I can't
> find what is the interrupt line of CortexA9 performance monitor
> in omap4. Seems without this information, we can't use perf on
> omap4.
>
> Any suggestions or ideas about it?

The PMU interrupt is routed through the CTI, which needs to be properly
configured.  Unfortunately, the CTI is not documented in the public TRM,
and nobody has seen fit to submit a patch suitable for upstream.  Some
dirty hacks have been posted, though.

-- 
Måns Rullgård
mans@mansr.com

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: OMAP4: IRQ line of CortexA9 performance monitor

[Santosh Shilimkar]

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Måns Rullgård
> Sent: Monday, February 21, 2011 10:49 PM
> To: linux-omap@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org
> Subject: Re: OMAP4: IRQ line of CortexA9 performance monitor
>
> Ming Lei <tom.leiming@gmail.com> writes:
>
> > Hi,
> >
> > From chapter 17 of "Interrupt controller", OMAP4 TRM, I can't
> > find what is the interrupt line of CortexA9 performance monitor
> > in omap4. Seems without this information, we can't use perf on
> > omap4.
> >
> > Any suggestions or ideas about it?
>
> The PMU interrupt is routed through the CTI, which needs to be
> properly
> configured.  Unfortunately, the CTI is not documented in the public
> TRM,
> and nobody has seen fit to submit a patch suitable for upstream.
> Some dirty hacks have been posted, though.
>
Mans is right. Last time I looked at this, the OMAP4 PMU support
needed some hacky code and was not fitting to the generic PMU
framework.

I will take a second look at it and see if a patch can be generated
for upstream.

Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html