Comment 11 for bug 859825

Hi Wade

On Mon, Oct 24, 2011 at 8:19 AM, Vinod Krishnamoni
<email address hidden> wrote:
> Update from Wade Cherry, who's working on the defect at ARM:
>
> "After incorporating the changes by Inderpal Singh from the Linaro
> branch into my code base for Orion, the Orion board has the pmu
> interrupt for core 0 set to irq 146 and core 1 set to irq 154. However,
> when calling init_pmu() an error is returned indicating that associating
> the irq to a certain core failed. Thus, I was not able to verify the
> changes, though there may be something else at odds here: 1) I'm not
> using Exynos4 but Orion s5p v310, what are the differences? 2) I did not
> use the same code base."
>

1) Exynos4(210) and Orion s5pv310 are the same part. However there a
re a few revisions of the chip could you tell us what CPU id is
reported during boot, or better yet add a bootlog to the bug.

2) is the code base you used available somewhere ?

Thanks
Angus

> --
> You received this bug notification because you are a member of Linaro
> Landing Team: Samsung, which is subscribed to linaro-landing-team-
> samsung.
> https://bugs.launchpad.net/bugs/859825
>
> Title:
>  Samsung Exynos4 ("Orion") doesn't have proper PMU definitions
>
> Status in Linaro Samsung Landing Team Project:
>  Fix Committed
>
> Bug description:
>  This issue was found with Streamline, and later confirmed with perf.
>  arch/arm/plat-s5p/dev-pmu.c is incomplete. Even worse, it pulls old
>  "arm-pmu" device from A8-based SOC (I think) so Streamline/perf think
>  it should work, but it doesn't. The end result is no proper error
>  message for the user and the PMU interrupts are not firing so the data
>  is invalid.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linaro-landing-team-samsung/+bug/859825/+subscriptions
>

--
Angus Ainslie <email address hidden>
Team Lead, Samsung Landing Team