devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dannenberg <dannenberg-l0cyMroinI0@public.gmane.org>
To: Dave Gerlach <d-gerlach-l0cyMroinI0@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH 2/2] ARM: dts: dra7: Add ti,secure-ram node to ocmcram1 node
Date: Wed, 11 May 2016 08:09:13 -0500	[thread overview]
Message-ID: <20160511130913.GS20461@borg.dal.design.ti.com> (raw)
In-Reply-To: <1462909782-14639-3-git-send-email-d-gerlach-l0cyMroinI0@public.gmane.org>

On Tue, May 10, 2016 at 02:49:42PM -0500, Dave Gerlach wrote:
> Secure variants of DRA7xx and AM57xx SoCs may need to reserve a region
> of the SRAM for use by secure software. To account for this, add a child
> node to the ocmcram1 node that will act as a placeholder at the start
> of the SRAM for the reserved region of memory that may be required
> by secure services. The node is added with size 0 so that by default
> parts will have the full space available but the bootloader or board dts
> file is able to resize the node as needed depending on how much reserved
> space is needed, if any, so end users of the ocmcram1 region on HS parts
> must be aware that a smaller amount of SRAM than expected may be available.
> 
> Signed-off-by: Dave Gerlach <d-gerlach-l0cyMroinI0@public.gmane.org>

Reviewed-by: Andreas Dannenberg <dannenberg-l0cyMroinI0@public.gmane.org>

--
Andreas Dannenberg
Texas Instruments Inc
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-05-11 13:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 19:49 [PATCH 0/2] ARM: dts: dra7: Add OCMCRAM nodes Dave Gerlach
     [not found] ` <1462909782-14639-1-git-send-email-d-gerlach-l0cyMroinI0@public.gmane.org>
2016-05-10 19:49   ` [PATCH 1/2] ARM: dts: dra7: Add ocmcram nodes Dave Gerlach
     [not found]     ` <1462909782-14639-2-git-send-email-d-gerlach-l0cyMroinI0@public.gmane.org>
2016-05-11 13:07       ` Andreas Dannenberg
2016-05-10 19:49   ` [PATCH 2/2] ARM: dts: dra7: Add ti,secure-ram node to ocmcram1 node Dave Gerlach
     [not found]     ` <1462909782-14639-3-git-send-email-d-gerlach-l0cyMroinI0@public.gmane.org>
2016-05-11 13:09       ` Andreas Dannenberg [this message]
2016-06-10 10:43   ` [PATCH 0/2] ARM: dts: dra7: Add OCMCRAM nodes Tony Lindgren

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=20160511130913.GS20461@borg.dal.design.ti.com \
    --to=dannenberg-l0cymroini0@public.gmane.org \
    --cc=d-gerlach-l0cyMroinI0@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=s-anna-l0cyMroinI0@public.gmane.org \
    --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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).