OMAP4: PRCM: add OMAP4-specific accessor/mutator functions
In some ways, the OMAP4 PRCM register layout is quite different than
the OMAP2/3 PRCM register layout. For example, on OMAP2/3, from a
register layout point of view, all CM instances were located in the CM
subsystem, and all PRM instances were located in the PRM subsystem.
OMAP4 changes this. Now, for example, some CM instances, such as
WKUP_CM and EMU_CM, are located in the system PRM subsystem. And a
"local PRCM" exists for the MPU - this PRCM combines registers that
would normally appear in both CM and PRM instances, but uses its own
register layout which matches neither the OMAP2/3 PRCM layout nor the
OMAP4 PRCM layout.
To try to deal with this, introduce some new functions, omap4_cminst*
and omap4_prminst*. The former is to be used when writing to a CM
instance register (no matter what subsystem or hardware module it
exists in), and the latter, similarly, with PRM instance registers.
To determine which "PRCM partition" to write to, the functions take a
PRCM instance ID argument. Subsequent patches add these partition IDs
to the OMAP4 powerdomain and clockdomain definitions.
As far as I can see, there's really no good way to handle these types
of register access inconsistencies. This patch seemed like the least
bad approach.
Moving forward, the long-term goal is to remove all direct PRCM
register access from the PM code. PRCM register access should go
through layers such as the powerdomain and clockdomain code that can
hide the details of how to interact with the specific hardware
variant.
While here, rename cm4xxx.c to cm44xx.c to match the naming convention
of the other OMAP4 PRCM files.
Thanks to Santosh Shilimkar <santosh.shilimkar@ti.com>, Rajendra Nayak
<rnayak@ti.com>, and Benoît Cousson <b-cousson@ti.com> for some comments.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Benoît Cousson <b-cousson@ti.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
2010-12-22 12:05:14 +08:00
|
|
|
/*
|
|
|
|
|
* OMAP4 PRCM definitions
|
|
|
|
|
*
|
|
|
|
|
* Copyright (C) 2010 Texas Instruments, Inc.
|
|
|
|
|
* Copyright (C) 2010 Nokia Corporation
|
|
|
|
|
*
|
|
|
|
|
* Paul Walmsley
|
|
|
|
|
*
|
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
|
* it under the terms of the GNU General Public License version 2 as
|
|
|
|
|
* published by the Free Software Foundation.
|
|
|
|
|
*
|
|
|
|
|
* This file contains macros and functions that are common to all of
|
|
|
|
|
* the PRM/CM/PRCM blocks on the OMAP4 devices: PRM, CM1, CM2,
|
|
|
|
|
* PRCM_MPU, SCRM
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef __ARCH_ARM_MACH_OMAP2_PRCM44XX_H
|
|
|
|
|
#define __ARCH_ARM_MACH_OMAP2_PRCM44XX_H
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* OMAP4 PRCM partition IDs
|
|
|
|
|
*
|
|
|
|
|
* The numbers and order are arbitrary, but 0 is reserved for the
|
|
|
|
|
* 'invalid' partition in case someone forgets to add a
|
|
|
|
|
* .prcm_partition field.
|
|
|
|
|
*/
|
|
|
|
|
#define OMAP4430_INVALID_PRCM_PARTITION 0
|
|
|
|
|
#define OMAP4430_PRM_PARTITION 1
|
|
|
|
|
#define OMAP4430_CM1_PARTITION 2
|
|
|
|
|
#define OMAP4430_CM2_PARTITION 3
|
|
|
|
|
#define OMAP4430_SCRM_PARTITION 4
|
|
|
|
|
#define OMAP4430_PRCM_MPU_PARTITION 5
|
|
|
|
|
|
2013-05-30 00:38:06 +08:00
|
|
|
#define OMAP54XX_PRM_PARTITION 1
|
|
|
|
|
#define OMAP54XX_CM_CORE_AON_PARTITION 2
|
|
|
|
|
#define OMAP54XX_CM_CORE_PARTITION 3
|
|
|
|
|
#define OMAP54XX_SCRM_PARTITION 4
|
|
|
|
|
#define OMAP54XX_PRCM_MPU_PARTITION 5
|
|
|
|
|
|
2013-07-09 15:32:11 +08:00
|
|
|
#define DRA7XX_PRM_PARTITION 1
|
|
|
|
|
#define DRA7XX_CM_CORE_AON_PARTITION 2
|
|
|
|
|
#define DRA7XX_CM_CORE_PARTITION 3
|
|
|
|
|
#define DRA7XX_MPU_PRCM_PARTITION 5
|
|
|
|
|
|
OMAP4: PRCM: add OMAP4-specific accessor/mutator functions
In some ways, the OMAP4 PRCM register layout is quite different than
the OMAP2/3 PRCM register layout. For example, on OMAP2/3, from a
register layout point of view, all CM instances were located in the CM
subsystem, and all PRM instances were located in the PRM subsystem.
OMAP4 changes this. Now, for example, some CM instances, such as
WKUP_CM and EMU_CM, are located in the system PRM subsystem. And a
"local PRCM" exists for the MPU - this PRCM combines registers that
would normally appear in both CM and PRM instances, but uses its own
register layout which matches neither the OMAP2/3 PRCM layout nor the
OMAP4 PRCM layout.
To try to deal with this, introduce some new functions, omap4_cminst*
and omap4_prminst*. The former is to be used when writing to a CM
instance register (no matter what subsystem or hardware module it
exists in), and the latter, similarly, with PRM instance registers.
To determine which "PRCM partition" to write to, the functions take a
PRCM instance ID argument. Subsequent patches add these partition IDs
to the OMAP4 powerdomain and clockdomain definitions.
As far as I can see, there's really no good way to handle these types
of register access inconsistencies. This patch seemed like the least
bad approach.
Moving forward, the long-term goal is to remove all direct PRCM
register access from the PM code. PRCM register access should go
through layers such as the powerdomain and clockdomain code that can
hide the details of how to interact with the specific hardware
variant.
While here, rename cm4xxx.c to cm44xx.c to match the naming convention
of the other OMAP4 PRCM files.
Thanks to Santosh Shilimkar <santosh.shilimkar@ti.com>, Rajendra Nayak
<rnayak@ti.com>, and Benoît Cousson <b-cousson@ti.com> for some comments.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Benoît Cousson <b-cousson@ti.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
2010-12-22 12:05:14 +08:00
|
|
|
/*
|
|
|
|
|
* OMAP4_MAX_PRCM_PARTITIONS: set to the highest value of the PRCM partition
|
|
|
|
|
* IDs, plus one
|
|
|
|
|
*/
|
|
|
|
|
#define OMAP4_MAX_PRCM_PARTITIONS 6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#endif
|