public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv6 3/7] ARM: OMAP4: hwmod: flag hwmods/modules not supporting module level context status
Date: Thu, 19 Jul 2012 12:50:55 +0300	[thread overview]
Message-ID: <1342691455.4672.125.camel@sokoban> (raw)
In-Reply-To: <alpine.DEB.2.00.1207181122280.19048@utopia.booyaka.com>

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 firmware,
> > > no?
> > 
> > It looks like current hwmod data doesn't support specific bits to be
> > used for the context declaration, it is only specifying the register
> > offset. Also, the same register is used by aess hwmod, so this will
> > cause a conflict if I take the same register into use.
> > 
> > This could be fixed by adding a field for the context bits, but I guess
> > this should be commented upon by someone (Benoit / Paul) before I craft
> > some sort of patch for that.
> 
> If you need to add a u8 there to specify the bitshift, go ahead and do it.  
> u8 lostmem_bit, perhaps?

Mask might be better, as we have RFF / DFF bits, and also if mask is not
defined, we can assume we want to check the whole register (current
behavior.) I'll add this for next rev.

-Tero

  reply	other threads:[~2012-07-19  9:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 15:26 [PATCHv6 0/7] ARM: OMAP4: core retention support Tero Kristo
2012-06-11 15:26 ` [PATCHv6 1/7] ARM: OMAP4: PM: add errata support Tero Kristo
2012-06-11 15:26 ` [PATCHv6 2/7] ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC control register change Tero Kristo
2012-07-18  9:17   ` Paul Walmsley
2012-07-18  9:51     ` Tero Kristo
2012-07-18  9:54       ` Paul Walmsley
2012-06-11 15:26 ` [PATCHv6 3/7] ARM: OMAP4: hwmod: flag hwmods/modules not supporting module level context status Tero Kristo
2012-07-17  8:11   ` Menon, Nishanth
2012-07-18  9:00     ` Tero Kristo
2012-07-18 16:23     ` Tero Kristo
2012-07-18 17:24       ` Paul Walmsley
2012-07-19  9:50         ` Tero Kristo [this message]
2012-06-11 15:26 ` [PATCHv6 4/7] ARM: OMAP: hwmod: Add support for per hwmod/module context lost count Tero Kristo
2012-07-17  7:59   ` Menon, Nishanth
2012-07-18  9:15     ` Tero Kristo
2012-07-19  5:55       ` Menon, Nishanth
2012-07-19  9:49         ` Tero Kristo
2012-07-19 10:27           ` Menon, Nishanth
2012-07-19 11:47             ` Tero Kristo
2012-07-19 10:35           ` Shilimkar, Santosh
2012-07-19 11:44             ` Tero Kristo
2012-07-19  7:00   ` Menon, Nishanth
2012-06-11 15:26 ` [PATCHv6 5/7] ARM: OMAP4: pwrdm: add support for reading prev logic and mem states Tero Kristo
2012-06-11 15:26 ` [PATCHv6 6/7] ARM: OMAP4: suspend: Program all domains to retention Tero Kristo
2012-06-11 15:26 ` [PATCHv6 7/7] ARM: OMAP4: PM: put all domains to OSWR during suspend Tero Kristo

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=1342691455.4672.125.camel@sokoban \
    --to=t-kristo@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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