public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Syed Mohammed, Khasim" <x0khasim@ti.com>
Cc: Linux OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [RFC] io.c for OMAP3430
Date: Wed, 30 May 2007 06:41:48 -0700	[thread overview]
Message-ID: <20070530134148.GD28353@atomide.com> (raw)
In-Reply-To: <9C23CDD79DA20A479D4615857B2E2C470106287E@dlee13.ent.ti.com>

* Syed Mohammed, Khasim <x0khasim@ti.com> [070529 21:13]:
> Hi Tony,
> 
> I have incorporated your review comments for io.c. 
> 
> Please do let me know if you find any further issues.
> 
> I have incorporated other review comments from Andrew and Trilok, will regenerate and publish
> the patch set once we agree upon these (irq.c and io.c) patch set.

Well I was thinking we'd have different structs:

#ifdef CONFIG_ARCH_OMAP24XX
static struct map_desc omap24xx_io_desc[] __initdata = {
       ...
};
#endif

#ifdef CONFIG_ARCH_OMAP34XX
static struct map_desc omap34xx_io_desc[] __initdata = {
       ...
       };
#endif
       
void __init omap2_map_common_io(void)
{
 	if (cpu_is_omap24xx()) {
        	iotable_init(omap24xx_io_desc, ARRAY_SIZE(omap24xx_io_desc));
	} else if (cpu_is_omap34xx()) {
		iotable_init(omap34xx_io_desc, ARRAY_SIZE(omap34xx_io_desc));
	}
	...
}

We should actually have separate one for 2420 and 2430 too to avoid
ifdefs within the structs.

Regards,

Tony

  reply	other threads:[~2007-05-30 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30  4:12 [RFC] io.c for OMAP3430 Syed Mohammed, Khasim
2007-05-30 13:41 ` Tony Lindgren [this message]
2007-05-30 17:17   ` Syed Mohammed, Khasim
2007-05-30 22:32     ` Syed Mohammed, Khasim
2007-05-31  3:38       ` Syed Mohammed, Khasim
2007-06-04 10:02         ` Tony Lindgren

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=20070530134148.GD28353@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=x0khasim@ti.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