linux/Documentation
Kim Phillips 7dfc2179ec crypto: caam - de-CHIP-ify device tree compatibles
- all the integration parameters have been captured by the binding.
- the block name really uniquely identifies this hardware.

Some advocate putting SoC names everywhere in case software needs
to work around some chip-specific bug, but more precise SoC
information already exists in SVR, and board information already
exists in the top-level device tree node.

Note that sometimes the SoC name is a worse identifier than the
block version, as the block version can change between revisions
of the same SoC.

As a matter of historical reference, neither SEC versions 2.x
nor 3.x (driven by talitos) ever needed CHIP references.

Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
Cc: Kumar Gala <kumar.gala@freescale.com>
Cc: Scott Wood <scottwood@freescale.com>
Acked-off-by: Grant Likely <grant.likely@secretlab.ca>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2011-03-27 10:45:18 +08:00
..
2011-03-10 08:52:07 +01:00
2010-02-24 13:51:32 +01:00
2011-03-24 13:54:24 +00:00
2010-07-11 22:17:45 +02:00
2011-03-09 15:43:38 -08:00
2010-04-08 11:34:34 +02:00
2011-03-07 13:20:05 -08:00
2010-03-10 17:09:33 -05:00
2010-07-19 10:56:54 +02:00
2010-03-16 11:47:56 +01:00
2010-08-02 15:35:10 +10:00