From: Suman Anna <s-anna@ti.com>
To: "Nayak, Rajendra" <rnayak@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: "tony@atomide.com" <tony@atomide.com>,
"bcousson@baylibre.com" <bcousson@baylibre.com>
Subject: Re: [PATCH 3/3] ARM: OMAP2+: Add machine entry for dra72x devices
Date: Fri, 14 Mar 2014 21:21:00 -0500 [thread overview]
Message-ID: <5323B90C.80803@ti.com> (raw)
In-Reply-To: <1394788841-15112-4-git-send-email-rnayak@ti.com>
Hi Rajendra,
On 03/14/2014 04:20 AM, Nayak, Rajendra wrote:
> The only difference from the dra75x devices is the missing .smp entry.
>
> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
> ---
> arch/arm/mach-omap2/board-generic.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/arch/arm/mach-omap2/board-generic.c b/arch/arm/mach-omap2/board-generic.c
> index 8e3daa1..d803d99 100644
> --- a/arch/arm/mach-omap2/board-generic.c
> +++ b/arch/arm/mach-omap2/board-generic.c
> @@ -253,4 +253,22 @@ DT_MACHINE_START(DRA7XX_DT, "Generic DRA7XX (Flattened Device Tree)")
> .dt_compat = dra7xx_boards_compat,
> .restart = omap44xx_restart,
> MACHINE_END
> +
> +static const char *dra72_boards_compat[] __initdata = {
How about using dra72x_ instead of dra72_ and keeping it consistent
at the other places as well?
regards
Suman
> + "ti,dra72x",
> + "ti,dra7",
> + NULL,
> +};
> +
> +DT_MACHINE_START(DRA72_DT, "Generic DRA72 (Flattened Device Tree)")
> + .reserve = omap_reserve,
> + .map_io = omap5_map_io,
> + .init_early = dra7xx_init_early,
> + .init_late = dra7xx_init_late,
> + .init_irq = omap_gic_of_init,
> + .init_machine = omap_generic_init,
> + .init_time = omap5_realtime_timer_init,
> + .dt_compat = dra72_boards_compat,
> + .restart = omap44xx_restart,
> +MACHINE_END
> #endif
>
next prev parent reply other threads:[~2014-03-15 2:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 9:20 [PATCH 0/3] ARM: DRA7: Add support for DRA72x devices Rajendra Nayak
2014-03-14 9:20 ` [PATCH 1/3] Documentation: dts: OMAP: Fix typos in DRA752 device name Rajendra Nayak
2014-04-23 8:39 ` Rajendra Nayak
2014-03-14 9:20 ` [PATCH 2/3] arm: dts: Add support for DRA72x family of devices Rajendra Nayak
2014-03-14 9:20 ` [PATCH 3/3] ARM: OMAP2+: Add machine entry for dra72x devices Rajendra Nayak
2014-03-15 2:21 ` Suman Anna [this message]
2014-03-18 4:43 ` Rajendra Nayak
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=5323B90C.80803@ti.com \
--to=s-anna@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@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;
as well as URLs for NNTP newsgroup(s).