All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Nishanth Menon <nm@ti.com>, TAO HU <tghk48@motorola.com>
Cc: TAO HU <taohu@motorola.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	Jean <jean.pihet@newoldbits.com>, Tony <tony@atomide.com>,
	Kevin <khilman@deeprootsystems.com>,
	Vishwanath Sripathy <vishwanath.bs@ti.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: RE: [PATCH 4/5 v2] OMAP3630: PM: Disable L2 cache while invalidating L2 cache
Date: Thu, 2 Dec 2010 10:35:57 +0530	[thread overview]
Message-ID: <68d1d4807ed2c28d3b339571601a2a7f@mail.gmail.com> (raw)
In-Reply-To: <4CF65E03.103@ti.com>

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Nishanth Menon
> Sent: Wednesday, December 01, 2010 8:09 PM
> To: TAO HU
> Cc: TAO HU; linux-omap; Jean; Tony; Kevin; Vishwa
> Subject: Re: [PATCH 4/5 v2] OMAP3630: PM: Disable L2 cache while
> invalidating L2 cache
>
> TAO HU had written, on 12/01/2010 02:56 AM, the following:
> > Do we need to implement the same thing in bootloader?
> > I.e. Do we need to disable L2 prior invalidating L2 for  OMAP3630 1st
> boot up?
> Though out of context for this email list (linux kernel :)), I believe
> it wont hurt to do this as a standard procedure.

You should always invalidate the cache before enabling it. Now if
at the 1st boot-up if the ROM code / boot-loader is doing this,
you don't have do it.

At least from kernel point of it's responsibility of
boot-loaders/boot-straps to keep the caches invalidated. That's why
the generic kernel don't invalidate them before enabling them.

RMK has documeneted this. Read " 2. Loader Checks"
http://www.arm.linux.org.uk/developer/noboot-checklist/



Regards,
Santosh

  reply	other threads:[~2010-12-02  5:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 20:19 [PATCH 0/5 v2] OMAP: idle path errata fixes Nishanth Menon
2010-11-29 20:19 ` [PATCH 1/5 v2] OMAP3: PM: Update clean_l2 to use v7_flush_dcache_all Nishanth Menon
2010-11-29 20:19 ` [PATCH 2/5 v2] OMAP3: PM: Erratum i581 support: dll kick strategy Nishanth Menon
2010-11-29 20:19 ` [PATCH 3/5] OMAP3630: PM: Erratum i608: disable RTA Nishanth Menon
2010-11-30  6:07   ` Varadarajan, Charulatha
2010-11-30 14:15     ` Nishanth Menon
2010-11-29 20:19 ` [PATCH 4/5 v2] OMAP3630: PM: Disable L2 cache while invalidating L2 cache Nishanth Menon
2010-11-30  6:03   ` TAO HU
2010-11-30 14:18     ` Nishanth Menon
2010-12-01  8:56       ` TAO HU
2010-12-01 14:38         ` Nishanth Menon
2010-12-02  5:05           ` Santosh Shilimkar [this message]
2010-11-30  6:12   ` Varadarajan, Charulatha
2010-11-30 14:18     ` Nishanth Menon
2010-11-29 20:19 ` [PATCH 5/5] OMAP3630: PM: Erratum i583: disable coreoff if < ES1.2 Nishanth Menon

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=68d1d4807ed2c28d3b339571601a2a7f@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=jean.pihet@newoldbits.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nm@ti.com \
    --cc=taohu@motorola.com \
    --cc=tghk48@motorola.com \
    --cc=tony@atomide.com \
    --cc=vishwanath.bs@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.