linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajendra Nayak <rnayak@ti.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: tony@atomide.com, paul@pwsan.com, khilman@linaro.org,
	benoit.cousson@gmail.com, r.sricharan@ti.com, ambresh@ti.com,
	Rajendra Nayak <rnayak@ti.com>
Subject: [PATCH 3/8] ARM: DRA7: hwmod: Reuse the soc_ops used for OMAP4/5
Date: Tue, 9 Jul 2013 12:57:48 +0530	[thread overview]
Message-ID: <1373354873-12359-4-git-send-email-rnayak@ti.com> (raw)
In-Reply-To: <1373354873-12359-1-git-send-email-rnayak@ti.com>

The soc_ops for dra7xx devices can be completed reused
from the ones used for omap4 and omap5 devices.

Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Signed-off-by: R Sricharan <r.sricharan@ti.com>
---
 arch/arm/mach-omap2/omap_hwmod.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c
index 7341eff..f6eb29b 100644
--- a/arch/arm/mach-omap2/omap_hwmod.c
+++ b/arch/arm/mach-omap2/omap_hwmod.c
@@ -4113,7 +4113,7 @@ void __init omap_hwmod_init(void)
 		soc_ops.assert_hardreset = _omap2_assert_hardreset;
 		soc_ops.deassert_hardreset = _omap2_deassert_hardreset;
 		soc_ops.is_hardreset_asserted = _omap2_is_hardreset_asserted;
-	} else if (cpu_is_omap44xx() || soc_is_omap54xx()) {
+	} else if (cpu_is_omap44xx() || soc_is_omap54xx() || soc_is_dra7xx()) {
 		soc_ops.enable_module = _omap4_enable_module;
 		soc_ops.disable_module = _omap4_disable_module;
 		soc_ops.wait_target_ready = _omap4_wait_target_ready;
-- 
1.7.9.5


  parent reply	other threads:[~2013-07-09  7:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09  7:27 [PATCH 0/8] DRA7xx core support Rajendra Nayak
2013-07-09  7:27 ` [PATCH 1/8] ARM: DRA7: id: Add cpu detection support for DRA7xx based SoCs' Rajendra Nayak
2013-07-09  7:27 ` [PATCH 2/8] ARM: DRA7: Update SRAM details Rajendra Nayak
2013-07-09  8:36   ` Tony Lindgren
2013-07-09  7:27 ` Rajendra Nayak [this message]
2013-07-09  7:27 ` [PATCH 4/8] ARM: DRA7: Reuse all of PRCM and MPUSS SMP infra Rajendra Nayak
2013-07-09  7:27 ` [PATCH 5/8] ARM: DRA7: Reuse io tables and add a new .init_early Rajendra Nayak
2013-07-09  7:27 ` [PATCH 6/8] ARM: DRA7: Resue the clocksource, clockevent support Rajendra Nayak
2013-07-09  7:27 ` [PATCH 7/8] ARM: DRA7: board-generic: Add basic DT support Rajendra Nayak
2013-07-09  7:27 ` [PATCH 8/8] ARM: DRA7: Kconfig: Increase the default gpio count Rajendra Nayak
2013-07-14 12:07   ` Kevin Hilman
2013-07-16  5:21     ` Sricharan R

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=1373354873-12359-4-git-send-email-rnayak@ti.com \
    --to=rnayak@ti.com \
    --cc=ambresh@ti.com \
    --cc=benoit.cousson@gmail.com \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=r.sricharan@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).