Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@nokia.com>
To: "Doyu Hiroshi (Nokia-D/Helsinki)" <hiroshi.doyu@nokia.com>
Cc: "Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
	"h-kanigeri2@ti.com" <h-kanigeri2@ti.com>,
	"tony@atomide.com" <tony@atomide.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"grgupta@ti.com" <grgupta@ti.com>,
	"rmk@arm.linux.org.uk" <rmk@arm.linux.org.uk>,
	"vpasam@ti.com" <vpasam@ti.com>
Subject: Re: [RFC][PATCH 2/3] ARM:OMAP4 iommu:add omap4 support in iommu
Date: Fri, 24 Jul 2009 23:08:47 +0300	[thread overview]
Message-ID: <20090724200847.GA14117@nokia.com> (raw)
In-Reply-To: <20090724.214757.112593122.Hiroshi.DOYU@nokia.com>

hi,

On Fri, Jul 24, 2009 at 08:47:57PM +0200, Doyu Hiroshi (Nokia-D/Helsinki) wrote:
> > > +static unsigned long iommu_base[] __initdata = {
> > > +	OMAP4_MMU1_BASE,
> > > +	OMAP4_MMU2_BASE,
> > > +};
> > > +
> > > +static int iommu_irq[] __initdata = {
> > > +	OMAP4_MMU1_IRQ,
> > > +	OMAP4_MMU2_IRQ,
> > > +};
> > 
> > these two looks really odd :-s
> 
> I think that the above just follows Russeell's proposal as below:
> 
> http://lists.arm.linux.org.uk/lurker/message/20090516.092036.df9420d1.en.html

I see... still looks odd though.

-- 
balbi

  reply	other threads:[~2009-07-24 20:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 17:22 [RFC][PATCH 2/3] ARM:OMAP4 iommu:add omap4 support in iommu Kanigeri, Hari
2009-07-24 18:21 ` Hiroshi DOYU
2009-07-27  0:18   ` Kanigeri, Hari
2009-07-27  6:47     ` Hiroshi DOYU
2009-07-28 15:42       ` Kanigeri, Hari
2009-07-29  6:36         ` Hiroshi DOYU
2009-07-24 18:27 ` Felipe Balbi
2009-07-24 18:47   ` Hiroshi DOYU
2009-07-24 20:08     ` Felipe Balbi [this message]
2009-07-26 18:16   ` Kanigeri, Hari
2009-07-25  9:02 ` Shilimkar, Santosh
2009-07-25 23:17   ` Kanigeri, Hari

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=20090724200847.GA14117@nokia.com \
    --to=felipe.balbi@nokia.com \
    --cc=grgupta@ti.com \
    --cc=h-kanigeri2@ti.com \
    --cc=hiroshi.doyu@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=tony@atomide.com \
    --cc=vpasam@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