linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 8/8] arm64: dts: renesas: eagle: add EtherAVB support
Date: Tue, 10 Oct 2017 09:33:46 +0200	[thread overview]
Message-ID: <20171010073346.GL2518@verge.net.au> (raw)
In-Reply-To: <d5940a12-3823-eebb-50d9-c0fd0fcf0fd1@cogentembedded.com>

On Mon, Oct 09, 2017 at 08:57:42PM +0300, Sergei Shtylyov wrote:
> On 10/05/2017 12:05 PM, Simon Horman wrote:
> 
> >>>On 9/21/2017 4:08 PM, Geert Uytterhoeven wrote:
> >>>>>Define the Eagle board  dependent part of the EtherAVB device node.
> >>>>>Enable DHCP  and NFS root for the kernel booting.
> >>>>>
> >>>>>Based  on the original (and large) patch by Vladimir Barinov.
> >>>>>
> >>>>>Signed-off-by: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
> >>>>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> >>>>
> >>>>
> >>>>>--- renesas.orig/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
> >>>>>+++ renesas/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
> >>>
> >>>[...]
> >>>>>
> >>>>>@@ -43,3 +44,14 @@
> >>>>>   &scif0 {
> >>>>>          status = "okay";
> >>>>>   };
> >>>>>+
> >>>>>+&avb {
> >>>>>+       renesas,no-ether-link;
> >>>>>+       phy-handle = <&phy0>;
> >>>>>+       status = "okay";
> >>>>>+
> >>>>>+       phy0: ethernet-phy at 0 {
> >>>>>+               rxc-skew-ps = <1500>;
> >>>>>+               reg = <0>;
> >>>>
> >>>>
> >>>>Any specific reason why you don't want to wire up the interrupt?
> >>>>
> >>>>                  interrupt-parent = <&gpio2>;
> >>>
> >>>
> >>>    I thought it's quite obvious -- we don't have GPIOs yet, and GPIOs seem
> >>>to require PFC.
> >>
> >>Of course. And these can be added later.
> >>
> >>Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> >Thanks, applied.
> 
>    Unfortunately, you applied an outdated version of this patch. :-(

Sorry, I think patchwork has been playing up of late - or my use of it!

Could you repost the correct patch so I am sure to get the right one
the second time around?

  reply	other threads:[~2017-10-10  7:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15 19:43 [PATCH v2 8/8] arm64: dts: renesas: eagle: add EtherAVB support Sergei Shtylyov
2017-09-21 13:08 ` Geert Uytterhoeven
2017-09-21 16:03   ` Sergei Shtylyov
2017-09-21 16:09     ` Geert Uytterhoeven
2017-10-05  9:05       ` Simon Horman
2017-10-05 17:18         ` Sergei Shtylyov
2017-10-06  9:31           ` Simon Horman
2017-10-06  9:34             ` Sergei Shtylyov
2017-10-09 17:57         ` Sergei Shtylyov
2017-10-10  7:33           ` Simon Horman [this message]
2017-10-10  7:48             ` Simon Horman
2017-10-10  8:03               ` 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=20171010073346.GL2518@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).