public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Viresh Kumar <viresh.kumar@st.com>
Cc: devicetree-discuss@ozlabs.org, artem.bityutskiy@linux.intel.com,
	spear-devel@list.st.com, linux-mtd@lists.infradead.org,
	viresh.linux@gmail.com, sr@denx.de
Subject: Re: [PATCH] mtd: spear-smi: Update compatible property
Date: Fri, 23 Mar 2012 09:10:25 -0500	[thread overview]
Message-ID: <4F6C8451.1020005@gmail.com> (raw)
In-Reply-To: <97859bb4d86d008968a784339be8567094c487a1.1332492461.git.viresh.kumar@st.com>

On 03/23/2012 03:48 AM, Viresh Kumar wrote:
> SPEAr SMI controller version is same for all SPEAr machines. Thus we don't need
> per machine compatible property in driver.

Until the next chip...

> Thus this patch updates compatible entry to: "st,spear-smi", so that it
> works for all SPEAr machines.
> 

There is no reason all machines can't use "st,spear600-smi" in their
dts. It doesn't have to be a spear600, just compatible with it. Really
you want the string to be the oldest SOC the block is in and then newer
SOCs can claim compatibility with the old version.

This is also bad that you would break any existing dtb's out there. This
is probably not a concern yet since it's all new and in transition, but
down the road this is something that can't be done.

Rob

> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
> ---
>  .../devicetree/bindings/mtd/spear_smi.txt          |    4 ++--
>  drivers/mtd/devices/spear_smi.c                    |    2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/mtd/spear_smi.txt b/Documentation/devicetree/bindings/mtd/spear_smi.txt
> index 7248aad..80dfd96 100644
> --- a/Documentation/devicetree/bindings/mtd/spear_smi.txt
> +++ b/Documentation/devicetree/bindings/mtd/spear_smi.txt
> @@ -1,7 +1,7 @@
>  * SPEAr SMI
>  
>  Required properties:
> -- compatible : "st,spear600-smi"
> +- compatible : "st,spear-smi"
>  - reg : Address range of the mtd chip
>  - #address-cells, #size-cells : Must be present if the device has sub-nodes
>    representing partitions.
> @@ -16,7 +16,7 @@ Optional properties:
>  Example:
>  
>  	smi: flash@fc000000 {
> -		compatible = "st,spear600-smi";
> +		compatible = "st,spear-smi";
>  		#address-cells = <1>;
>  		#size-cells = <1>;
>  		reg = <0xfc000000 0x1000>;
> diff --git a/drivers/mtd/devices/spear_smi.c b/drivers/mtd/devices/spear_smi.c
> index bebce11..f392594 100644
> --- a/drivers/mtd/devices/spear_smi.c
> +++ b/drivers/mtd/devices/spear_smi.c
> @@ -1113,7 +1113,7 @@ int spear_smi_resume(struct platform_device *pdev)
>  
>  #ifdef CONFIG_OF
>  static const struct of_device_id spear_smi_id_table[] = {
> -	{ .compatible = "st,spear600-smi" },
> +	{ .compatible = "st,spear-smi" },
>  	{}
>  };
>  MODULE_DEVICE_TABLE(of, spear_smi_id_table);

  reply	other threads:[~2012-03-23 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  8:48 [PATCH] mtd: spear-smi: Update compatible property Viresh Kumar
2012-03-23 14:10 ` Rob Herring [this message]
2012-03-25  7:25   ` viresh kumar

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=4F6C8451.1020005@gmail.com \
    --to=robherring2@gmail.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=spear-devel@list.st.com \
    --cc=sr@denx.de \
    --cc=viresh.kumar@st.com \
    --cc=viresh.linux@gmail.com \
    /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