From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Kim Phillips" <kim.phillips@freescale.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH v2] update crypto node definition and device tree instances
Date: Fri, 27 Jun 2008 22:29:59 -0700 [thread overview]
Message-ID: <fa686aa40806272229s795067d5he962c8a1750a260@mail.gmail.com> (raw)
In-Reply-To: <20080627115243.d76e0814.kim.phillips@freescale.com>
On Fri, Jun 27, 2008 at 9:52 AM, Kim Phillips
<kim.phillips@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@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@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.
next prev parent reply other threads:[~2008-06-28 5:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 16:52 [PATCH v2] update crypto node definition and device tree instances Kim Phillips
2008-06-28 5:29 ` Grant Likely [this message]
2008-06-28 23:37 ` Segher Boessenkool
2008-06-30 16:04 ` Kim Phillips
2008-06-30 16:55 ` Segher Boessenkool
2008-06-30 18:14 ` Kim Phillips
2008-06-30 21:19 ` Segher Boessenkool
2008-06-30 22:30 ` Kim Phillips
2008-06-30 23:27 ` Segher Boessenkool
2008-07-01 0:38 ` Kim Phillips
2008-06-30 15:56 ` 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=fa686aa40806272229s795067d5he962c8a1750a260@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=kim.phillips@freescale.com \
--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).