From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] arm: dts: gr-peach: Add ETHER pin group
Date: Wed, 30 Aug 2017 09:25:42 +0200 [thread overview]
Message-ID: <20170830072542.GH10398@verge.net.au> (raw)
In-Reply-To: <20170824125359.GB3905@w540>
On Thu, Aug 24, 2017 at 02:53:59PM +0200, jmondi wrote:
> Thanks Geert,
>
> On Thu, Aug 24, 2017 at 01:56:16PM +0200, Geert Uytterhoeven wrote:
> > Hi Jacopo,
> >
>
> [snip]
>
> > > I haven't find any mention in device tree bindings documentation of a
> > > "reset-gpio" property for sh_eth, in the code examples I've seen in
> > > u-boot and mbed, the interface is reset before any actual
> > > configuration is performed. I feel like that should be the place where
> > > that gpio is requested and cycled...
> >
> > Documentation/devicetree/bindings/net/mdio.txt says
> >
> > These are generic properties that can apply to any MDIO bus.
> >
>
> I have now used mdio defined generic properties
>
> ðer {
> pinctrl-names = "default";
> pinctrl-0 = <ðer_pins>;
>
> status = "okay";
>
> reset-gpios = <&port4 2 GPIO_ACTIVE_LOW>;
> reset-delay-us = <5>;
>
> renesas,no-ether-link;
> phy-handle = <&phy0>;
> phy0: ethernet-phy at 0 {
> reg = <0>;
> };
> };
>
> I see the gpio being cycled, but same results as before: device gets
> probed, address set, but I cannot ping, device gets probed, address
> gets set, but I cannot ping
>
> --- target ---
> [ 0.000000] libphy: sh_mii: probed
> [ 0.000000] sh-eth e8203000.ethernet eth0: Base address at 0xe8203000, 68:14:97:20:97:00, IRQ 22.
>
> # ifconfig eth0 192.168.100.50
> [ 0.000000] Generic PHY e8203000.ethernet-ffffffff:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e8203000.ethernet-f)
>
> --- host ---
> $ping 192.168.100.50
> PING 192.168.100.50 (192.168.100.50) 56(84) bytes of data.
> >From 192.168.100.18 icmp_seq=1 Destination Host Unreachable
> >From 192.168.100.18 icmp_seq=1 Destination Host Unreachable
> >From 192.168.100.18 icmp_seq=1 Destination Host Unreachable
>
>
> Let's leave this out of the DTS series I've just sent for now, ok?
I'm a little confused by this. Am I right in thinking that you don't want
this patch applied at this time and may resubmit it or an updated version
later? With that understanding I have marked it as "Rejected" for now. Feel
free to resubmit when you are ready.
next prev parent reply other threads:[~2017-08-30 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1503564523-31899-1-git-send-email-jacopo+renesas@jmondi.org>
[not found] ` <1503564523-31899-2-git-send-email-jacopo+renesas@jmondi.org>
2017-08-24 9:22 ` [PATCH 1/4] arm: dts: gr-peach: Remove empty line Geert Uytterhoeven
[not found] ` <1503564523-31899-3-git-send-email-jacopo+renesas@jmondi.org>
2017-08-24 9:27 ` [PATCH 2/4] arm: dts: gr-peach: Add SCIF2 pin group Geert Uytterhoeven
[not found] ` <1503564523-31899-5-git-send-email-jacopo+renesas@jmondi.org>
2017-08-24 9:31 ` [PATCH 4/4] arm: dts: gr-peach: Add user led device nodes Geert Uytterhoeven
[not found] ` <1503564523-31899-4-git-send-email-jacopo+renesas@jmondi.org>
2017-08-24 9:48 ` [PATCH 3/4] arm: dts: gr-peach: Add ETHER pin group Geert Uytterhoeven
2017-08-24 11:46 ` jmondi
2017-08-24 11:56 ` Geert Uytterhoeven
2017-08-24 12:53 ` jmondi
2017-08-30 7:25 ` Simon Horman [this message]
2017-08-30 7:35 ` jmondi
2017-08-30 9:28 ` Simon Horman
2017-08-24 10:53 ` [PATCH 0/4] GR-Peach DTS update Simon Horman
2017-08-24 10:57 ` 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=20170830072542.GH10398@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).