From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@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,
Andreas Dannenberg <dannenberg-l0cyMroinI0@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>
Subject: Re: [PATCH 0/2] ARM: dts: dra7: Add OCMCRAM nodes
Date: Fri, 10 Jun 2016 03:43:17 -0700 [thread overview]
Message-ID: <20160610104316.GU22406@atomide.com> (raw)
In-Reply-To: <1462909782-14639-1-git-send-email-d-gerlach-l0cyMroinI0@public.gmane.org>
* Dave Gerlach <d-gerlach-l0cyMroinI0@public.gmane.org> [160510 12:52]:
> Hi,
> This series adds ocmcram nodes to use the mmio-sram driver to dra7.dtsi
> for use by all dra7xx and am57xx platforms. Not all ocmcram regions are
> present on every SoC variant so all possible nodes are added to the parent
> dtsi with the optional nodes marked "disabled". Board dts files that are
> known to have silicon supporting them can then enable them as needed.
>
> Patch two adds a "dummy" reserved region in the ocmcram1 node that acts
> as a placeholder for the region that is needed by secure software running
> on secure variants of the SoC. It is left as size zero with the intention
> that either:
>
> - The bootloader will step in and adjust the size based on what the
> secure software that is in use requires.
> - A board dts with specific requirements will override the node with
> appropriate size.
>
> The SRAM bindings in use are described in this patch [1] that is part of a
> series that adds SRAM regions for OMAP3 platforms.
Applying these two into omap-for-v4.8/dt thanks.
Tony
--
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
prev parent reply other threads:[~2016-06-10 10:43 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
2016-06-10 10:43 ` Tony Lindgren [this message]
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=20160610104316.GU22406@atomide.com \
--to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
--cc=d-gerlach-l0cyMroinI0@public.gmane.org \
--cc=dannenberg-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 \
/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).