From: Tomasz Figa <t.figa@samsung.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Mj Embd <mj.embd@gmail.com>
Cc: linaro-kernel <linaro-kernel@lists.linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-samsung-soc@vger.kernel.org
Subject: Re: Arndale Timer Interrupt Question
Date: Fri, 10 Jan 2014 17:57:55 +0100 [thread overview]
Message-ID: <52D02693.1040003@samsung.com> (raw)
In-Reply-To: <1437466.9hkS4zH5MN@amdc1032>
Hi,
On 09.01.2014 13:52, Bartlomiej Zolnierkiewicz wrote:
>
> added linux-samsung-soc to cc:,
> it is a better suited list for this question
>
> On Thursday, January 09, 2014 10:30:56 AM Mj Embd wrote:
>> I am a bit confused on the interrupt number for CNTVIRQ..CNTHPIRQ. Can
>> you please help here.
>>
>> As per the exynos5 public manual
>> What is the difference between CPU_nCNTHPIRQ[0] and CNTHPIRQ.
I'm not sure if this is really what I think it is, but looking at the
manual, CPU_nCNTHPIRQ[0] and [1] SPI ports and CNTHPIRQ PPI port seem to
be the same signals, with the difference that the first two are shared
interrupts connected through the combiner, while the last one is a
per-processor interrupt, directly connected to GIC PPI port, allowing
each CPU to get its own CNTHPIRQ signal ([0] for CPU 0 and [1] for CPU 1).
Best regards,
Tomasz
>>
>> While the later has an interrupt ID 26, the former is part of a group
>> with combined interrupt id as 33 for core 0 and 54 for core 1.
>>
>> For a timer interrupt which goes to PL2, which id should be used 26 or
>> 33 for core 0 ?
>>
>> Please clear this confusion.
>>
>> Many Thanks
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-01-10 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 5:00 Arndale Timer Interrupt Question Mj Embd
2014-01-09 12:52 ` Bartlomiej Zolnierkiewicz
2014-01-10 16:57 ` Tomasz Figa [this message]
2014-01-23 6:10 ` Mj Embd
2014-01-24 13:46 ` Tomasz Figa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D02693.1040003@samsung.com \
--to=t.figa@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mj.embd@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox