From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Hiremath, Vaibhav" <hvaibhav@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Hilman, Kevin" <khilman@ti.com>,
"Nayak, Rajendra" <rnayak@ti.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH-V4 0/4] ARM: OMAP2+: Add voltagedomain, powerdomain & PRM support for AM33XX device
Date: Wed, 18 Apr 2012 16:21:35 -0700 [thread overview]
Message-ID: <20120418232135.GU21106@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204130440390.25832@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [120413 03:46]:
> Hi Vaibhav,
>
> On Fri, 13 Apr 2012, Hiremath, Vaibhav wrote:
>
> > Yes, we are using am3517evm file for AM33XX MACHINE_INIT definition here.
> > These patches have been reviewed and accepted in the list, only thing is
> > they couldn't make it to upstream during v3.4 merge window.
> >
> > I believe Tony is going to push them for v3.5 now.
>
> Hmm, but if you modify the AM3517EVM board file to call
> am33xx_init_early(), won't that break the AM3517EVM board?
> Wouldn't a separate board file be needed for the AM33xx?
You can have multiple MACHINE_START entries in a board-*.c file
if that's what you're asking.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH-V4 0/4] ARM: OMAP2+: Add voltagedomain, powerdomain & PRM support for AM33XX device
Date: Wed, 18 Apr 2012 16:21:35 -0700 [thread overview]
Message-ID: <20120418232135.GU21106@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204130440390.25832@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [120413 03:46]:
> Hi Vaibhav,
>
> On Fri, 13 Apr 2012, Hiremath, Vaibhav wrote:
>
> > Yes, we are using am3517evm file for AM33XX MACHINE_INIT definition here.
> > These patches have been reviewed and accepted in the list, only thing is
> > they couldn't make it to upstream during v3.4 merge window.
> >
> > I believe Tony is going to push them for v3.5 now.
>
> Hmm, but if you modify the AM3517EVM board file to call
> am33xx_init_early(), won't that break the AM3517EVM board?
> Wouldn't a separate board file be needed for the AM33xx?
You can have multiple MACHINE_START entries in a board-*.c file
if that's what you're asking.
Regards,
Tony
next prev parent reply other threads:[~2012-04-18 23:21 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 16:03 [PATCH-V4 0/4] ARM: OMAP2+: Add voltagedomain, powerdomain & PRM support for AM33XX device Vaibhav Hiremath
2012-03-30 16:03 ` Vaibhav Hiremath
2012-03-30 16:03 ` [PATCH-V4 1/4] ARM: OMAP3+: am33xx: Add voltage domain data Vaibhav Hiremath
2012-03-30 16:03 ` Vaibhav Hiremath
2012-04-28 0:39 ` Paul Walmsley
2012-04-28 0:39 ` Paul Walmsley
2012-04-30 20:41 ` Kevin Hilman
2012-04-30 20:41 ` Kevin Hilman
2012-03-30 16:03 ` [PATCH-V4 2/4] ARM: OMAP3/4: omap_hwmod: Add rstst_off field to struct omap_hwmod_omap4_prcm Vaibhav Hiremath
2012-03-30 16:03 ` Vaibhav Hiremath
2012-05-29 6:31 ` Hiremath, Vaibhav
2012-05-29 6:31 ` Hiremath, Vaibhav
2012-03-30 16:03 ` [PATCH-V4 3/4] ARM: OMAP2+: powerdomain: Add offset & mask fields to struct powerdomain Vaibhav Hiremath
2012-03-30 16:03 ` Vaibhav Hiremath
2012-03-30 16:03 ` [PATCH-V4 4/4] ARM: OMAP3+: am33xx: Add powerdomain & PRM support Vaibhav Hiremath
2012-03-30 16:03 ` Vaibhav Hiremath
2012-04-27 0:49 ` Kevin Hilman
2012-04-27 0:49 ` Kevin Hilman
2012-04-27 6:37 ` Hiremath, Vaibhav
2012-04-27 6:37 ` Hiremath, Vaibhav
2012-05-04 18:43 ` Tony Lindgren
2012-05-04 18:43 ` Tony Lindgren
2012-04-27 20:44 ` Kevin Hilman
2012-04-27 20:44 ` Kevin Hilman
2012-03-30 16:22 ` [PATCH-V4 0/4] ARM: OMAP2+: Add voltagedomain, powerdomain & PRM support for AM33XX device Hiremath, Vaibhav
2012-03-30 16:22 ` Hiremath, Vaibhav
2012-04-12 8:26 ` Paul Walmsley
2012-04-12 8:26 ` Paul Walmsley
2012-04-13 10:36 ` Hiremath, Vaibhav
2012-04-13 10:36 ` Hiremath, Vaibhav
2012-04-13 10:43 ` Paul Walmsley
2012-04-13 10:43 ` Paul Walmsley
2012-04-16 7:18 ` Hiremath, Vaibhav
2012-04-16 7:18 ` Hiremath, Vaibhav
2012-04-18 23:21 ` Tony Lindgren [this message]
2012-04-18 23:21 ` Tony Lindgren
2012-04-18 23:18 ` Tony Lindgren
2012-04-18 23:18 ` Tony Lindgren
2012-04-23 18:28 ` Hiremath, Vaibhav
2012-04-23 18:28 ` Hiremath, Vaibhav
2012-04-26 18:43 ` Tony Lindgren
2012-04-26 18:43 ` Tony Lindgren
2012-04-26 18:49 ` Hiremath, Vaibhav
2012-04-26 18:49 ` Hiremath, Vaibhav
2012-04-26 19:05 ` Tony Lindgren
2012-04-26 19:05 ` Tony Lindgren
2012-04-27 8:53 ` Hiremath, Vaibhav
2012-04-27 8:53 ` Hiremath, Vaibhav
2012-05-02 9:09 ` Paul Walmsley
2012-05-02 9:09 ` Paul Walmsley
2012-05-07 10:32 ` Cousson, Benoit
2012-05-07 10:32 ` Cousson, Benoit
2012-05-07 10:44 ` Shilimkar, Santosh
2012-05-07 10:44 ` Shilimkar, Santosh
2012-05-07 13:59 ` Hiremath, Vaibhav
2012-05-07 13:59 ` Hiremath, Vaibhav
2012-05-02 9:30 ` Paul Walmsley
2012-05-02 9:30 ` Paul Walmsley
2012-05-02 9:37 ` Hiremath, Vaibhav
2012-05-02 9:37 ` Hiremath, Vaibhav
2012-05-03 14:44 ` Hiremath, Vaibhav
2012-05-03 14:44 ` Hiremath, Vaibhav
2012-04-25 13:44 ` Hiremath, Vaibhav
2012-04-25 13:44 ` Hiremath, Vaibhav
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=20120418232135.GU21106@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=hvaibhav@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@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.