From: Hollis Blanchard <hollis@penguinppc.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Add FSL SEC node to documentation
Date: Tue, 21 Mar 2006 13:28:55 -0600 [thread overview]
Message-ID: <1142969335.395.6.camel@basalt> (raw)
In-Reply-To: <1DBAE58F-2152-4074-B9BA-ADB1FA63DD1B@kernel.crashing.org>
On Tue, 2006-03-21 at 12:25 -0600, Kumar Gala wrote:
> On Mar 20, 2006, at 8:14 PM, Hollis Blanchard wrote:
>
> > On Monday 20 March 2006 19:59, Kim Phillips wrote:
> >> diff --git a/Documentation/powerpc/booting-without-of.txt
> > b/Documentation/powerpc/booting-without-of.txt
> >> index d02c649..72f3241 100644
> >> --- a/Documentation/powerpc/booting-without-of.txt
> >> +++ b/Documentation/powerpc/booting-without-of.txt
> >> @@ -1365,6 +1365,79 @@ platforms are moved over to use the flat
> >> };
> >>
> >>
> >> + g) Freescale SOC SEC Security Engines
> >> +
> >> + Required properties:
> >> +
> >> + - device_type : Should be "crypto"
> >> + - model : Model of the device. Should be "SEC1" or "SEC2"
> >> + - compatible : Should be "talitos"
> > [snip]
> >
> > Have you consulted with any other vendors regarding these
> > properties? I know
> > there is no IEEE1275 binding for these sorts of devices, but we can
> > at least
> > attempt to standardize it (even in the absence of the Open Firmware
> > Working
> > Group)...
>
> Beyond the device_type, I'm not sure if there is much more one could
> standardize one. The other fields that Kim spec'd are either generic
> OF fields (reg, interrupts, etc.) or specific to the Freescale devices.
The device_type and compatible properties are exactly what I'm talking
about.
-Hollis
next prev parent reply other threads:[~2006-03-21 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 1:59 [PATCH] powerpc: Add FSL SEC node to documentation Kim Phillips
2006-03-21 2:14 ` Hollis Blanchard
2006-03-21 17:48 ` Kim Phillips
2006-03-21 18:21 ` Kumar Gala
2006-03-22 1:10 ` Kim Phillips
2006-03-22 4:09 ` Paul Mackerras
2006-03-21 18:25 ` Kumar Gala
2006-03-21 19:28 ` Hollis Blanchard [this message]
2006-03-21 21:23 ` Paul Nasrat
2006-03-25 22:27 ` Doug Maxey
-- strict thread matches above, loose matches on Subject: below --
2006-03-22 20:39 Kim Phillips
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=1142969335.395.6.camel@basalt \
--to=hollis@penguinppc.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).