From: Rob Herring <robherring2@gmail.com>
To: Neil Zhang <zhangwm@marvell.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yu Tang <ytang5@marvell.com>, Zhou Zhu <zzhu3@marvell.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [Question] Ask for arm arch timer
Date: Wed, 16 Oct 2013 07:59:25 -0500 [thread overview]
Message-ID: <525E8DAD.60801@gmail.com> (raw)
In-Reply-To: <175CCF5F49938B4D99B2E3EF7F558EBE49FCEFF280@SC-VEXCH4.marvell.com>
[adding Will and Catalin...]
On 10/16/2013 07:39 AM, Neil Zhang wrote:
> Hi Rob,
> 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.
Can you be more specific what initialization is needed.
Rob
> commit 0583fe478a7d93be2c814b7e50d6e81c287edfe8
> Author: Rob Herring <rob.herring@calxeda.com>
> Date: Wed Apr 10 18:27:51 2013 -0500
>
> ARM: convert arm/arm64 arch timer to use CLKSRC_OF init
>
>
> Best Regards,
> Neil Zhang
>
>
next prev parent reply other threads:[~2013-10-16 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 12:39 [Question] Ask for arm arch timer Neil Zhang
2013-10-16 12:59 ` Rob Herring [this message]
2013-10-16 13:20 ` Catalin Marinas
2013-10-17 1:25 ` Neil Zhang
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=525E8DAD.60801@gmail.com \
--to=robherring2@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=ytang5@marvell.com \
--cc=zhangwm@marvell.com \
--cc=zzhu3@marvell.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