From: Grant Likely <grant.likely@secretlab.ca>
To: Vaibhav Hiremath <hvaibhav@ti.com>
Cc: devicetree-discuss@lists.ozlabs.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Benoit Cousson <b-cousson@ti.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 1/2] arm:omap2:board-generic: Add DT support for AM33xx devices
Date: Wed, 18 Jan 2012 13:58:28 -0700 [thread overview]
Message-ID: <20120118205828.GM4223@ponder.secretlab.ca> (raw)
In-Reply-To: <1326870839-19951-1-git-send-email-hvaibhav@ti.com>
On Wed, Jan 18, 2012 at 12:43:58PM +0530, Vaibhav Hiremath wrote:
> Although we consider am33xx device under omap34xx family of devices,
> there is indeed difference between them, for example,
>
> - Initial required mapping (->map_io)
> - Early init (->init_early)
> Here, the whole sequence/data is different than omap3,
> For example, clock/hwmod/power/voltage data.
> - clock event/source timer (name and instances)
>
> So, this patch adds seperate machine descriptor for AM33XX family
> of devices in board-generic.c file.
>
> Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> CC: Benoit Cousson <b-cousson@ti.com>
> Cc: Grant Likely <grant.likely@secretlab.ca>
> Cc: Tony Lindgren <tony@atomide.com>
> ---
> Tested it on AM335x-EVM, AM37xEVM and AM3517EVM.
>
> arch/arm/mach-omap2/board-generic.c | 19 +++++++++++++++++++
> 1 files changed, 19 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-generic.c b/arch/arm/mach-omap2/board-generic.c
> index f7b4b24..2faecc8 100644
> --- a/arch/arm/mach-omap2/board-generic.c
> +++ b/arch/arm/mach-omap2/board-generic.c
> @@ -106,6 +106,25 @@ DT_MACHINE_START(OMAP3_DT, "Generic OMAP3 (Flattened Device Tree)")
> MACHINE_END
> #endif
>
> +#if defined(CONFIG_SOC_OMAPAM33XX)
> +static const char *am33xx_boards_compat[] __initdata = {
> + "ti,am33xx",
Don't forget to add the new compatible values to
Documentation/device-tree/bindings.
> + NULL,
> +};
> +
> +DT_MACHINE_START(AM33XX_DT, "Generic AM33XX (Flattened Device Tree)")
> + .atag_offset = 0x100,
Unneeded for DT booting.
Otherwise, you can add:
Acked-by: Grant Likely <grant.likely@secretlab.ca>
> + .reserve = omap_reserve,
> + .map_io = am33xx_map_io,
> + .init_early = am33xx_init_early,
> + .init_irq = omap_init_irq,
> + .handle_irq = omap3_intc_handle_irq,
> + .init_machine = omap_generic_init,
> + .timer = &omap3_am33xx_timer,
> + .dt_compat = am33xx_boards_compat,
> +MACHINE_END
> +#endif
> +
> #if defined(CONFIG_ARCH_OMAP4)
> static const char *omap4_boards_compat[] __initdata = {
> "ti,omap4",
> --
> 1.7.0.4
>
next prev parent reply other threads:[~2012-01-18 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 7:13 [PATCH 1/2] arm:omap2:board-generic: Add DT support for AM33xx devices Vaibhav Hiremath
2012-01-18 7:13 ` [PATCH 2/2] arm/dts: Add support for TI AM335x EVM board Vaibhav Hiremath
2012-02-03 6:42 ` Hiremath, Vaibhav
2012-01-18 20:58 ` Grant Likely [this message]
[not found] ` <20120118205828.GM4223-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2012-01-19 8:10 ` [PATCH 1/2] arm:omap2:board-generic: Add DT support for AM33xx devices Hiremath, Vaibhav
2012-01-23 8:11 ` 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=20120118205828.GM4223@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).