linux-kernel - Re: [Question] Ask for arm arch timer

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]

Message-ID: <20131016132042.GC4196@arm.com>
Date:	Wed, 16 Oct 2013 14:20:43 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Rob Herring <robherring2@...il.com>
Cc:	Neil Zhang <zhangwm@...vell.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Yu Tang <ytang5@...vell.com>, Zhou Zhu <zzhu3@...vell.com>,
	Will Deacon <Will.Deacon@....com>
Subject: Re: [Question] Ask for arm arch timer

On Wed, Oct 16, 2013 at 01:59:25PM +0100, Rob Herring wrote:
> On 10/16/2013 07:39 AM, Neil Zhang wrote:
> > I saw your following patch called clocksource_of_init() directly in
> > time_init() for arm64.
> > My question is that what should we do if there are some Soc special
> > work need to be done before arch timer can be used?
> > Thanks in advance.
> 
> If the timer itself is different, then you should have a different DT
> compatible string which you can use to trigger additional initialization.
> 
> Integration level initialization like enabling clocks would need
> something different as no machine descriptors exist for arm64.
> 
> Another option would be do the setup in secure world or the bootloader.

The generic timer should indeed be initialised in the firmware
(bootloader may not be suitable if initialisation needs to happen on
each CPU). Linux doesn't need to do other things than reading the
frequency, programming the interrupts, counters (but definitely not
SoC-specific initialisation).

> Can you be more specific what initialization is needed.

I'm interested in this as well.

-- 
Catalin
--
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/