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 1/2] sata_rcar: Adjust and document device tree bindings
Date: Mon, 14 Oct 2013 17:13:54 +0100 [thread overview]
Message-ID: <20131014161353.GA19196@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1381765354-28440-2-git-send-email-valentine.barshak@cogentembedded.com>
On Mon, Oct 14, 2013 at 04:42:33PM +0100, Valentine Barshak wrote:
> This converts the R-Car SATA DT compatibility string to
> the <unit>-<soc> format which is the preferred one for
> all SH-Mobile devices. The DT bindings are documented.
>
> Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
> ---
> Documentation/devicetree/bindings/ata/sata_rcar.txt | 16 ++++++++++++++++
> arch/arm/boot/dts/r8a7779.dtsi | 2 +-
> drivers/ata/sata_rcar.c | 2 +-
> 3 files changed, 18 insertions(+), 2 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/ata/sata_rcar.txt
>
> diff --git a/Documentation/devicetree/bindings/ata/sata_rcar.txt b/Documentation/devicetree/bindings/ata/sata_rcar.txt
> new file mode 100644
> index 0000000..2465183
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/ata/sata_rcar.txt
> @@ -0,0 +1,16 @@
> +* Renesas R-Car SATA
> +
> +Required properties:
> +- compatible : must be "renesas,sata-r8a7779"
s/must be/should include/
> +- reg : address range of the SATA registers.
Also their size...
> +- interrupt-parent : interrupt parent controller phandle
This isn't required as such, as the interrupt-controller can be
inherited from the parent. As it's a standard auxiliary property I don't
think it needs to be documented here.
> +- interrupts : must consist of one interrupt specifier.
Is there only one interrupt generated by the device?
> +
> +Example:
> +
> +sata: sata@fc600000 {
> + compatible = "renesas,sata-r8a7779";
> + reg = <0xfc600000 0x2000>;
> + interrupt-parent = <&gic>;
> + interrupts = <0 100 0x4>;
> +};
> diff --git a/arch/arm/boot/dts/r8a7779.dtsi b/arch/arm/boot/dts/r8a7779.dtsi
> index da61d27..b1747f5 100644
> --- a/arch/arm/boot/dts/r8a7779.dtsi
> +++ b/arch/arm/boot/dts/r8a7779.dtsi
> @@ -201,7 +201,7 @@
> };
>
> sata: sata@fc600000 {
> - compatible = "renesas,rcar-sata";
> + compatible = "renesas,sata-r8a7779";
> reg = <0xfc600000 0x2000>;
> interrupt-parent = <&gic>;
> interrupts = <0 100 0x4>;
> diff --git a/drivers/ata/sata_rcar.c b/drivers/ata/sata_rcar.c
> index c2d95e9..c4cd738 100644
> --- a/drivers/ata/sata_rcar.c
> +++ b/drivers/ata/sata_rcar.c
> @@ -893,7 +893,7 @@ static const struct dev_pm_ops sata_rcar_pm_ops = {
> #endif
>
> static struct of_device_id sata_rcar_match[] = {
> - { .compatible = "renesas,rcar-sata", },
> + { .compatible = "renesas,sata-r8a7779", },
> {},
> };
Why is an existing compatible string being removed?
Please do not change existing strings, it will break any dts files that
are already in use.
While the new compatible string may be preferred, the old string should
be kept for compatibility.
Thanks,
Mark.
next prev parent reply other threads:[~2013-10-14 16:13 UTC|newest]
Thread overview: 17+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
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-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
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=20131014161353.GA19196@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).