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: [PATCH] Pre 3430 patch for io.c map table cleanup
Date: Mon, 25 Jun 2007 01:57:12 -0700 [thread overview]
Message-ID: <20070625085711.GC32406@atomide.com> (raw)
In-Reply-To: <9C23CDD79DA20A479D4615857B2E2C47012A5209@dlee13.ent.ti.com>
* Syed Mohammed, Khasim <x0khasim@ti.com> [070621 06:13]:
> Hi Tony,
>
> >> +#if defined(CONFIG_ARCH_OMAP2420)
> >> + iotable_init(omap24xx_io_desc, ARRAY_SIZE(omap24xx_io_desc));
> >> + iotable_init(omap242x_io_desc, ARRAY_SIZE(omap242x_io_desc));
> >> +#elif defined(CONFIG_ARCH_OMAP2430)
> >> + iotable_init(omap24xx_io_desc, ARRAY_SIZE(omap24xx_io_desc));
> >> + iotable_init(omap243x_io_desc, ARRAY_SIZE(omap243x_io_desc));
> >> +#endif
> >> /* Normally devicemaps_init() would flush caches and tlb after
> >> * mdesc->map_io(), but we must also do it here because of the CPU
> >> * revision check below.
> >
> >You don't need the #defines here. This adds yet another artificial
> >barrier to compiling in both.
> >
> >Use cpu_is_omap34xx() et al to init them.
>
> We had discussion on this topic and I had communicated why defines are required.
Oh yeah, that's right, sorry I forgot about the cpu detection issue.
> Let me know your views on the same.
Yes, I'll apply your current patch and we'll deal with the cpu
detection issues later on.
Tony
prev parent reply other threads:[~2007-06-25 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 21:16 [PATCH] Pre 3430 patch for io.c map table cleanup Syed Mohammed, Khasim
2007-06-21 12:03 ` Tony Lindgren
2007-06-21 13:12 ` Syed Mohammed, Khasim
2007-06-25 8:57 ` Tony Lindgren [this message]
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=20070625085711.GC32406@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 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.