From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 3/5] ARM: EXYNOS: Add support for Exynos secure firmware
Date: Wed, 26 Dec 2012 08:53:50 +0000 [thread overview]
Message-ID: <201212260853.50852.arnd@arndb.de> (raw)
In-Reply-To: <CAGsJ_4yjm-CE6iJC+pAT=aiNAf0dpANH49e2OD+CqBG+JveGfQ@mail.gmail.com>
On Wednesday 26 December 2012, Barry Song wrote:
> > / {
> > /* ... */
> >
> > firmware at 0203F000 {
> > compatible = "samsung,secure-firmware";
> > reg = <0x0203F000 0x1000>;
> > };
> >
> > /* ... */
> > };
>
> well. amazing, dts is used to describle hardware details, here the
> firmware is just a software and reg is the memory the firmware will
> use. is this something againest the dt rule?
> but it is really simple.
We have for a long time had DT bindings to describe firmware, e.g.
on IBM Power systems, I think this is fine.
Arnd
next prev parent reply other threads:[~2012-12-26 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 15:51 [PATCH v4 0/5] ARM: EXYNOS: Add secure firmware support Tomasz Figa
2012-11-22 15:51 ` [PATCH v4 1/5] ARM: Add interface for registering and calling firmware-specific operations Tomasz Figa
2012-12-26 8:00 ` Barry Song
2012-11-22 15:51 ` [PATCH v4 2/5] ARM: EXYNOS: Add support for secure monitor calls Tomasz Figa
2012-11-22 15:51 ` [PATCH v4 3/5] ARM: EXYNOS: Add support for Exynos secure firmware Tomasz Figa
2012-12-26 8:17 ` Barry Song
2012-12-26 8:53 ` Arnd Bergmann [this message]
2012-11-22 15:51 ` [PATCH v4 4/5] ARM: EXYNOS: Add IO mapping for non-secure SYSRAM Tomasz Figa
2012-11-22 15:51 ` [PATCH v4 5/5] ARM: EXYNOS: Add secure firmware support to secondary CPU bring-up Tomasz Figa
2012-11-24 2:21 ` [PATCH v4 0/5] ARM: EXYNOS: Add secure firmware support Kukjin Kim
2012-11-28 15:44 ` Tomasz Figa
2012-11-30 10:58 ` Kukjin Kim
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=201212260853.50852.arnd@arndb.de \
--to=arnd@arndb.de \
--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