From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: cache-l2x0: add resume entry for l2 in secure mode
Date: Thu, 29 Sep 2011 16:06:02 +0530 [thread overview]
Message-ID: <4E844A12.7050507@ti.com> (raw)
In-Reply-To: <20110929102213.GB7453@e102568-lin.cambridge.arm.com>
On Thursday 29 September 2011 03:52 PM, Lorenzo Pieralisi wrote:
> On Thu, Sep 29, 2011 at 06:35:58AM +0100, Santosh Shilimkar wrote:
>> Barry,
>>
>> On Monday 26 September 2011 08:56 AM, Barry Song wrote:
>>> we save the l2x0 registers at the first initialization, and platform codes
>>> can get them to restore l2x0 status after wakeup.
>>>
>>> Cc: Shawn Guo <shawn.guo@linaro.org>
>>> Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
>>> Signed-off-by: Barry Song <Baohua.Song@csr.com>
>>> ---
>
> [...]
>
>>> +
>>> +struct l2x0_regs {
>>> + unsigned long aux_ctrl;
>>> + /*
>>> + * Whether the following registers need to be saved/restored
>>> + * depends on platform
>>> + */
>>> + unsigned long tag_latency;
>>> + unsigned long data_latency;
>>> + unsigned long filter_start;
>>> + unsigned long filter_end;
>>> +};
>>> +
>> You are missing POR register here which is available on
>> PL310 versions. You should add that.
>>
>
> In latest versions there are Prefetch and Power control registers, but
> it depends on the revision. What should we do in this case Santosh ?
> PCR is a superset of POR from r3p0 onwards, but Power control ? Leave it
> to platform code ?
>
Good point Lorenzo.
C code resume can be fixed by marking the validity based
on PL310 revision register.
The asm code restore with MMU OFF code, would be handled
with platform code with this patch and platform code can choose
restore of only supported registers.
Regards
Santosh
next prev parent reply other threads:[~2011-09-29 10:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 3:26 [PATCH v2] ARM: cache-l2x0: add resume entry for l2 in secure mode Barry Song
2011-09-29 5:35 ` Santosh Shilimkar
2011-09-29 5:49 ` Shawn Guo
2011-09-29 5:59 ` Barry Song
2011-09-29 10:22 ` Lorenzo Pieralisi
2011-09-29 10:36 ` Santosh Shilimkar [this message]
2011-09-29 9:28 ` Shawn Guo
2011-09-29 9:24 ` Russell King - ARM Linux
2011-09-29 12:44 ` Shawn Guo
2011-09-29 12:50 ` Russell King - ARM Linux
2011-09-29 13:12 ` Shawn Guo
2011-09-29 13:26 ` Russell King - ARM Linux
2011-09-29 13:50 ` Shawn Guo
2011-09-29 9:44 ` Barry Song
2011-09-29 13:57 ` Shawn Guo
2011-09-29 14:55 ` Barry Song
2011-09-29 15:07 ` Shawn Guo
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=4E844A12.7050507@ti.com \
--to=santosh.shilimkar@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;
as well as URLs for NNTP newsgroup(s).