From: Kevin Hilman <khilman@deeprootsystems.com>
To: hvaibhav@ti.com
Cc: linux-omap@vger.kernel.org, tony@atomide.com,
Sriramakrishnan <srk@ti.com>
Subject: Re: [PATCH 2/3] AM35xx: Introduce am35xx.h file
Date: Wed, 06 Jan 2010 15:50:21 -0800 [thread overview]
Message-ID: <873a2iaj42.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1262613116-20185-3-git-send-email-hvaibhav@ti.com> (hvaibhav@ti.com's message of "Mon\, 4 Jan 2010 19\:21\:55 +0530")
hvaibhav@ti.com writes:
> From: Vaibhav Hiremath <hvaibhav@ti.com>
>
> Add base address definations for new AM35xx IPSS modules, like
> VPFE, USBOTG, CPGMAC.
>
> Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> Signed-off-by: Sriramakrishnan <srk@ti.com>
> ---
> arch/arm/plat-omap/include/plat/am35xx.h | 25 +++++++++++++++++++++++++
> arch/arm/plat-omap/include/plat/hardware.h | 1 +
> 2 files changed, 26 insertions(+), 0 deletions(-)
> create mode 100644 arch/arm/plat-omap/include/plat/am35xx.h
>
> diff --git a/arch/arm/plat-omap/include/plat/am35xx.h b/arch/arm/plat-omap/include/plat/am35xx.h
> new file mode 100644
> index 0000000..d41bd61
> --- /dev/null
> +++ b/arch/arm/plat-omap/include/plat/am35xx.h
> @@ -0,0 +1,25 @@
> +/*:
> + * Address mappings and base address for AM35XX specific interconnects
> + * and peripherals.
> + *
> + * Copyright (C) 2009 Texas Instruments
> + *
> + * Author: Sriramakrishnan <srk@ti.com>
> + * Vaibhav Hiremath <hvaibhav@ti.com>
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free Software Foundation.
> + */
> +#ifndef __ASM_ARCH_AM35XX_H
> +#define __ASM_ARCH_AM35XX_H
> +
> +/*
> + * Base addresses
> + */
> +#define AM35XX_IPSS_EMAC_BASE 0x5C000000
> +#define AM35XX_IPSS_USBOTGSS_BASE 0x5C040000
> +#define AM35XX_IPSS_HECC_BASE 0x5C050000
> +#define AM35XX_IPSS_VPFE_BASE 0x5C060000
I think this secont needs ome more comments. In the 34xx TRM memory
map, this region is shown as IVA2, so folks familiar with 34xx might
be confused.
That being said, is there any reason to have these in a global header
file? Nobody should use these except SoC/board init code, so these
should probably stay in arch/arm/mach-omap2 in AM35x specific code.
I know this is different than what is done for 34xx, but we don't need
the 34xx defines to be global anymore either.
Kevin
> +#endif /* __ASM_ARCH_AM35XX_H */
> diff --git a/arch/arm/plat-omap/include/plat/hardware.h b/arch/arm/plat-omap/include/plat/hardware.h
> index d5b26ad..930c3f9 100644
> --- a/arch/arm/plat-omap/include/plat/hardware.h
> +++ b/arch/arm/plat-omap/include/plat/hardware.h
> @@ -285,6 +285,7 @@
> #include <plat/omap16xx.h>
> #include <plat/omap24xx.h>
> #include <plat/omap34xx.h>
> +#include <plat/am35xx.h>
> #include <plat/omap44xx.h>
>
> #endif /* __ASM_ARCH_OMAP_HARDWARE_H */
> --
> 1.6.2.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-06 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 13:51 [PATCH 2/3] AM35xx: Introduce am35xx.h file hvaibhav
2010-01-06 23:50 ` Kevin Hilman [this message]
2010-01-07 17:38 ` Hiremath, Vaibhav
2010-01-07 19:14 ` Kevin Hilman
2010-01-07 19:18 ` 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=873a2iaj42.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=hvaibhav@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=srk@ti.com \
--cc=tony@atomide.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