From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
devicetree@vger.kernel.org, linux-sh@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: dts: Add shmobile platform device tree bindings documentation
Date: Fri, 29 Aug 2014 09:34:57 +0900 [thread overview]
Message-ID: <20140829003456.GM16165@verge.net.au> (raw)
In-Reply-To: <1409213120-5291-1-git-send-email-geert+renesas@glider.be>
On Thu, Aug 28, 2014 at 10:05:20AM +0200, Geert Uytterhoeven wrote:
> Add Renesas SH-Mobile, R-Mobile, and R-Car Platform Device Tree Bindings
> Documentation, listing supported SoCs and boards.
>
> This allows to use checkpatch to validate DTSes referring to Renesas
> shmobile SoCs, and boards containing those SoCs.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Thanks Geert, this looks good to me.
Is it for me to pick up?
If so I would prefer a slightly re-structured title:
ARM: shmobile: Add platform device tree bindings documentation
> ---
> v2:
> - Drop RFC
> - Move sh7372/sh73a0 up, before r8a73a4
> - Add r8a7793/Gose
> - Drop bogus EMEV2 before KZM9D board name
> - Drop armadillo-reference, as it's on its way out
> ---
> Documentation/devicetree/bindings/arm/shmobile.txt | 71 ++++++++++++++++++++++
> 1 file changed, 71 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/shmobile.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/shmobile.txt b/Documentation/devicetree/bindings/arm/shmobile.txt
> new file mode 100644
> index 000000000000..5d1c5c0085dc
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/shmobile.txt
> @@ -0,0 +1,71 @@
> +Renesas SH-Mobile, R-Mobile, and R-Car Platform Device Tree Bindings
> +--------------------------------------------------------------------
> +
> +SoCs:
> +
> + - Emma Mobile EV2
> + compatible = "renesas,emev2"
> + - RZ/A1H (R7S72100)
> + compatible = "renesas,r7s72100"
> + - SH-Mobile AP4 (R8A73720/SH7372)
> + compatible = "renesas,sh7372"
> + - SH-Mobile AG5 (R8A73A00/SH73A0)
> + compatible = "renesas,sh73a0"
> + - R-Mobile APE6 (R8A73A40)
> + compatible = "renesas,r8a73a4"
> + - R-Mobile A1 (R8A77400)
> + compatible = "renesas,r8a7740"
> + - R-Car M1A (R8A77781)
> + compatible = "renesas,r8a7778"
> + - R-Car H1 (R8A77790)
> + compatible = "renesas,r8a7779"
> + - R-Car H2 (R8A77900)
> + compatible = "renesas,r8a7790"
> + - R-Car M2-W (R8A77910)
> + compatible = "renesas,r8a7791"
> + - R-Car V2H (R8A77920)
> + compatible = "renesas,r8a7792"
> + - R-Car M2-N (R8A77930)
> + compatible = "renesas,r8a7793"
> + - R-Car E2 (R8A77940)
> + compatible = "renesas,r8a7794"
> +
> +
> +Boards:
> +
> + - Alt
> + compatible = "renesas,alt", "renesas,r8a7794"
> + - APE6-EVM
> + compatible = "renesas,ape6evm", "renesas,r8a73a4"
> + - APE6-EVM - Reference Device Tree Implementation
> + compatible = "renesas,ape6evm-reference", "renesas,r8a73a4"
> + - Atmark Techno Armadillo-800 EVA
> + compatible = "renesas,armadillo800eva"
> + - BOCK-W
> + compatible = "renesas,bockw", "renesas,r8a7778"
> + - BOCK-W - Reference Device Tree Implementation
> + compatible = "renesas,bockw-reference", "renesas,r8a7778"
> + - Genmai (RTK772100BC00000BR)
> + compatible = "renesas,genmai", "renesas,r7s72100"
> + - Gose
> + compatible = "renesas,gose", "renesas,r8a7793"
> + - Henninger
> + compatible = "renesas,henninger", "renesas,r8a7791"
> + - Koelsch (RTP0RC7791SEB00010S)
> + compatible = "renesas,koelsch", "renesas,r8a7791"
> + - KZM9D
> + compatible = "renesas,kzm9d", "renesas,emev2"
> + - KZM-A9-GT
> + compatible = "renesas,kzm9g", "renesas,sh73a0"
> + - KZM-A9-GT - Reference Device Tree Implementation
> + compatible = "renesas,kzm9g-reference", "renesas,sh73a0"
> + - Lager (RTP0RC7790SEB00010S)
> + compatible = "renesas,lager", "renesas,r8a7790"
> + - Mackerel (R0P7372LC0016RL, AP4 EVM 2nd)
> + compatible = "renesas,mackerel"
> + - Marzen
> + compatible = "renesas,marzen", "renesas,r8a7779"
> +
> +Note: Reference Device Tree Implementations are temporary implementations
> + to ease the migration from platform devices to Device Tree, and are
> + intended to be removed in the future.
> --
> 1.9.1
>
next prev parent reply other threads:[~2014-08-29 0:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 8:05 [PATCH v2] ARM: dts: Add shmobile platform device tree bindings documentation Geert Uytterhoeven
2014-08-29 0:34 ` Simon Horman [this message]
2014-08-29 8:26 ` Geert Uytterhoeven
2014-09-01 0:55 ` Simon Horman
2014-09-01 1:45 ` Simon Horman
2014-09-01 7:17 ` Geert Uytterhoeven
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=20140829003456.GM16165@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@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;
as well as URLs for NNTP newsgroup(s).