From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
khilman@deeprootsystems.com, felipe.balbi@nokia.com,
x0095840@ti.com, linux-omap@vger.kernel.org,
ameya.palande@nokia.com, felipe.contreras@nokia.com
Subject: Re: [PATCH] OMAP3: mailbox initialization for all omap versions
Date: Thu, 1 Apr 2010 05:50:13 -0700 [thread overview]
Message-ID: <20100401125012.GR31200@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1004010629380.27004@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [100401 05:29]:
> Hi Hiroshi,
>
> On Thu, 1 Apr 2010, Hiroshi DOYU wrote:
>
> > From: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
> > Subject: Re: [PATCH] OMAP3: mailbox initialization for all omap versions
> > Date: Thu, 01 Apr 2010 13:23:36 +0300 (EEST)
> >
> > > From: ext Tony Lindgren <tony@atomide.com>
> > > Subject: Re: [PATCH] OMAP3: mailbox initialization for all omap versions
> > > Date: Thu, 1 Apr 2010 11:52:04 +0200
> > >
> > >> * Hiroshi DOYU <Hiroshi.DOYU@nokia.com> [100329 02:05]:
> > >>> From: "Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>
> > >>> Subject: Re: [PATCH] OMAP3: mailbox initialization for all omap versions
> > >>> Date: Mon, 29 Mar 2010 09:01:45 +0200
> > >>> >
> > >>> > in that case, wouldn't it be better to split that into
> > >>> > arch/arm/omap1/mbox.c arch/arm/omap2/mbox24xx.c
> > >>> > arch/arm/omap2/mbox34xx.c arch/arm/omap2/mbox44xx.c ??
> > >>> >
> > >>> > that way we don't need ifdefs on the code and we will only compile what
> > >>> > we really need.
> > >>>
> > >>> This is feasible.
> > >>> But I'm not so sure whether adding 4 new files with around only 10
> > >>> lines code is acceptable or not.
> > >>>
> > >>> Tony, any comment on the above?
> > >>>
> > >>> Basically there could be the case we need all resources if we want to
> > >>> support omap1, 2, 3 and 4 at the same time, and the appropriate one
> > >>> will be chosen at run time by CPUID. I'm not sure how mature "omap
> > >>> multi arch" support is practically, but it's better to keep it as much
> > >>> as possbile.
> > >>
> > >> I like Felipe's suggestion of adding devices2420.c, devices34xx.c,
> > >> devices44xx.c or similar. Then do the device init from those with
> > >> a arch_initcall that returns immediately if not running on the right
> > >> soc.
> > >
> > > Ok, let's procced with this. I'll post something later.
> > >
> >
> > Something like the following?
>
> Is it possible to try a hwmod conversion of this? Similar to the UART,
> HSMMC, etc. work that Kevin has queued in his pm-wip/hwmods branch:
>
> http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=shortlog;h=refs/heads/pm-wip/hwmods
>
> Otherwise this will all have to be redone when the mailbox is converted to
> use hwmod.
Sounds like a plan to me.
Tony
next prev parent reply other threads:[~2010-04-01 12:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 19:30 [PATCH] OMAP3: mailbox initialization for all omap versions Guzman Lugo, Fernando
2010-03-29 6:40 ` Hiroshi DOYU
2010-03-29 7:01 ` Felipe Balbi
2010-03-29 9:08 ` Hiroshi DOYU
2010-04-01 9:52 ` Tony Lindgren
2010-04-01 10:23 ` Hiroshi DOYU
2010-04-01 11:26 ` Hiroshi DOYU
2010-04-01 11:36 ` Felipe Balbi
2010-04-01 12:33 ` Paul Walmsley
2010-04-01 12:50 ` Tony Lindgren [this message]
2010-04-01 13:06 ` Hiroshi DOYU
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=20100401125012.GR31200@atomide.com \
--to=tony@atomide.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.balbi@nokia.com \
--cc=felipe.contreras@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=x0095840@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.