From: Tony Lindgren <tony@atomide.com>
To: Hemant Pedanekar <hemantp@ti.com>
Cc: linux-omap@vger.kernel.org, khilman@deeprootsystems.com
Subject: Re: [PATCH v2 3/6] TI816X: Update common OMAP machine specific sources
Date: Thu, 16 Sep 2010 15:25:00 -0700 [thread overview]
Message-ID: <20100916222459.GQ29610@atomide.com> (raw)
In-Reply-To: <1281546664-11477-1-git-send-email-hemantp@ti.com>
* Hemant Pedanekar <hemantp@ti.com> [100811 10:03]:
> This patch updates the common machine spcific source files with support for
> TI816X.
>
> Note that the nr_irqs is overridden in INTC driver since the number of IRQs on
> TI816X are different (128) comapared to other OMAPs (96).
<snip>
> --- a/arch/arm/mach-omap2/id.c
> +++ b/arch/arm/mach-omap2/id.c
> @@ -419,6 +441,9 @@ void __init omap2_check_revision(void)
> } else if (cpu_is_omap44xx()) {
> omap4_check_revision();
> return;
> + } else if (cpu_is_ti816x()) {
> + ti816x_check_revision();
> + return;
> } else {
> pr_err("OMAP revision unknown, please fix!\n");
> }
This does not look right, at this point you should just know
the processor class set by the set_globals call.
Please take a look at plat-omap/common.c and add an entry for
omap2_set_globals_ti816x. This gets called very early from the board-*.c
file, so you can initialize things.
Note that by default we are building in support for omap2, 3 and 4
and support for all the boards too. This allows booting them
with the same kernel binary for developers and distros.
In general, you might want to see how we added support for omap36xx.
TI816X seems to be very close to omap3 with some extra registers, and
I'm not at all convinced that we even need to set it up as a separate
processor. Basically adding the set_globals + doing the more
accurate detection in id.c should do the trick.
Regards,
Tony
next prev parent reply other threads:[~2010-09-16 22:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 17:11 [PATCH v2 3/6] TI816X: Update common OMAP machine specific sources Hemant Pedanekar
2010-09-16 22:25 ` Tony Lindgren [this message]
2010-10-22 18:07 ` Pedanekar, Hemant
2010-11-05 20:59 ` Tony Lindgren
2010-11-29 17:17 ` Pedanekar, Hemant
2010-11-29 19:29 ` Tony Lindgren
2010-12-01 1:46 ` Pedanekar, Hemant
2010-12-06 16:53 ` Tony Lindgren
2010-12-11 0:58 ` Pedanekar, Hemant
2010-12-11 1:51 ` Tony Lindgren
2010-12-11 1:53 ` Pedanekar, Hemant
2010-12-04 0:20 ` Pedanekar, Hemant
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=20100916222459.GQ29610@atomide.com \
--to=tony@atomide.com \
--cc=hemantp@ti.com \
--cc=khilman@deeprootsystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox