From: Tony Lindgren <tony@atomide.com>
To: Vaibhav Hiremath <hvaibhav@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Kevin Hilman <khilman@ti.com>, Paul Walmsley <paul@pwsan.com>
Subject: Re: [RESEND PATCH] ARM: OMAP2+: am33xx: Make am33xx as a separate class
Date: Thu, 5 Jul 2012 08:27:43 -0700 [thread overview]
Message-ID: <20120705152743.GG1122@atomide.com> (raw)
In-Reply-To: <20120704081546.GR1122@atomide.com>
* Tony Lindgren <tony@atomide.com> [120704 01:20]:
> * Tony Lindgren <tony@atomide.com> [120704 00:29]:
> > * Vaibhav Hiremath <hvaibhav@ti.com> [120703 06:12]:
> > > Initially, we decided to make am33xx family of device to fall
> > > under omap3 class (cpu_is_omap34xx() = true), since it carries
> > > Cortex-A8 core. But while adding complete baseport support
> > > (like, clock, power and hwmod) support, it is observed that,
> > > we are creating more and more problems by treating am33xx device
> > > as omap3 family, as nothing matches between them
> > > (except cortex-A8 mpu).
> > >
> > > So, after long discussion we have came to the conclusion that,
> > > we should not consider am33xx device as omap3 family, instead
> > > create separate class (SOC_AM33XX) under OMAP2PLUS.
> > > This means, for am33xx device, cpu_is_omap34xx() will return false,
> > > and only cpu_is_am33xx() will be true.
> >
> > Thanks applying both.
>
> I believe all your patches are now applied. I've pushed them out
> into devel-am33xx-part2 branch. Can you please check and send
> additional patches as needed?
I ended up moving some patches into cleanup-part2 branch as omap5
patches also need those. So the new branch for am33xx is called
devel-am33xx-data at commit 79ab2664. The old devel-am33xx-part2
branch should be ignored now.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] ARM: OMAP2+: am33xx: Make am33xx as a separate class
Date: Thu, 5 Jul 2012 08:27:43 -0700 [thread overview]
Message-ID: <20120705152743.GG1122@atomide.com> (raw)
In-Reply-To: <20120704081546.GR1122@atomide.com>
* Tony Lindgren <tony@atomide.com> [120704 01:20]:
> * Tony Lindgren <tony@atomide.com> [120704 00:29]:
> > * Vaibhav Hiremath <hvaibhav@ti.com> [120703 06:12]:
> > > Initially, we decided to make am33xx family of device to fall
> > > under omap3 class (cpu_is_omap34xx() = true), since it carries
> > > Cortex-A8 core. But while adding complete baseport support
> > > (like, clock, power and hwmod) support, it is observed that,
> > > we are creating more and more problems by treating am33xx device
> > > as omap3 family, as nothing matches between them
> > > (except cortex-A8 mpu).
> > >
> > > So, after long discussion we have came to the conclusion that,
> > > we should not consider am33xx device as omap3 family, instead
> > > create separate class (SOC_AM33XX) under OMAP2PLUS.
> > > This means, for am33xx device, cpu_is_omap34xx() will return false,
> > > and only cpu_is_am33xx() will be true.
> >
> > Thanks applying both.
>
> I believe all your patches are now applied. I've pushed them out
> into devel-am33xx-part2 branch. Can you please check and send
> additional patches as needed?
I ended up moving some patches into cleanup-part2 branch as omap5
patches also need those. So the new branch for am33xx is called
devel-am33xx-data at commit 79ab2664. The old devel-am33xx-part2
branch should be ignored now.
Regards,
Tony
next prev parent reply other threads:[~2012-07-05 15:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 13:00 [RESEND PATCH] ARM: OMAP2+: am33xx: Change cpu_is_am33xx to soc_is_am33xx Vaibhav Hiremath
2012-07-03 13:00 ` Vaibhav Hiremath
2012-07-03 13:00 ` [RESEND PATCH] ARM: OMAP2+: am33xx: Make am33xx as a separate class Vaibhav Hiremath
2012-07-03 13:00 ` Vaibhav Hiremath
2012-07-04 7:24 ` Tony Lindgren
2012-07-04 7:24 ` Tony Lindgren
2012-07-04 8:15 ` Tony Lindgren
2012-07-04 8:15 ` Tony Lindgren
2012-07-05 15:27 ` Tony Lindgren [this message]
2012-07-05 15:27 ` Tony Lindgren
2012-07-10 8:38 ` Hiremath, Vaibhav
2012-07-10 8:38 ` Hiremath, Vaibhav
2012-07-10 8:43 ` Tony Lindgren
2012-07-10 8:43 ` Tony Lindgren
2012-07-04 10:26 ` Hiremath, Vaibhav
2012-07-04 10:26 ` 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=20120705152743.GG1122@atomide.com \
--to=tony@atomide.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 \
/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.