devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ata: sata_rcar: add gen[123] fallback compatibility strings
Date: Tue, 8 Mar 2016 10:33:12 +0900	[thread overview]
Message-ID: <20160308013312.GA19565@verge.net.au> (raw)
In-Reply-To: <1457400642-19377-1-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>

[CC devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org]

On Tue, Mar 08, 2016 at 10:30:42AM +0900, Simon Horman wrote:
> Add fallback compatibility string for R-Car Gen 1, 2 and 3.
> 
> In the case of Renesas R-Car hardware we know that there are generations of
> SoCs, e.g. Gen 1 and 2. But beyond that its not clear what the relationship
> between IP blocks might be. For example, I believe that r8a7779 is older
> than r8a7778 but that doesn't imply that the latter is a descendant of the
> former or vice versa.
> 
> We can, however, by examining the documentation and behaviour of the
> hardware at run-time observe that the current driver implementation appears
> to be compatible with the IP blocks on SoCs within a given generation.
> 
> For the above reasons and convenience when enabling new SoCs a
> per-generation fallback compatibility string scheme being adopted for
> drivers for Renesas SoCs.
> 
> Signed-off-by: Simon Horman <horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
> ---
> Based on libata/for-next
> ---
>  Documentation/devicetree/bindings/ata/sata_rcar.txt | 15 ++++++++++++---
>  drivers/ata/sata_rcar.c                             | 12 ++++++++++++
>  2 files changed, 24 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/ata/sata_rcar.txt b/Documentation/devicetree/bindings/ata/sata_rcar.txt
> index 0764f9ab63dc..b44048176938 100644
> --- a/Documentation/devicetree/bindings/ata/sata_rcar.txt
> +++ b/Documentation/devicetree/bindings/ata/sata_rcar.txt
> @@ -1,14 +1,23 @@
>  * Renesas R-Car SATA
>  
>  Required properties:
> -- compatible		: should contain one of the following:
> +- compatible		: should contain one or more of the following:
>  			  - "renesas,sata-r8a7779" for R-Car H1
> -			    ("renesas,rcar-sata" is deprecated)
>  			  - "renesas,sata-r8a7790-es1" for R-Car H2 ES1
>  			  - "renesas,sata-r8a7790" for R-Car H2 other than ES1
>  			  - "renesas,sata-r8a7791" for R-Car M2-W
>  			  - "renesas,sata-r8a7793" for R-Car M2-N
>  			  - "renesas,sata-r8a7795" for R-Car H3
> +			  - "renesas,rcar-gen1-sata" for a generic R-Car Gen1 compatible device
> +			  - "renesas,rcar-gen2-sata" for a generic R-Car Gen2 compatible device
> +			  - "renesas,rcar-gen3-sata" for a generic R-Car Gen3 compatible device
> +			  - "renesas,rcar-sata" is deprecated
> +
> +			  When compatible with the generic version, nodes
> +			  must list the SoC-specific version corresponding
> +			  to the platform first followed by the generic
> +			  version.
> +
>  - reg			: address and length of the SATA registers;
>  - interrupts		: must consist of one interrupt specifier.
>  - clocks		: must contain a reference to the functional clock.
> @@ -16,7 +25,7 @@ Required properties:
>  Example:
>  
>  sata0: sata@ee300000 {
> -	compatible = "renesas,sata-r8a7791";
> +	compatible = "renesas,sata-r8a7791", "renesas,rcar-gen2-sata";
>  	reg = <0 0xee300000 0 0x2000>;
>  	interrupt-parent = <&gic>;
>  	interrupts = <0 105 IRQ_TYPE_LEVEL_HIGH>;
> diff --git a/drivers/ata/sata_rcar.c b/drivers/ata/sata_rcar.c
> index f72d601e300a..09d4ba3f0bc4 100644
> --- a/drivers/ata/sata_rcar.c
> +++ b/drivers/ata/sata_rcar.c
> @@ -858,6 +858,18 @@ static struct of_device_id sata_rcar_match[] = {
>  		.compatible = "renesas,sata-r8a7795",
>  		.data = (void *)RCAR_GEN2_SATA
>  	},
> +	{
> +		.compatible = "renesas,rcar-gen1-sata",
> +		.data = (void *)RCAR_GEN1_SATA
> +	},
> +	{
> +		.compatible = "renesas,rcar-gen2-sata",
> +		.data = (void *)RCAR_GEN2_SATA
> +	},
> +	{
> +		.compatible = "renesas,rcar-gen3-sata",
> +		.data = (void *)RCAR_GEN2_SATA
> +	},
>  	{ },
>  };
>  MODULE_DEVICE_TABLE(of, sata_rcar_match);
> -- 
> 2.1.4
> 
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2016-03-08  1:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1457400642-19377-1-git-send-email-horms+renesas@verge.net.au>
     [not found] ` <1457400642-19377-1-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2016-03-08  1:33   ` Simon Horman [this message]
2016-03-08  8:37     ` [PATCH] ata: sata_rcar: add gen[123] fallback compatibility strings Geert Uytterhoeven
2016-03-09  2:24       ` Simon Horman

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=20160308013312.GA19565@verge.net.au \
    --to=horms-/r6kz+ddxgppr4jqbcensq@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).