lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 09 Jan 2014 13:52:46 +0100
From:	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
To:	Mj Embd <mj.embd@...il.com>
Cc:	linaro-kernel <linaro-kernel@...ts.linaro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-samsung-soc@...r.kernel.org
Subject: Re: Arndale Timer Interrupt Question


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.
> 
> 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ