From: Tony Lindgren <tony@atomide.com>
To: Vaibhav Hiremath <hvaibhav@ti.com>
Cc: linux-omap@vger.kernel.org, khilman@ti.com
Subject: Re: [PATCH-V3 2/2] arm:omap: cleanup & split omap2/3/4_check_revision function
Date: Mon, 19 Dec 2011 15:51:11 -0800 [thread overview]
Message-ID: <20111219235111.GX6464@atomide.com> (raw)
In-Reply-To: <1324290015-12679-3-git-send-email-hvaibhav@ti.com>
* Vaibhav Hiremath <hvaibhav@ti.com> [111219 01:48]:
> This patch doesn't change functionality or behavior of the code
> execution; it barely cleans up the code and splits into SoC
> specific implementation for Rev ID and feature detection.
Thanks, looks good now and allows further clean-up later on.
I'll apply these into soc-part2 branch.
> @@ -495,37 +498,6 @@ static void __init omap4_check_revision(void)
> }
>
> /*
> - * Try to detect the exact revision of the omap we're running on
> - */
> -void __init omap2_check_revision(void)
> -{
> - /*
> - * At this point we have an idea about the processor revision set
> - * earlier with omap2_set_globals_tap().
> - */
> - if (cpu_is_omap24xx()) {
> - omap24xx_check_revision();
> - } else if (cpu_is_omap34xx()) {
> - omap3_check_revision();
> -
> - /* TI81XX doesn't have feature register */
> - if (!cpu_is_ti81xx())
> - omap3_check_features();
> - else
> - ti81xx_check_features();
> -
> - omap3_cpuinfo();
> - return;
> - } else if (cpu_is_omap44xx()) {
> - omap4_check_revision();
> - omap4_check_features();
> - return;
> - } else {
> - pr_err("OMAP revision unknown, please fix!\n");
> - }
> -}
> -
Nice that we can get rid of this function now :)
Tony
next prev parent reply other threads:[~2011-12-19 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 10:20 [PATCH-V3 0/2] arm:omap:cleanup & split omap2/3/4_check_revision function Vaibhav Hiremath
2011-12-19 10:20 ` [PATCH-V3 1/2] arm:omap: Make cpu_rev static global variable Vaibhav Hiremath
2011-12-19 10:20 ` [PATCH-V3 2/2] arm:omap: cleanup & split omap2/3/4_check_revision function Vaibhav Hiremath
2011-12-19 23:51 ` Tony Lindgren [this message]
2011-12-20 4:38 ` Hiremath, Vaibhav
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=20111219235111.GX6464@atomide.com \
--to=tony@atomide.com \
--cc=hvaibhav@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.