From: Vipin Kumar <vipin.kumar@st.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH resend] armv7/ltimer: Add support for local timer on armv7 cpus
Date: Tue, 18 Dec 2012 10:09:53 +0530 [thread overview]
Message-ID: <50CFF399.90700@st.com> (raw)
In-Reply-To: <20121217175026.64789202AAE@gemini.denx.de>
On 12/17/2012 11:20 PM, Wolfgang Denk wrote:
> Dear "Dennis Lan (dlan)",
>
> In message<CAF1ZMEcVWc3DNdcb7gQ60D-8Nx-MHOpkLs=eY0ph2w_Lgcozaw@mail.gmail.com> you wrote:
>>
>>> What would be the use of such timer support? Is there any code that
>>> actually needs it, and why does it need anything beyond the existing
>>> timer support we have?
>
>> I think vipin here is trying to provide a generic timer support for ARMV7
>> architecture,
>> which contains private(local) and global timer. It's general a good thing
>> which means we can maximize the code usage..
>
> Sorry, I don't get it. Why would we need separate global and local
> timers? And what exactly is "local" here - local to what?
>
> We don't need anything like that on other architectures - so why here?
>
Let me start afresh. There are two timer peripherals (called as local
and global) built into armv7 cores. The local timer is specific to each
processor while the global timer is common for all cores. These timers
may be initialized and used for timer operations in armv7 based SoCs
> "general a good thing" sounds like "nice to have", and this is usually
> something we don't really need, especially not in a boot loader.
>
This is nothing but a timer peripheral driver. The timer is a part of
armv7 core so it is kept in arch/arm/cpu/armv7
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0407i/index.html
Regards
Vipin
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2012-12-18 4:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 9:22 [U-Boot] [PATCH resend] armv7/ltimer: Add support for local timer on armv7 cpus Vipin Kumar
2012-12-12 10:01 ` Vipin Kumar
2012-12-14 9:26 ` Vipin Kumar
2012-12-14 22:20 ` Wolfgang Denk
2012-12-16 7:44 ` Dennis Lan
2012-12-17 4:24 ` Vipin Kumar
2012-12-17 17:53 ` Wolfgang Denk
2012-12-17 17:50 ` Wolfgang Denk
2012-12-18 4:39 ` Vipin Kumar [this message]
2012-12-17 10:39 ` Armando Visconti
2013-02-03 13:58 ` Albert ARIBAUD
2013-02-06 6:46 ` Vipin Kumar
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=50CFF399.90700@st.com \
--to=vipin.kumar@st.com \
--cc=u-boot@lists.denx.de \
/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