2008-03-18 15:02:50 +07:00
|
|
|
/*
|
2010-12-22 05:30:55 +07:00
|
|
|
* OMAP2/3/4 Power/Reset Management (PRM) bitfield definitions
|
2008-03-18 15:02:50 +07:00
|
|
|
*
|
2012-10-30 09:57:39 +07:00
|
|
|
* Copyright (C) 2007-2009, 2012 Texas Instruments, Inc.
|
2010-09-21 23:34:10 +07:00
|
|
|
* Copyright (C) 2010 Nokia Corporation
|
2008-03-18 15:02:50 +07:00
|
|
|
*
|
2010-12-22 05:30:55 +07:00
|
|
|
* Paul Walmsley
|
2008-03-18 15:02:50 +07:00
|
|
|
*
|
|
|
|
|
* 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.
|
|
|
|
|
*/
|
2010-12-22 05:30:55 +07:00
|
|
|
#ifndef __ARCH_ARM_MACH_OMAP2_PRM_H
|
|
|
|
|
#define __ARCH_ARM_MACH_OMAP2_PRM_H
|
2008-03-18 15:02:50 +07:00
|
|
|
|
|
|
|
|
#include "prcm-common.h"
|
|
|
|
|
|
2012-10-30 09:57:39 +07:00
|
|
|
# ifndef __ASSEMBLER__
|
|
|
|
|
extern void __iomem *prm_base;
|
2014-03-31 22:15:44 +07:00
|
|
|
extern u16 prm_features;
|
2012-10-30 09:57:39 +07:00
|
|
|
extern void omap2_set_globals_prm(void __iomem *prm);
|
2013-10-25 19:28:11 +07:00
|
|
|
int of_prcm_init(void);
|
2012-10-30 09:57:39 +07:00
|
|
|
# endif
|
|
|
|
|
|
2014-03-31 22:15:44 +07:00
|
|
|
/*
|
|
|
|
|
* prm_features flag values
|
|
|
|
|
*
|
|
|
|
|
* PRM_HAS_IO_WAKEUP: has IO wakeup capability
|
|
|
|
|
* PRM_HAS_VOLTAGE: has voltage domains
|
|
|
|
|
*/
|
|
|
|
|
#define PRM_HAS_IO_WAKEUP (1 << 0)
|
2012-10-30 09:57:44 +07:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* MAX_MODULE_SOFTRESET_WAIT: Maximum microseconds to wait for OMAP
|
|
|
|
|
* module to softreset
|
|
|
|
|
*/
|
|
|
|
|
#define MAX_MODULE_SOFTRESET_WAIT 10000
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* MAX_MODULE_HARDRESET_WAIT: Maximum microseconds to wait for an OMAP
|
|
|
|
|
* submodule to exit hardreset
|
|
|
|
|
*/
|
|
|
|
|
#define MAX_MODULE_HARDRESET_WAIT 10000
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Register bitfields
|
|
|
|
|
*/
|
|
|
|
|
|
2008-03-18 15:02:50 +07:00
|
|
|
/*
|
|
|
|
|
* 24XX: PM_PWSTST_CORE, PM_PWSTST_GFX, PM_PWSTST_MPU, PM_PWSTST_DSP
|
|
|
|
|
*
|
|
|
|
|
* 2430: PM_PWSTST_MDM
|
|
|
|
|
*
|
|
|
|
|
* 3430: PM_PWSTST_IVA2, PM_PWSTST_MPU, PM_PWSTST_CORE, PM_PWSTST_GFX,
|
|
|
|
|
* PM_PWSTST_DSS, PM_PWSTST_CAM, PM_PWSTST_PER, PM_PWSTST_EMU,
|
|
|
|
|
* PM_PWSTST_NEON
|
|
|
|
|
*/
|
2010-05-19 07:40:23 +07:00
|
|
|
#define OMAP_INTRANSITION_MASK (1 << 20)
|
2008-03-18 15:02:50 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* 24XX: PM_PWSTST_GFX, PM_PWSTST_DSP
|
|
|
|
|
*
|
|
|
|
|
* 2430: PM_PWSTST_MDM
|
|
|
|
|
*
|
|
|
|
|
* 3430: PM_PWSTST_IVA2, PM_PWSTST_MPU, PM_PWSTST_CORE, PM_PWSTST_GFX,
|
|
|
|
|
* PM_PWSTST_DSS, PM_PWSTST_CAM, PM_PWSTST_PER, PM_PWSTST_EMU,
|
|
|
|
|
* PM_PWSTST_NEON
|
|
|
|
|
*/
|
|
|
|
|
#define OMAP_POWERSTATEST_SHIFT 0
|
|
|
|
|
#define OMAP_POWERSTATEST_MASK (0x3 << 0)
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* 24XX: PM_PWSTCTRL_MPU, PM_PWSTCTRL_CORE, PM_PWSTCTRL_GFX,
|
|
|
|
|
* PM_PWSTCTRL_DSP, PM_PWSTST_MPU
|
|
|
|
|
*
|
|
|
|
|
* 2430: PM_PWSTCTRL_MDM shared bits
|
|
|
|
|
*
|
|
|
|
|
* 3430: PM_PWSTCTRL_IVA2, PM_PWSTCTRL_MPU, PM_PWSTCTRL_CORE,
|
|
|
|
|
* PM_PWSTCTRL_GFX, PM_PWSTCTRL_DSS, PM_PWSTCTRL_CAM, PM_PWSTCTRL_PER,
|
|
|
|
|
* PM_PWSTCTRL_NEON shared bits
|
|
|
|
|
*/
|
|
|
|
|
#define OMAP_POWERSTATE_SHIFT 0
|
|
|
|
|
#define OMAP_POWERSTATE_MASK (0x3 << 0)
|
|
|
|
|
|
2012-10-21 14:01:13 +07:00
|
|
|
/*
|
|
|
|
|
* Standardized OMAP reset source bits
|
|
|
|
|
*
|
|
|
|
|
* To the extent these happen to match the hardware register bit
|
|
|
|
|
* shifts, it's purely coincidental. Used by omap-wdt.c.
|
|
|
|
|
* OMAP_UNKNOWN_RST_SRC_ID_SHIFT is a special value, used whenever
|
|
|
|
|
* there are any bits remaining in the global PRM_RSTST register that
|
|
|
|
|
* haven't been identified, or when the PRM code for the current SoC
|
|
|
|
|
* doesn't know how to interpret the register.
|
|
|
|
|
*/
|
|
|
|
|
#define OMAP_GLOBAL_COLD_RST_SRC_ID_SHIFT 0
|
|
|
|
|
#define OMAP_GLOBAL_WARM_RST_SRC_ID_SHIFT 1
|
|
|
|
|
#define OMAP_SECU_VIOL_RST_SRC_ID_SHIFT 2
|
|
|
|
|
#define OMAP_MPU_WD_RST_SRC_ID_SHIFT 3
|
|
|
|
|
#define OMAP_SECU_WD_RST_SRC_ID_SHIFT 4
|
|
|
|
|
#define OMAP_EXTWARM_RST_SRC_ID_SHIFT 5
|
|
|
|
|
#define OMAP_VDD_MPU_VM_RST_SRC_ID_SHIFT 6
|
|
|
|
|
#define OMAP_VDD_IVA_VM_RST_SRC_ID_SHIFT 7
|
|
|
|
|
#define OMAP_VDD_CORE_VM_RST_SRC_ID_SHIFT 8
|
|
|
|
|
#define OMAP_ICEPICK_RST_SRC_ID_SHIFT 9
|
|
|
|
|
#define OMAP_ICECRUSHER_RST_SRC_ID_SHIFT 10
|
|
|
|
|
#define OMAP_C2C_RST_SRC_ID_SHIFT 11
|
|
|
|
|
#define OMAP_UNKNOWN_RST_SRC_ID_SHIFT 12
|
|
|
|
|
|
ARM: OMAP2+: PRM: prepare for use of prm_ll_data function pointers
There are several PRM operations which behave similarly across OMAP2+
SoCs, but which have slight differences in their underlying
implementations. For example, to fetch the SoC's last reset sources,
different registers are read across OMAP2xxx, 3xxx, and 44xx, and
different bits are used on each SoC. But the information returned is
so similar that a single, common interface for drivers is useful.
This patch creates the support code for this function pointer
registration process. No function pointers are included yet, but a
subsequent patch will create one for the reset source API.
To illustrate the end goal with the above reset source example, each
per-SoC driver will use its own low-level implementation function --
e.g., prm2xxx.c would contain omap2xxx_prm_read_reset_sources(). This
function would read the appropriate register and remap the register
bits to a standard set of reset source bits. When the prm2xxx.c
driver is loaded, it would register this function with the common PRM
driver, prm.c. prm.c would then export a common function,
omap_prm_read_reset_sources(). Calling it would call through to the
function pointer for the currently-registered SoC PRM driver. This
will allow other drivers to use PRM-provided data and operations
without needing to know which SoC is currently in use.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
2012-10-21 14:01:11 +07:00
|
|
|
#ifndef __ASSEMBLER__
|
|
|
|
|
|
2012-10-21 14:01:13 +07:00
|
|
|
/**
|
|
|
|
|
* struct prm_reset_src_map - map register bitshifts to standard bitshifts
|
|
|
|
|
* @reg_shift: bitshift in the PRM reset source register
|
|
|
|
|
* @std_shift: bitshift equivalent in the standard reset source list
|
|
|
|
|
*
|
|
|
|
|
* The fields are signed because -1 is used as a terminator.
|
|
|
|
|
*/
|
|
|
|
|
struct prm_reset_src_map {
|
|
|
|
|
s8 reg_shift;
|
|
|
|
|
s8 std_shift;
|
|
|
|
|
};
|
|
|
|
|
|
ARM: OMAP2+: PRM: prepare for use of prm_ll_data function pointers
There are several PRM operations which behave similarly across OMAP2+
SoCs, but which have slight differences in their underlying
implementations. For example, to fetch the SoC's last reset sources,
different registers are read across OMAP2xxx, 3xxx, and 44xx, and
different bits are used on each SoC. But the information returned is
so similar that a single, common interface for drivers is useful.
This patch creates the support code for this function pointer
registration process. No function pointers are included yet, but a
subsequent patch will create one for the reset source API.
To illustrate the end goal with the above reset source example, each
per-SoC driver will use its own low-level implementation function --
e.g., prm2xxx.c would contain omap2xxx_prm_read_reset_sources(). This
function would read the appropriate register and remap the register
bits to a standard set of reset source bits. When the prm2xxx.c
driver is loaded, it would register this function with the common PRM
driver, prm.c. prm.c would then export a common function,
omap_prm_read_reset_sources(). Calling it would call through to the
function pointer for the currently-registered SoC PRM driver. This
will allow other drivers to use PRM-provided data and operations
without needing to know which SoC is currently in use.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
2012-10-21 14:01:11 +07:00
|
|
|
/**
|
|
|
|
|
* struct prm_ll_data - fn ptrs to per-SoC PRM function implementations
|
ARM: OMAP2+: hwmod: Add support for per hwmod/module context lost count
OMAP4 has module specific context lost registers which makes it now
possible to have module level context loss count, instead of relying
on the powerdomain level context count.
Add 2 private hwmod api's to update/clear the hwmod/module specific
context lost counters/register.
Update the module specific context_lost_counter and clear the hardware
bits just after enabling the module.
omap_hwmod_get_context_loss_count() now returns the hwmod context loss
count them on platforms where they exist (OMAP4), else fall back on
the pwrdm level counters for older platforms.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
[paul@pwsan.com: added function kerneldoc, fixed structure kerneldoc,
rearranged structure to avoid memory waste, marked fns as OMAP4-specific,
prevent fn entry on non-OMAP4 chips, reduced indentation, merged update
and clear, merged patches]
[t-kristo@ti.com: added support for arch specific hwmod ops, and changed
the no context offset indicator to USHRT_MAX]
Signed-off-by: Tero Kristo <t-kristo@ti.com>
[paul@pwsan.com: use NO_CONTEXT_LOSS_BIT flag rather than USHRT_MAX;
convert unsigned context lost counter to int to match the return type;
get rid of hwmod_ops in favor of the existing soc_ops mechanism;
move context loss low-level accesses to the PRM code]
Signed-off-by: Paul Walmsley <paul@pwsan.com>
2012-11-22 06:15:17 +07:00
|
|
|
* @read_reset_sources: ptr to the SoC PRM-specific get_reset_source impl
|
|
|
|
|
* @was_any_context_lost_old: ptr to the SoC PRM context loss test fn
|
|
|
|
|
* @clear_context_loss_flags_old: ptr to the SoC PRM context loss flag clear fn
|
2014-03-31 22:15:45 +07:00
|
|
|
* @late_init: ptr to the late init function
|
ARM: OMAP2+: hwmod: Add support for per hwmod/module context lost count
OMAP4 has module specific context lost registers which makes it now
possible to have module level context loss count, instead of relying
on the powerdomain level context count.
Add 2 private hwmod api's to update/clear the hwmod/module specific
context lost counters/register.
Update the module specific context_lost_counter and clear the hardware
bits just after enabling the module.
omap_hwmod_get_context_loss_count() now returns the hwmod context loss
count them on platforms where they exist (OMAP4), else fall back on
the pwrdm level counters for older platforms.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
[paul@pwsan.com: added function kerneldoc, fixed structure kerneldoc,
rearranged structure to avoid memory waste, marked fns as OMAP4-specific,
prevent fn entry on non-OMAP4 chips, reduced indentation, merged update
and clear, merged patches]
[t-kristo@ti.com: added support for arch specific hwmod ops, and changed
the no context offset indicator to USHRT_MAX]
Signed-off-by: Tero Kristo <t-kristo@ti.com>
[paul@pwsan.com: use NO_CONTEXT_LOSS_BIT flag rather than USHRT_MAX;
convert unsigned context lost counter to int to match the return type;
get rid of hwmod_ops in favor of the existing soc_ops mechanism;
move context loss low-level accesses to the PRM code]
Signed-off-by: Paul Walmsley <paul@pwsan.com>
2012-11-22 06:15:17 +07:00
|
|
|
*
|
|
|
|
|
* XXX @was_any_context_lost_old and @clear_context_loss_flags_old are
|
|
|
|
|
* deprecated.
|
ARM: OMAP2+: PRM: prepare for use of prm_ll_data function pointers
There are several PRM operations which behave similarly across OMAP2+
SoCs, but which have slight differences in their underlying
implementations. For example, to fetch the SoC's last reset sources,
different registers are read across OMAP2xxx, 3xxx, and 44xx, and
different bits are used on each SoC. But the information returned is
so similar that a single, common interface for drivers is useful.
This patch creates the support code for this function pointer
registration process. No function pointers are included yet, but a
subsequent patch will create one for the reset source API.
To illustrate the end goal with the above reset source example, each
per-SoC driver will use its own low-level implementation function --
e.g., prm2xxx.c would contain omap2xxx_prm_read_reset_sources(). This
function would read the appropriate register and remap the register
bits to a standard set of reset source bits. When the prm2xxx.c
driver is loaded, it would register this function with the common PRM
driver, prm.c. prm.c would then export a common function,
omap_prm_read_reset_sources(). Calling it would call through to the
function pointer for the currently-registered SoC PRM driver. This
will allow other drivers to use PRM-provided data and operations
without needing to know which SoC is currently in use.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
2012-10-21 14:01:11 +07:00
|
|
|
*/
|
2012-10-21 14:01:13 +07:00
|
|
|
struct prm_ll_data {
|
|
|
|
|
u32 (*read_reset_sources)(void);
|
ARM: OMAP2+: hwmod: Add support for per hwmod/module context lost count
OMAP4 has module specific context lost registers which makes it now
possible to have module level context loss count, instead of relying
on the powerdomain level context count.
Add 2 private hwmod api's to update/clear the hwmod/module specific
context lost counters/register.
Update the module specific context_lost_counter and clear the hardware
bits just after enabling the module.
omap_hwmod_get_context_loss_count() now returns the hwmod context loss
count them on platforms where they exist (OMAP4), else fall back on
the pwrdm level counters for older platforms.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
[paul@pwsan.com: added function kerneldoc, fixed structure kerneldoc,
rearranged structure to avoid memory waste, marked fns as OMAP4-specific,
prevent fn entry on non-OMAP4 chips, reduced indentation, merged update
and clear, merged patches]
[t-kristo@ti.com: added support for arch specific hwmod ops, and changed
the no context offset indicator to USHRT_MAX]
Signed-off-by: Tero Kristo <t-kristo@ti.com>
[paul@pwsan.com: use NO_CONTEXT_LOSS_BIT flag rather than USHRT_MAX;
convert unsigned context lost counter to int to match the return type;
get rid of hwmod_ops in favor of the existing soc_ops mechanism;
move context loss low-level accesses to the PRM code]
Signed-off-by: Paul Walmsley <paul@pwsan.com>
2012-11-22 06:15:17 +07:00
|
|
|
bool (*was_any_context_lost_old)(u8 part, s16 inst, u16 idx);
|
|
|
|
|
void (*clear_context_loss_flags_old)(u8 part, s16 inst, u16 idx);
|
2014-03-31 22:15:45 +07:00
|
|
|
int (*late_init)(void);
|
2012-10-21 14:01:13 +07:00
|
|
|
};
|
ARM: OMAP2+: PRM: prepare for use of prm_ll_data function pointers
There are several PRM operations which behave similarly across OMAP2+
SoCs, but which have slight differences in their underlying
implementations. For example, to fetch the SoC's last reset sources,
different registers are read across OMAP2xxx, 3xxx, and 44xx, and
different bits are used on each SoC. But the information returned is
so similar that a single, common interface for drivers is useful.
This patch creates the support code for this function pointer
registration process. No function pointers are included yet, but a
subsequent patch will create one for the reset source API.
To illustrate the end goal with the above reset source example, each
per-SoC driver will use its own low-level implementation function --
e.g., prm2xxx.c would contain omap2xxx_prm_read_reset_sources(). This
function would read the appropriate register and remap the register
bits to a standard set of reset source bits. When the prm2xxx.c
driver is loaded, it would register this function with the common PRM
driver, prm.c. prm.c would then export a common function,
omap_prm_read_reset_sources(). Calling it would call through to the
function pointer for the currently-registered SoC PRM driver. This
will allow other drivers to use PRM-provided data and operations
without needing to know which SoC is currently in use.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
2012-10-21 14:01:11 +07:00
|
|
|
|
|
|
|
|
extern int prm_register(struct prm_ll_data *pld);
|
|
|
|
|
extern int prm_unregister(struct prm_ll_data *pld);
|
|
|
|
|
|
2012-10-21 14:01:13 +07:00
|
|
|
extern u32 prm_read_reset_sources(void);
|
ARM: OMAP2+: hwmod: Add support for per hwmod/module context lost count
OMAP4 has module specific context lost registers which makes it now
possible to have module level context loss count, instead of relying
on the powerdomain level context count.
Add 2 private hwmod api's to update/clear the hwmod/module specific
context lost counters/register.
Update the module specific context_lost_counter and clear the hardware
bits just after enabling the module.
omap_hwmod_get_context_loss_count() now returns the hwmod context loss
count them on platforms where they exist (OMAP4), else fall back on
the pwrdm level counters for older platforms.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
[paul@pwsan.com: added function kerneldoc, fixed structure kerneldoc,
rearranged structure to avoid memory waste, marked fns as OMAP4-specific,
prevent fn entry on non-OMAP4 chips, reduced indentation, merged update
and clear, merged patches]
[t-kristo@ti.com: added support for arch specific hwmod ops, and changed
the no context offset indicator to USHRT_MAX]
Signed-off-by: Tero Kristo <t-kristo@ti.com>
[paul@pwsan.com: use NO_CONTEXT_LOSS_BIT flag rather than USHRT_MAX;
convert unsigned context lost counter to int to match the return type;
get rid of hwmod_ops in favor of the existing soc_ops mechanism;
move context loss low-level accesses to the PRM code]
Signed-off-by: Paul Walmsley <paul@pwsan.com>
2012-11-22 06:15:17 +07:00
|
|
|
extern bool prm_was_any_context_lost_old(u8 part, s16 inst, u16 idx);
|
|
|
|
|
extern void prm_clear_context_loss_flags_old(u8 part, s16 inst, u16 idx);
|
2012-10-21 14:01:13 +07:00
|
|
|
|
ARM: OMAP2+: PRM: prepare for use of prm_ll_data function pointers
There are several PRM operations which behave similarly across OMAP2+
SoCs, but which have slight differences in their underlying
implementations. For example, to fetch the SoC's last reset sources,
different registers are read across OMAP2xxx, 3xxx, and 44xx, and
different bits are used on each SoC. But the information returned is
so similar that a single, common interface for drivers is useful.
This patch creates the support code for this function pointer
registration process. No function pointers are included yet, but a
subsequent patch will create one for the reset source API.
To illustrate the end goal with the above reset source example, each
per-SoC driver will use its own low-level implementation function --
e.g., prm2xxx.c would contain omap2xxx_prm_read_reset_sources(). This
function would read the appropriate register and remap the register
bits to a standard set of reset source bits. When the prm2xxx.c
driver is loaded, it would register this function with the common PRM
driver, prm.c. prm.c would then export a common function,
omap_prm_read_reset_sources(). Calling it would call through to the
function pointer for the currently-registered SoC PRM driver. This
will allow other drivers to use PRM-provided data and operations
without needing to know which SoC is currently in use.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
2012-10-21 14:01:11 +07:00
|
|
|
#endif
|
2008-03-18 15:02:50 +07:00
|
|
|
|
2012-10-21 14:01:13 +07:00
|
|
|
|
2008-03-18 15:02:50 +07:00
|
|
|
#endif
|