[PATCH] DT: net: renesas,ravb: document R8A77980 bindings

Renesas R-Car V3H (R8A77980) SoC has the R-Car gen3 compatible EtherAVB
device, so document the SoC specific bindings.

Signed-off-by: Sergei Shtylyov <sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>

---
The patch is against DaveM's 'net-next.git' repo but I wouldn't mind if it's
applied to 'net.git' instead. :-)

 Documentation/devicetree/bindings/net/renesas,ravb.txt |    1 +
 1 file changed, 1 insertion(+)

Index: net-next/Documentation/devicetree/bindings/net/renesas,ravb.txt
===================================================================

--- net-next.orig/Documentation/devicetree/bindings/net/renesas,ravb.txt
+++ net-next/Documentation/devicetree/bindings/net/renesas,ravb.txt

@@ -18,6 +18,7 @@ Required properties:
       - "renesas,etheravb-r8a7795" for the R8A7795 SoC.
       - "renesas,etheravb-r8a7796" for the R8A7796 SoC.
       - "renesas,etheravb-r8a77970" for the R8A77970 SoC.
+      - "renesas,etheravb-r8a77980" for the R8A77980 SoC.
       - "renesas,etheravb-r8a77995" for the R8A77995 SoC.
       - "renesas,etheravb-rcar-gen3" as a fallback for the above
 		R-Car Gen3 devices.
--

To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

On Thu, Feb 1, 2018 at 9:13 PM, Sergei Shtylyov
[off-list ref] wrote:

Renesas R-Car V3H (R8A77980) SoC has the R-Car gen3 compatible EtherAVB
device, so document the SoC specific bindings.

Signed-off-by: Sergei Shtylyov <redacted>

Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Gr{oetje,eeting}s,

                        Geert

On Thu, Feb 01, 2018 at 11:13:45PM +0300, Sergei Shtylyov wrote:

Renesas R-Car V3H (R8A77980) SoC has the R-Car gen3 compatible EtherAVB
device, so document the SoC specific bindings.

Signed-off-by: Sergei Shtylyov <redacted>

---
The patch is against DaveM's 'net-next.git' repo but I wouldn't mind if it's
applied to 'net.git' instead. :-)

 Documentation/devicetree/bindings/net/renesas,ravb.txt |    1 +
 1 file changed, 1 insertion(+)

Reviewed-by: Rob Herring <robh@kernel.org>

On 02/01/2018 11:13 PM, Sergei Shtylyov wrote:

Renesas R-Car V3H (R8A77980) SoC has the R-Car gen3 compatible EtherAVB
device, so document the SoC specific bindings.

Signed-off-by: Sergei Shtylyov <redacted>

---
The patch is against DaveM's 'net-next.git' repo but I wouldn't mind if it's
applied to 'net.git' instead. :-)

   David, I see this patch was marked as "not applicable" in patchwork. Why, because
it was posted during the merge window?

MNBR, Sergei

From: Sergei Shtylyov <redacted>
Date: Sat, 24 Feb 2018 21:01:15 +0300

On 02/01/2018 11:13 PM, Sergei Shtylyov wrote:

quoted

Renesas R-Car V3H (R8A77980) SoC has the R-Car gen3 compatible EtherAVB
device, so document the SoC specific bindings.

Signed-off-by: Sergei Shtylyov <redacted>

---
The patch is against DaveM's 'net-next.git' repo but I wouldn't mind if it's
applied to 'net.git' instead. :-)

   David, I see this patch was marked as "not applicable" in patchwork. Why, because
it was posted during the merge window?

No because I thought the relevant architecture tree would take a mere
DT update.

Hello!

On 2/25/2018 5:53 AM, David Miller wrote:

quoted

quoted

Renesas R-Car V3H (R8A77980) SoC has the R-Car gen3 compatible EtherAVB >>> device, so document the SoC specific bindings.>>>>>> Signed-off-by: 

Sergei Shtylyov [off-list ref]>>>>>> --->>> The patch is 
against DaveM's 'net-next.git' repo but I wouldn't mind if it's>>> applied to 
'net.git' instead. :-)>>>>     David, I see this patch was marked as "not 
applicable" in patchwork. Why, because>> it was posted during the merge 
window?> > No because I thought the relevant architecture tree would take a 
mere> DT update.
    Well, so far the binding updates have been merged via the appropriate 
driver subsystem trees, look at e.g. this patch:

https://patchwork.ozlabs.org/patch/813037/

MBR, Sergei

On 02/25/2018 11:48 AM, Sergei Shtylyov wrote:

quoted

quoted

quoted

Renesas R-Car V3H (R8A77980) SoC has the R-Car gen3 compatible EtherAVB >>> device, so document the SoC specific bindings.>>>>>> Signed-off-by: 

Sergei Shtylyov [off-list ref]>>>>>> --->>> The patch is against DaveM's 'net-next.git' repo but I wouldn't mind if it's>>> applied to 'net.git' instead. :-)>>>>     David, I see this patch was marked as "not applicable" in patchwork. Why, because>> it was posted during the merge window?> > No because I thought the relevant architecture tree would take a mere> DT update.

   Sorry for this crap -- I was testing my new mini-keyboard and something went wrong...

MBR, Sergei

On Sat, Feb 24, 2018 at 09:53:17PM -0500, David Miller wrote:

From: Sergei Shtylyov <redacted>
Date: Sat, 24 Feb 2018 21:01:15 +0300

quoted

On 02/01/2018 11:13 PM, Sergei Shtylyov wrote:

quoted

Renesas R-Car V3H (R8A77980) SoC has the R-Car gen3 compatible EtherAVB
device, so document the SoC specific bindings.

Signed-off-by: Sergei Shtylyov <redacted>

---
The patch is against DaveM's 'net-next.git' repo but I wouldn't mind if it's
applied to 'net.git' instead. :-)

   David, I see this patch was marked as "not applicable" in patchwork. Why, because
it was posted during the merge window?

No because I thought the relevant architecture tree would take a mere
DT update.

Hi Dave,

I am happy to take these kinds of changes for the ravb and sh_eth drivers
if that is your preference. I am also just as happy for you to take them,
which I think has been the case for similar changes in the past.

From: Simon Horman <horms@verge.net.au>
Date: Mon, 26 Feb 2018 11:58:24 +0100

On Sat, Feb 24, 2018 at 09:53:17PM -0500, David Miller wrote:

quoted

From: Sergei Shtylyov <redacted>
Date: Sat, 24 Feb 2018 21:01:15 +0300

quoted

On 02/01/2018 11:13 PM, Sergei Shtylyov wrote:

quoted

Renesas R-Car V3H (R8A77980) SoC has the R-Car gen3 compatible EtherAVB
device, so document the SoC specific bindings.

Signed-off-by: Sergei Shtylyov <redacted>

---
The patch is against DaveM's 'net-next.git' repo but I wouldn't mind if it's
applied to 'net.git' instead. :-)

   David, I see this patch was marked as "not applicable" in patchwork. Why, because
it was posted during the merge window?

No because I thought the relevant architecture tree would take a mere
DT update.

Hi Dave,

I am happy to take these kinds of changes for the ravb and sh_eth drivers
if that is your preference. I am also just as happy for you to take them,
which I think has been the case for similar changes in the past.

No, it's not a problem.  Applied to 'net', thanks.

On Mon, Feb 26, 2018 at 03:10:51PM -0500, David Miller wrote:

From: Simon Horman <horms@verge.net.au>
Date: Mon, 26 Feb 2018 11:58:24 +0100

quoted

On Sat, Feb 24, 2018 at 09:53:17PM -0500, David Miller wrote:

quoted

From: Sergei Shtylyov <redacted>
Date: Sat, 24 Feb 2018 21:01:15 +0300

quoted

On 02/01/2018 11:13 PM, Sergei Shtylyov wrote:

quoted

Renesas R-Car V3H (R8A77980) SoC has the R-Car gen3 compatible EtherAVB
device, so document the SoC specific bindings.

Signed-off-by: Sergei Shtylyov <redacted>

---
The patch is against DaveM's 'net-next.git' repo but I wouldn't mind if it's
applied to 'net.git' instead. :-)

   David, I see this patch was marked as "not applicable" in patchwork. Why, because
it was posted during the merge window?

No because I thought the relevant architecture tree would take a mere
DT update.

Hi Dave,

I am happy to take these kinds of changes for the ravb and sh_eth drivers
if that is your preference. I am also just as happy for you to take them,
which I think has been the case for similar changes in the past.

No, it's not a problem.  Applied to 'net', thanks.

Great, thanks.