From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] omap3: Optimize detection of cpu revision
Date: Tue, 15 Dec 2009 11:14:20 -0600 [thread overview]
Message-ID: <4B27C3EC.1050505@windriver.com> (raw)
In-Reply-To: <1260883106-4588-1-git-send-email-premi@ti.com>
Sanjeev Premi wrote:
> Each call to get_cpu_rev() leads to repetitive
> execution of code to detect the cpu revision.
>
> This patchset ensures that mechanism to detect
> revision is not executed each time; instead a
> stored value is returned.
>
> Since, revision info is needed in s_init(),
> the function to identify cpu revision needs
> to be called twice. At the moment, it is
> necessary/ unavoidable.
>
Is there some other reason to read this register only once?
This function is not used frequently and i do not
think the complexity of optimizing is necessary.
Tom
next prev parent reply other threads:[~2009-12-15 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 13:18 [U-Boot] [PATCH 0/2] omap3: Optimize detection of cpu revision Sanjeev Premi
2009-12-15 13:18 ` [U-Boot] [PATCH 1/2] omap3: Identify the CPU in arch_cpu_init() Sanjeev Premi
2009-12-15 13:18 ` [U-Boot] [PATCH 2/2] omap3: Identify cpu in s_init() Sanjeev Premi
2009-12-15 17:14 ` Tom [this message]
2009-12-15 18:44 ` [U-Boot] [PATCH 0/2] omap3: Optimize detection of cpu revision Premi, Sanjeev
2009-12-16 22:15 ` Wolfgang Denk
2010-01-07 14:56 ` Premi, Sanjeev
2010-01-07 15:32 ` Paulraj, Sandeep
2010-01-08 10:41 ` Premi, Sanjeev
2010-01-11 17:15 ` Premi, Sanjeev
2010-01-12 13:44 ` Tom
2010-01-17 21:32 ` Wolfgang Denk
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=4B27C3EC.1050505@windriver.com \
--to=tom.rix@windriver.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