From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: Valentine Barshak <valentine.barshak@cogentembedded.com>,
linux-sh@vger.kernel.org, linux-ide@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>, Tejun Heo <tj@kernel.org>,
Vladimir Barinov <vladimir.barinov@cogentembedded.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] ata: sata_rcar: Add RCAR Gen2 SATA PHY support
Date: Fri, 11 Oct 2013 19:25:35 +0000 [thread overview]
Message-ID: <52585E6F.40903@cogentembedded.com> (raw)
In-Reply-To: <20131011010032.GA13809@verge.net.au>
Hello.
On 11-10-2013 3:00, Simon Horman wrote:
> [ CCed devicetree@vger.kernel.org as this involves DT compatibility strings ]
Note that I did CC then-existing devicetree-discuss list when posting the
original driver but we got no feedback from there. That's why the binding
documentation is missing.
>> RCAR Gen2 SoC has a different phy which is not compatible with
Hm, the SoCs family is called R-Car, is it so hard to remember? :-)
>> the older H1/M1 versions. This adds OF/platform device table
>> and PHY initialization callbacks for H2/M2 (Gen2) SoC.
[...]
>> PHY initialization method is chosen based on the device id.
>> Default PHY settings are applied for Gen2 SoC, which should
>> suit the available Gen2 boards.
>> Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
[skip overquoating, grr :-]
>> @@ -770,8 +823,34 @@ static void sata_rcar_init_controller(struct ata_host *host)
>> iowrite32(ATAPI_INT_ENABLE_SATAINT, base + ATAPI_INT_ENABLE_REG);
>> }
>>
>> +static struct of_device_id sata_rcar_match[] = {
>> + {
>> + .compatible = "renesas,rcar-sata",
>> + .data = (void *)RCAR_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);
>> +
>> +static const struct platform_device_id sata_rcar_id_table[] = {
>> + { "sata_rcar", RCAR_SATA },
>> + { "sata-r8a7790", RCAR_GEN2_SATA },
>> + { "sata-r8a7791", RCAR_GEN2_SATA },
>> + { },
>> +};
>> +MODULE_DEVICE_TABLE(platform, sata_rcat_id_table);
>> +
> I think it would be better to add sata-r8a7779 and
> sata-r8a7778 to handle the GEN1 hardware and deprecate rcar-sata.
R8A7778 doesn't have the SATA controller AFAIR.
> Less importantly I think it would be better to name RCAR_SATA
> as RCAR_GEN1_SATA.
Now that we have Gen2, yes.
WBR, Sergei
prev parent reply other threads:[~2013-10-11 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 19:08 [PATCH] ata: sata_rcar: Add RCAR Gen2 SATA PHY support Valentine Barshak
2013-10-11 1:00 ` Simon Horman
2013-10-11 9:41 ` Mark Rutland
2013-10-11 10:54 ` Valentine
2013-10-11 14:47 ` Mark Rutland
2013-10-11 15:14 ` Valentine
2013-10-11 9:53 ` Valentine
2013-10-11 19:25 ` Sergei Shtylyov [this message]
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=52585E6F.40903@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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=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).