From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv6 2/7] ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC control register change.
Date: Wed, 18 Jul 2012 12:51:45 +0300 [thread overview]
Message-ID: <1342605105.4672.95.camel@sokoban> (raw)
In-Reply-To: <alpine.DEB.2.00.1207180314250.28834@utopia.booyaka.com>
On Wed, 2012-07-18 at 03:17 -0600, Paul Walmsley wrote:
> Hi
>
> one trivial comment
>
> On Mon, 11 Jun 2012, Tero Kristo wrote:
>
> > diff --git a/arch/arm/mach-omap2/pm.h b/arch/arm/mach-omap2/pm.h
> > index 46ab9d9..8d7de4f 100644
> > --- a/arch/arm/mach-omap2/pm.h
> > +++ b/arch/arm/mach-omap2/pm.h
> > @@ -88,6 +88,8 @@ extern void enable_omap3630_toggle_l2_on_restore(void);
> > static inline void enable_omap3630_toggle_l2_on_restore(void) { }
> > #endif /* defined(CONFIG_PM) && defined(CONFIG_ARCH_OMAP3) */
> >
> > +#define PM_OMAP4_ROM_SMP_BOOT_ERRATUM_xxx (1 << 0)
>
> "xxx" isn't unique, nor is it descriptive :-)
>
> Looking at the mail threads on this one, it sounds like there may not be a
> public erratum number associated with this. If there is, the 'xxx' should
> be replaced with the number. If there isn't, then it would be good to
> make up something short, like "GICD" to replace the "xxx".
There isn't public erratum number for this, thats the reason for xxx. I
can change the xxx to GICD though if that is better.
-Tero
next prev parent reply other threads:[~2012-07-18 9:51 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 [this message]
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
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=1342605105.4672.95.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