[PATCH v2] update crypto node definition and device tree instances
Grant Likely
grant.likely at secretlab.ca
Sat Jun 28 15:29:59 EST 2008
On Fri, Jun 27, 2008 at 9:52 AM, Kim Phillips
<kim.phillips at freescale.com> wrote:
> delete obsolete device-type property, delete model property
> (use compatible property instead), prepend "fsl," to Freescale
> specific properties. Add nodes to device trees that are missing them,
> and fix broken property values in other trees.
>
> Signed-off-by: Kim Phillips <kim.phillips at freescale.com>
Are there any drivers in mainline which use this node? Do these
changes break backwards compatibility with already deployed boards?
(I know; this patch doesn't change any code; but I'm asking whether
the driver will need to support both old and new bindings).
> ---
> diff --git a/arch/powerpc/boot/dts/mpc8272ads.dts b/arch/powerpc/boot/dts/mpc8272ads.dts
> index 46e2da3..9a3881d 100644
> --- a/arch/powerpc/boot/dts/mpc8272ads.dts
> +++ b/arch/powerpc/boot/dts/mpc8272ads.dts
> @@ -226,22 +226,15 @@
> compatible = "fsl,mpc8272-pic", "fsl,cpm2-pic";
> };
>
> -/* May need to remove if on a part without crypto engine */
> crypto at 30000 {
> - device_type = "crypto";
> - model = "SEC2";
> - compatible = "fsl,mpc8272-talitos-sec2",
> - "fsl,talitos-sec2",
> - "fsl,talitos",
> - "talitos";
> + compatible = "fsl,sec1.0";
Should really be encoding the SoC model in the compatible property.
At the very least, compatible should be:
compatible = "fsl,mpc8272-sec", "fsl,sec1.0";
I'm really don't like "fsl,sec1.0" or any of the variants as a
compatible property either because it can easily be abused (it's not
anchored to a specific physical part so the meaning can shift over
time); but that is another argument and it is well documented in other
email threads (http://thread.gmane.org/gmane.linux.ports.ppc64.devel/38977/focus=39147)
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
More information about the Linuxppc-dev
mailing list