From: Tony Lindgren <tony@atomide.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: linux-omap@vger.kernel.org, Rajendra Nayak <rnayak@ti.com>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 3/6] OMAP4: hwmod: Enable omap_device build for OMAP4
Date: Fri, 7 May 2010 13:33:08 -0700 [thread overview]
Message-ID: <20100507203308.GO387@atomide.com> (raw)
In-Reply-To: <1273248424-15943-4-git-send-email-b-cousson@ti.com>
* Benoit Cousson <b-cousson@ti.com> [100507 09:03]:
> From: Rajendra Nayak <rnayak@ti.com>
>
> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
> Signed-off-by: Benoit Cousson <b-cousson@ti.com>
> Cc: Paul Walmsley <paul@pwsan.com>
> ---
> arch/arm/plat-omap/Makefile | 1 +
> arch/arm/plat-omap/omap_device.c | 12 ++++++++++++
> 2 files changed, 13 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/plat-omap/Makefile b/arch/arm/plat-omap/Makefile
> index 98f0191..9405831 100644
> --- a/arch/arm/plat-omap/Makefile
> +++ b/arch/arm/plat-omap/Makefile
> @@ -15,6 +15,7 @@ obj-$(CONFIG_ARCH_OMAP16XX) += ocpi.o
> # omap_device support (OMAP2+ only at the moment)
> obj-$(CONFIG_ARCH_OMAP2) += omap_device.o
> obj-$(CONFIG_ARCH_OMAP3) += omap_device.o
> +obj-$(CONFIG_ARCH_OMAP4) += omap_device.o
>
> obj-$(CONFIG_OMAP_MCBSP) += mcbsp.o
> obj-$(CONFIG_OMAP_IOMMU) += iommu.o iovmm.o
> diff --git a/arch/arm/plat-omap/omap_device.c b/arch/arm/plat-omap/omap_device.c
> index 0f51974..b6144ff 100644
> --- a/arch/arm/plat-omap/omap_device.c
> +++ b/arch/arm/plat-omap/omap_device.c
> @@ -90,6 +90,18 @@
> #define USE_WAKEUP_LAT 0
> #define IGNORE_WAKEUP_LAT 1
>
> +/* XXX this should be moved into a separate file */
> +#if defined(CONFIG_ARCH_OMAP2420)
> +# define OMAP_32KSYNCT_BASE 0x48004000
> +#elif defined(CONFIG_ARCH_OMAP2430)
> +# define OMAP_32KSYNCT_BASE 0x49020000
> +#elif defined(CONFIG_ARCH_OMAP3430)
> +# define OMAP_32KSYNCT_BASE 0x48320000
> +#elif defined(CONFIG_ARCH_OMAP4)
> +# define OMAP_32KSYNCT_BASE 0x4a304000
> +#else
> +# error Unknown OMAP device
> +#endif
>
> #define OMAP_DEVICE_MAGIC 0xf00dcafe
This OMAP_32KSYNCT_BASE stuff will break multi-omap as it's defined
in a different way for for various omaps.
Also, OMAP_32KSYNCT_BASE define should no longer be needed at all,
I think all issues like this have been fixed over past year or so.
Can you please check your patches, if you're OMAP_32KSYNCT_BASE
in your other patches, they should be fixed.
Regards,
Tony
next prev parent reply other threads:[~2010-05-07 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 16:06 [PATCH 0/6] OMAP: hwmod: Full data set for OMAP4430 ES1.0 Benoit Cousson
2010-05-07 16:06 ` [PATCH 1/6] OMAP4: hwmod: Add partial hwmod support " Benoit Cousson
2010-05-07 16:07 ` [PATCH 2/6] OMAP4: hwmod: Enable omap_hwmod build for OMAP4 Benoit Cousson
2010-05-07 16:07 ` [PATCH 3/6] OMAP4: hwmod: Enable omap_device " Benoit Cousson
2010-05-07 16:10 ` Benoit Cousson
2010-05-07 20:33 ` Tony Lindgren [this message]
2010-05-10 10:00 ` Benoit Cousson
2010-05-07 16:07 ` [PATCH 4/6] OMAP: hwmod: Temporary disable dependency Benoit Cousson
2010-05-20 17:25 ` Kevin Hilman
2010-05-07 16:07 ` [PATCH 5/6] OMAP4: hwmod: Add remaining hwmod support for OMAP4430 ES1.0 Benoit Cousson
2010-05-07 16:07 ` [PATCH 6/6] OMAP: hwmod: Temp fixes to get hwmod registers work Benoit Cousson
2010-05-20 17:26 ` Kevin Hilman
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=20100507203308.GO387@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).