From: Mark Rutland <mark.rutland@arm.com>
To: Valentine Barshak <valentine.barshak@cogentembedded.com>
Cc: "linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Vladimir Barinov <vladimir.barinov@cogentembedded.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH 2/2] sata_rcar: Add R-Car Gen2 SATA support
Date: Mon, 14 Oct 2013 16:26:03 +0000 [thread overview]
Message-ID: <20131014162603.GB19196@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1381765354-28440-3-git-send-email-valentine.barshak@cogentembedded.com>
On Mon, Oct 14, 2013 at 04:42:34PM +0100, Valentine Barshak wrote:
> R-Car Gen2 SoCs have a different PHY which is not compatible
> with the older R-Car H1 (R8A7779) version.
> This adds OF/platform device id tables and PHY initialization
> callbacks for the following Gen2 SoCs:
> * R-Car H2: R8A7790;
> * R-Car M2: R8A7791.
>
> PHY initialization method is chosen, based on the device id.
> Default PHY settings are applied for Gen2 SoCs, which should
> suit the Gen2 boards available.
>
> The R8A7779 platform code is modified to use "sata-r8a7779"
> device id.
>
> Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
> ---
> .../devicetree/bindings/ata/sata_rcar.txt | 5 +-
> arch/arm/mach-shmobile/clock-r8a7779.c | 2 +-
> arch/arm/mach-shmobile/setup-r8a7779.c | 2 +-
> drivers/ata/sata_rcar.c | 112 ++++++++++++++++++---
> 4 files changed, 102 insertions(+), 19 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/ata/sata_rcar.txt b/Documentation/devicetree/bindings/ata/sata_rcar.txt
> index 2465183..b5a41bf 100644
> --- a/Documentation/devicetree/bindings/ata/sata_rcar.txt
> +++ b/Documentation/devicetree/bindings/ata/sata_rcar.txt
> @@ -1,7 +1,10 @@
> * Renesas R-Car SATA
>
> Required properties:
> -- compatible : must be "renesas,sata-r8a7779"
> +- compatible : must be one of the following:
s/must be/should contain/
> + - "renesas,sata-r8a7779" for R-Car H1
> + - "renesas,sata-r8a7790" for R-Car H2
> + - "renesas,sata-r8a7791" for R-Car M2
How do renesas,sata-r8a7790 and renesas,sata-r8a7791 differ?
> - reg : address range of the SATA registers.
It's a size too...
> - interrupt-parent : interrupt parent controller phandle
Not required.
[...]
> +static struct of_device_id sata_rcar_match[] = {
> + {
> + .compatible = "renesas,sata-r8a7779",
> + .data = (void *)RCAR_GEN1_SATA,
> + },
> + {
> + .compatible = "renesas,sata-r8a7790",
> + .data = (void *)RCAR_GEN2_SATA
> + },
> + {
> + .compatible = "renesas,sata-r8a7791",
> + .data = (void *)RCAR_GEN2_SATA
> + },
> + {},
> +};
> +MODULE_DEVICE_TABLE(of, sata_rcar_match);
Are the renesas,sata-r8a779x variants identical?
If so, why the two strings?
Could we not require sata-r8a7791 devices to have "sata-r8a7790" in the
compatible list:
compatible = "sata-r8a7791", "sata-r8a7790";
That way we can match on "sata-r8a7791" if we want to later, but don't
need code for it now.
Thanks,
Mark.
next prev parent reply other threads:[~2013-10-14 16:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 15:42 [PATCH 0/2] sata_rcar: Adjust DT bindings and add R-Car Gen2 PHY support Valentine Barshak
2013-10-14 15:42 ` [PATCH 1/2] sata_rcar: Adjust and document device tree bindings Valentine Barshak
2013-10-14 16:13 ` Mark Rutland
2013-10-14 17:19 ` Valentine
2013-10-15 0:25 ` Simon Horman
2013-10-15 8:15 ` Mark Rutland
2013-10-14 15:42 ` [PATCH 2/2] sata_rcar: Add R-Car Gen2 SATA support Valentine Barshak
2013-10-14 16:26 ` Mark Rutland [this message]
2013-10-14 17:58 ` Valentine
2013-10-14 18:15 ` Laurent Pinchart
2013-10-14 21:22 ` Valentine
2013-10-15 0:23 ` Simon Horman
2013-10-15 0:32 ` Laurent Pinchart
2013-10-16 6:10 ` Simon Horman
2013-10-15 10:20 ` [PATCH 0/2] sata_rcar: Adjust DT bindings and add R-Car Gen2 PHY support (take 2) Valentine Barshak
2013-10-15 10:20 ` [PATCH 1/2] sata_rcar: Adjust and document device tree bindings Valentine Barshak
2013-10-16 0:42 ` Simon Horman
2013-10-15 10:20 ` [PATCH 2/2] sata_rcar: Add R-Car Gen2 SATA PHY support Valentine Barshak
2013-10-15 12:40 ` [PATCH 0/2] sata_rcar: Adjust DT bindings and add R-Car Gen2 PHY support (take 2) Tejun Heo
2013-10-16 12:05 ` [PATCH 0/2] sata_rcar: Adjust DT bindings and add R-Car Gen2 PHY support (take 3) Valentine Barshak
2013-10-16 12:06 ` [PATCH 1/2] sata_rcar: Adjust and document device tree bindings Valentine Barshak
2013-10-16 12:06 ` [PATCH 2/2] sata_rcar: Add R-Car Gen2 SATA PHY support Valentine Barshak
2013-10-29 4:59 ` Simon Horman
2013-10-29 8:24 ` Kumar Gala
2013-10-29 8:44 ` Simon Horman
2013-10-29 17:19 ` Kumar Gala
2013-10-30 0:28 ` Simon Horman
2013-10-30 7:05 ` Kumar Gala
2013-10-30 17:07 ` Valentine
2013-10-29 8:46 ` 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=20131014162603.GB19196@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tj@kernel.org \
--cc=valentine.barshak@cogentembedded.com \
--cc=vladimir.barinov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).