On Wed, 2012-07-18 at 11:24 -0600, Paul Walmsley wrote:
On Wed, 18 Jul 2012, Tero Kristo wrote:
On Tue, 2012-07-17 at 03:11 -0500, Menon, Nishanth wrote:
OMAP4430_RM_ABE_AESS_CONTEXT? why not use LOSTMEM_AESSMEM ? ABE will
need to know when it lost context to be able to reload it's
On Tue, 2012-07-17 at 03:11 -0500, Menon, Nishanth wrote:
On Mon, Jun 11, 2012 at 10:26 AM, Tero Kristo t-kri...@ti.com wrote:
On OMAP4 most modules/hwmods support module level context status. On
OMAP3 and earlier, we relied on the power domain level context status.
Identify all modules
On Tue, 2012-07-17 at 03:11 -0500, Menon, Nishanth wrote:
On Mon, Jun 11, 2012 at 10:26 AM, Tero Kristo t-kri...@ti.com wrote:
On OMAP4 most modules/hwmods support module level context status. On
OMAP3 and earlier, we relied on the power domain level context status.
Identify all modules
On Wed, 18 Jul 2012, Tero Kristo wrote:
On Tue, 2012-07-17 at 03:11 -0500, Menon, Nishanth wrote:
OMAP4430_RM_ABE_AESS_CONTEXT? why not use LOSTMEM_AESSMEM ? ABE will
need to know when it lost context to be able to reload it's firmware,
no?
It looks like current hwmod data doesn't
On Mon, Jun 11, 2012 at 10:26 AM, Tero Kristo t-kri...@ti.com wrote:
On OMAP4 most modules/hwmods support module level context status. On
OMAP3 and earlier, we relied on the power domain level context status.
Identify all modules that don't support 'context_offs' by marking the
offset as
On OMAP4 most modules/hwmods support module level context status. On
OMAP3 and earlier, we relied on the power domain level context status.
Identify all modules that don't support 'context_offs' by marking the
offset as USHRT_MAX. Rest have a valid 'context_offs' populated in
.prcm structure
