Re: [PATCH 1/9] ARM: OMAP4+: Use common scratchpad SAR RAM offsets for all architectures
On Thursday 28 March 2013 02:22 AM, Santosh Shilimkar wrote: On Thursday 28 March 2013 02:19 AM, Tony Lindgren wrote: * Santosh Shilimkar santosh.shilim...@ti.com [130327 13:52]: On Thursday 28 March 2013 12:11 AM, Kevin Hilman wrote: Santosh Shilimkar santosh.shilim...@ti.com writes: From: Tero Kristo t-kri...@ti.com Simplifies code and also allows the re-use as is on OMAP5 devices. nit: changelog here is rather weak. It claims simplifies code but it's not obvious from the patch how changing a few #defines does that. I agree. Basically the offset are chosen such a way that they can work on OMAP4 and OMAP5 instead of having two separate sets. Will expand the changelog to make it clear. You might want to mention also that the offsets are only used by the kernel to save and restore registers from so people don't think those are hardare registers and that the patch might break some things. Yeah. Will mention that. For record, patch with updated changelog end of email. Regards, Santosh From f98d5fe8079cc4830e4ce22585055822119da5c8 Mon Sep 17 00:00:00 2001 From: Tero Kristo t-kri...@ti.com Date: Wed, 6 Feb 2013 18:39:20 +0530 Subject: [PATCH v2 1/9] ARM: OMAP4+: Use common scratchpad SAR RAM offsets for all architectures Choose the common scratch pad offsets, so that same offsets can work for OMAP4 and OMAP5 devices. It simplifies code and also allows the re-use as is on OMAP5 devices. Note that these offsets are used by low power code for various power state management. They are not hardware register offsets. Signed-off-by: Tero Kristo t-kri...@ti.com Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com --- arch/arm/mach-omap2/omap4-sar-layout.h | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/arch/arm/mach-omap2/omap4-sar-layout.h b/arch/arm/mach-omap2/omap4-sar-layout.h index e170fe8..6822d0a 100644 --- a/arch/arm/mach-omap2/omap4-sar-layout.h +++ b/arch/arm/mach-omap2/omap4-sar-layout.h @@ -20,13 +20,13 @@ #define SAR_BANK4_OFFSET 0x3000 /* Scratch pad memory offsets from SAR_BANK1 */ -#define SCU_OFFSET00xd00 -#define SCU_OFFSET10xd04 -#define OMAP_TYPE_OFFSET 0xd10 -#define L2X0_SAVE_OFFSET0 0xd14 -#define L2X0_SAVE_OFFSET1 0xd18 -#define L2X0_AUXCTRL_OFFSET0xd1c -#define L2X0_PREFETCH_CTRL_OFFSET 0xd20 +#define SCU_OFFSET00xfe4 +#define SCU_OFFSET10xfe8 +#define OMAP_TYPE_OFFSET 0xfec +#define L2X0_SAVE_OFFSET0 0xff0 +#define L2X0_SAVE_OFFSET1 0xff4 +#define L2X0_AUXCTRL_OFFSET0xff8 +#define L2X0_PREFETCH_CTRL_OFFSET 0xffc /* CPUx Wakeup Non-Secure Physical Address offsets in SAR_BANK3 */ #define CPU0_WAKEUP_NS_PA_ADDR_OFFSET 0xa04 -- 1.7.9.5 -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/9] ARM: OMAP4+: Use common scratchpad SAR RAM offsets for all architectures
Santosh Shilimkar santosh.shilim...@ti.com writes: From: Tero Kristo t-kri...@ti.com Simplifies code and also allows the re-use as is on OMAP5 devices. nit: changelog here is rather weak. It claims simplifies code but it's not obvious from the patch how changing a few #defines does that. Kevin Signed-off-by: Tero Kristo t-kri...@ti.com Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com --- arch/arm/mach-omap2/omap4-sar-layout.h | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/arch/arm/mach-omap2/omap4-sar-layout.h b/arch/arm/mach-omap2/omap4-sar-layout.h index e170fe8..6822d0a 100644 --- a/arch/arm/mach-omap2/omap4-sar-layout.h +++ b/arch/arm/mach-omap2/omap4-sar-layout.h @@ -20,13 +20,13 @@ #define SAR_BANK4_OFFSET 0x3000 /* Scratch pad memory offsets from SAR_BANK1 */ -#define SCU_OFFSET0 0xd00 -#define SCU_OFFSET1 0xd04 -#define OMAP_TYPE_OFFSET 0xd10 -#define L2X0_SAVE_OFFSET00xd14 -#define L2X0_SAVE_OFFSET10xd18 -#define L2X0_AUXCTRL_OFFSET 0xd1c -#define L2X0_PREFETCH_CTRL_OFFSET0xd20 +#define SCU_OFFSET0 0xfe4 +#define SCU_OFFSET1 0xfe8 +#define OMAP_TYPE_OFFSET 0xfec +#define L2X0_SAVE_OFFSET00xff0 +#define L2X0_SAVE_OFFSET10xff4 +#define L2X0_AUXCTRL_OFFSET 0xff8 +#define L2X0_PREFETCH_CTRL_OFFSET0xffc /* CPUx Wakeup Non-Secure Physical Address offsets in SAR_BANK3 */ #define CPU0_WAKEUP_NS_PA_ADDR_OFFSET0xa04 -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/9] ARM: OMAP4+: Use common scratchpad SAR RAM offsets for all architectures
On Thursday 28 March 2013 12:11 AM, Kevin Hilman wrote: Santosh Shilimkar santosh.shilim...@ti.com writes: From: Tero Kristo t-kri...@ti.com Simplifies code and also allows the re-use as is on OMAP5 devices. nit: changelog here is rather weak. It claims simplifies code but it's not obvious from the patch how changing a few #defines does that. I agree. Basically the offset are chosen such a way that they can work on OMAP4 and OMAP5 instead of having two separate sets. Will expand the changelog to make it clear. Regards, Santosh -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/9] ARM: OMAP4+: Use common scratchpad SAR RAM offsets for all architectures
* Santosh Shilimkar santosh.shilim...@ti.com [130327 13:52]: On Thursday 28 March 2013 12:11 AM, Kevin Hilman wrote: Santosh Shilimkar santosh.shilim...@ti.com writes: From: Tero Kristo t-kri...@ti.com Simplifies code and also allows the re-use as is on OMAP5 devices. nit: changelog here is rather weak. It claims simplifies code but it's not obvious from the patch how changing a few #defines does that. I agree. Basically the offset are chosen such a way that they can work on OMAP4 and OMAP5 instead of having two separate sets. Will expand the changelog to make it clear. You might want to mention also that the offsets are only used by the kernel to save and restore registers from so people don't think those are hardare registers and that the patch might break some things. Regards, Tony -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/9] ARM: OMAP4+: Use common scratchpad SAR RAM offsets for all architectures
On Thursday 28 March 2013 02:19 AM, Tony Lindgren wrote: * Santosh Shilimkar santosh.shilim...@ti.com [130327 13:52]: On Thursday 28 March 2013 12:11 AM, Kevin Hilman wrote: Santosh Shilimkar santosh.shilim...@ti.com writes: From: Tero Kristo t-kri...@ti.com Simplifies code and also allows the re-use as is on OMAP5 devices. nit: changelog here is rather weak. It claims simplifies code but it's not obvious from the patch how changing a few #defines does that. I agree. Basically the offset are chosen such a way that they can work on OMAP4 and OMAP5 instead of having two separate sets. Will expand the changelog to make it clear. You might want to mention also that the offsets are only used by the kernel to save and restore registers from so people don't think those are hardare registers and that the patch might break some things. Yeah. Will mention that. Regards, Santosh -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
