From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm, omap2, sram: On HS/EMU devices, only 64K internal SRAM is available.
Date: Wed, 14 Oct 2015 15:20:23 -0700 [thread overview]
Message-ID: <20151014222022.GL10113@atomide.com> (raw)
In-Reply-To: <20151014174920.GE10113@atomide.com>
* Tony Lindgren <tony@atomide.com> [151014 10:56]:
> * Heiko Schocher <hs@denx.de> [151012 22:58]:
> > Of this, secure content (including PPA) uses initial
> > portion of the SRAM. This chunk is not (and shouldn't
> > be) accessible from the public code.
> >
> > The minimum size of this chunk (0x350) is used in this
> > patch. Available size is rounded off to 63K.
> >
> > Both values would require a change if size of secure
> > content grows beyond 0x350.
>
> Makes sense to me. And something similar is needed at least for
> dm814x to get rid of the imprecise abort during boot with
> commit bbeb92095159 ("ARM: 8422/1: enable imprecise aborts during
> early kernel startup") applied.
>
> Is this needed as a fix to the -rc cycle, or can this wait for
> v4.4?
Actually I think we may have a regression somwhere. If you look
at commit 8b9a2810b02e ("ARM: OMAP4+: Move SRAM data to DT")
this should all be handled by drivers/misc/sram.c nowadays.
So for most SoCs, we should completely skip the plat-omap/sram.c
code.
Regards,
Tony
next prev parent reply other threads:[~2015-10-14 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 5:54 [PATCH] arm, omap2, sram: On HS/EMU devices, only 64K internal SRAM is available Heiko Schocher
2015-10-14 17:49 ` Tony Lindgren
2015-10-14 22:20 ` Tony Lindgren [this message]
2015-10-14 23:54 ` Tony Lindgren
2015-10-15 4:26 ` Heiko Schocher
2015-10-15 3:57 ` Heiko Schocher
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=20151014222022.GL10113@atomide.com \
--to=tony@atomide.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).