From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms+renesas@verge.net.au>,
David Miller <davem@davemloft.net>
Cc: Magnus Damm <magnus.damm@gmail.com>,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] dt-bindings: net: sh_eth: add R-Car Gen[12] fallback compatibility strings
Date: Tue, 17 Oct 2017 13:14:51 +0300 [thread overview]
Message-ID: <337f227a-3019-4e82-a0cb-1328d7036df7@cogentembedded.com> (raw)
In-Reply-To: <20171017074747.24159-2-horms+renesas@verge.net.au>
Hello!
On 10/17/2017 10:47 AM, Simon Horman wrote:
> Add fallback compatibility strings for R-Car Gen 1 and 2.
>
> In the case of Renesas R-Car hardware we know that there are generations of
> SoCs, f.e. Gen 1 and 2. But beyond that its not clear what the relationship
> between IP blocks might be. For example, I believe that r8a7790 is older
> than r8a7791 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.
>
> Note that R-Car Gen2 and RZ/G1 have many compatible IP blocks. The
> approach that has been consistently taken for other IP blocks is to name
> common code, compatibility strings and so on after Rcar Gen2.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Reviewed-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> ---
> Documentation/devicetree/bindings/net/sh_eth.txt | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/net/sh_eth.txt b/Documentation/devicetree/bindings/net/sh_eth.txt
> index 0115c85a2425..48cab94dd056 100644
> --- a/Documentation/devicetree/bindings/net/sh_eth.txt
> +++ b/Documentation/devicetree/bindings/net/sh_eth.txt
> @@ -4,7 +4,8 @@ This file provides information on what the device node for the SH EtherMAC
> interface contains.
>
> Required properties:
> -- compatible: "renesas,gether-r8a7740" if the device is a part of R8A7740 SoC.
> +- compatible: Must contain one or more of the following:
> + "renesas,gether-r8a7740" if the device is a part of R8A7740 SoC.
> "renesas,ether-r8a7743" if the device is a part of R8A7743 SoC.
> "renesas,ether-r8a7745" if the device is a part of R8A7745 SoC.
> "renesas,ether-r8a7778" if the device is a part of R8A7778 SoC.
> @@ -14,6 +15,14 @@ Required properties:
> "renesas,ether-r8a7793" if the device is a part of R8A7793 SoC.
> "renesas,ether-r8a7794" if the device is a part of R8A7794 SoC.
> "renesas,ether-r7s72100" if the device is a part of R7S72100 SoC.
> + "renesas,rcar-gen1-ether" for a generic R-Car Gen1 device.
> + "renesas,rcar-gen2-ether" for a generic R-Car Gen2 or RZ/G1
> + device.
> +
> + When compatible with the generic version nodes must list
> + the SoC-specific version corresponding to the platform
> + first followed by the generic version.
> +
The original text uses the different indentation, tab and then spaces),
while you use only spaces here (but not above).
> - reg: offset and length of (1) the E-DMAC/feLic register block (required),
> (2) the TSU register block (optional).
> - interrupts: interrupt specifier for the sole interrupt.
> @@ -36,7 +45,8 @@ Optional properties:
> Example (Lager board):
>
> ethernet@ee700000 {
> - compatible = "renesas,ether-r8a7790";
> + compatible = "renesas,ether-r8a7790",
> + "renesas,rcar-gen2-ether";
Again, using one more tab seems possible here...
> reg = <0 0xee700000 0 0x400>;
> interrupt-parent = <&gic>;
> interrupts = <0 162 IRQ_TYPE_LEVEL_HIGH>;
>
MBR, Sergei
next prev parent reply other threads:[~2017-10-17 10:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 7:47 [PATCH net-next 0/3] net: sh_eth: add R-Car Gen[12] fallback compatibility strings Simon Horman
2017-10-17 7:47 ` [PATCH net-next 1/3] dt-bindings: " Simon Horman
2017-10-17 8:22 ` Geert Uytterhoeven
2017-10-17 10:14 ` Sergei Shtylyov [this message]
2017-10-17 10:18 ` Sergei Shtylyov
2017-10-17 7:47 ` [PATCH net-next 2/3] net: sh_eth: rename name structures as rcar_gen[12]_* Simon Horman
2017-10-17 8:20 ` Geert Uytterhoeven
2017-10-17 10:17 ` Sergei Shtylyov
2017-10-17 7:47 ` [PATCH net-next 3/3] net: sh_eth: implement R-Car Gen[12] fallback compatibility strings Simon Horman
2017-10-17 8:21 ` Geert Uytterhoeven
2017-10-17 10:20 ` Sergei Shtylyov
2017-10-18 6:49 ` [PATCH net-next 0/3] net: sh_eth: add " 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=337f227a-3019-4e82-a0cb-1328d7036df7@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=horms+renesas@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.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