linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sricharan R <r.sricharan@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>, linux-omap@vger.kernel.org
Cc: Felipe Balbi <balbi@ti.com>, Benoit Cousson <b-cousson@ti.com>
Subject: RE: [PATCH 1/6] omap3: hwmod_data: Add l3 error log data to hwmod database.
Date: Wed, 23 Feb 2011 13:44:50 +0530	[thread overview]
Message-ID: <c3f5b25dde2b0ab9536aba0aece25ac6@mail.gmail.com> (raw)
In-Reply-To: <1298295990-1070-2-git-send-email-santosh.shilimkar@ti.com>

>-----Original Message-----
>From: Santosh Shilimkar [mailto:santosh.shilimkar@ti.com]
>Sent: Monday, February 21, 2011 7:16 PM
>To: linux-omap@vger.kernel.org
>Cc: balbi@ti.com; b-cousson@ti.com; r.sricharan@ti.com; Santosh Shilimkar
>Subject: [PATCH 1/6] omap3: hwmod_data: Add l3 error log data to hwmod
>database.
>
>From: sricharan <r.sricharan@ti.com>
>
>Add the error log registers, irqs of the l3 interconnect to the
>hwmod data. The hwmod changes are aligned with Benoit Cousson.
>
Changed as per your comments for omap3.

---------------
[PATCH v2 1/6] omap3: hwmod_data: Add address space and irq in L3 hwmod.

Add the address spaces, irqs of the l3 interconnect to the
hwmod data. The hwmod changes are aligned with Benoit Cousson.

Signed-off-by: sricharan <r.sricharan@ti.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Tested-by: sricharan <r.sricharan@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>
---
changed the subject line and changelog.

 arch/arm/mach-omap2/omap_hwmod_3xxx_data.c |   22 ++++++++++++++++++++--
 arch/arm/plat-omap/include/plat/irqs.h     |    2 ++
 2 files changed, 22 insertions(+), 2 deletions(-)

diff --git a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
b/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
index 8d81813..9a8f799 100644
--- a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
+++ b/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
@@ -72,10 +72,26 @@ static struct omap_hwmod_ocp_if
omap3xxx_l3_main__l4_per = {
 	.user	= OCP_USER_MPU | OCP_USER_SDMA,
 };

+/* L3 taret configuration and error log registers */
+static struct omap_hwmod_irq_info omap3xxx_l3_targ_irqs[] = {
+	{ .irq = INT_34XX_L3_DBG_IRQ },
+	{ .irq = INT_34XX_L3_APP_IRQ },
+};
+
+static struct omap_hwmod_addr_space omap3xxx_l3_targ_addrs[] = {
+	{
+		.pa_start       = 0x68000000,
+		.pa_end         = 0x68100000,
+		.flags          = ADDR_TYPE_RT,
+	},
+};
+
 /* MPU -> L3 interface */
 static struct omap_hwmod_ocp_if omap3xxx_mpu__l3_main = {
-	.master = &omap3xxx_mpu_hwmod,
-	.slave	= &omap3xxx_l3_main_hwmod,
+	.master   = &omap3xxx_mpu_hwmod,
+	.slave    = &omap3xxx_l3_main_hwmod,
+	.addr     = omap3xxx_l3_targ_addrs,
+	.addr_cnt = ARRAY_SIZE(omap3xxx_l3_targ_addrs),
 	.user	= OCP_USER_MPU,
 };

@@ -94,6 +110,8 @@ static struct omap_hwmod_ocp_if
*omap3xxx_l3_main_masters[] = {
 static struct omap_hwmod omap3xxx_l3_main_hwmod = {
 	.name		= "l3_main",
 	.class		= &l3_hwmod_class,
+	.mpu_irqs       = omap3xxx_l3_targ_irqs,
+	.mpu_irqs_cnt   = ARRAY_SIZE(omap3xxx_l3_targ_irqs),
 	.masters	= omap3xxx_l3_main_masters,
 	.masters_cnt	= ARRAY_SIZE(omap3xxx_l3_main_masters),
 	.slaves		= omap3xxx_l3_main_slaves,
diff --git a/arch/arm/plat-omap/include/plat/irqs.h
b/arch/arm/plat-omap/include/plat/irqs.h
index 2910de9..e614de1 100644
--- a/arch/arm/plat-omap/include/plat/irqs.h
+++ b/arch/arm/plat-omap/include/plat/irqs.h
@@ -315,6 +315,8 @@
 #define INT_34XX_SSM_ABORT_IRQ	6
 #define INT_34XX_SYS_NIRQ	7
 #define INT_34XX_D2D_FW_IRQ	8
+#define INT_34XX_L3_DBG_IRQ     9
+#define INT_34XX_L3_APP_IRQ     10
 #define INT_34XX_PRCM_MPU_IRQ	11
 #define INT_34XX_MCBSP1_IRQ	16
 #define INT_34XX_MCBSP2_IRQ	17
-- 
1.7.0.4

Thanks,
 Sricharan

  parent reply	other threads:[~2011-02-23  8:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 13:46 [PATCH 0/6] omap3/4: Add l3-interconnect error logging support Santosh Shilimkar
2011-02-21 13:46 ` [PATCH 1/6] omap3: hwmod_data: Add l3 error log data to hwmod database Santosh Shilimkar
2011-02-23  8:03   ` Sricharan R
2011-02-23  8:14   ` Sricharan R [this message]
2011-02-21 13:46 ` [PATCH 2/6] omap3: Initialise the l3 device with the hwmod data Santosh Shilimkar
2011-02-21 13:46 ` [PATCH 3/6] omap3: l3: Introduce l3-interconnect error handling driver Santosh Shilimkar
2011-02-21 13:46 ` [PATCH 4/6] omap4: hwmod_data: Add l3 errorlog data to hwmod database Santosh Shilimkar
2011-02-21 14:39   ` Cousson, Benoit
2011-02-23  5:38     ` Sricharan R
2011-02-23  8:04     ` Sricharan R
2011-03-04 21:34       ` Cousson, Benoit
2011-03-05  7:51         ` Santosh Shilimkar
2011-02-23  8:14     ` Sricharan R
2011-02-21 13:46 ` [PATCH 5/6] omap4: Initialise the l3 device with the hwmod data Santosh Shilimkar
2011-02-21 18:10   ` Cousson, Benoit
2011-02-21 19:03     ` Santosh Shilimkar
2011-03-03 18:31       ` Tony Lindgren
2011-03-04  6:20         ` Santosh Shilimkar
2011-03-04 18:08           ` Tony Lindgren
2011-03-05  7:46             ` Santosh Shilimkar
2011-03-07 10:22       ` Cousson, Benoit
2011-03-07 11:19         ` Santosh Shilimkar
2011-03-07 11:25           ` Santosh Shilimkar
2011-02-21 13:46 ` [PATCH 6/6] omap4: l3: Introduce l3-interconnect error handling driver Santosh Shilimkar

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=c3f5b25dde2b0ab9536aba0aece25ac6@mail.gmail.com \
    --to=r.sricharan@ti.com \
    --cc=b-cousson@ti.com \
    --cc=balbi@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@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).