Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	vivien.didelot@savoirfairelinux.com, f.fainelli@gmail.com,
	john@phrozen.org, linux-mips@linux-mips.org, dev@kresin.me,
	hauke.mehrtens@intel.com
Subject: Re: [PATCH 3/4] net: lantiq: Add Lantiq / Intel vrx200 Ethernet driver
Date: Sun, 29 Jul 2018 17:51:06 +0200	[thread overview]
Message-ID: <20180729155106.GB13198@lunn.ch> (raw)
In-Reply-To: <0ba31982-1657-aea8-42bc-0ea838621256@hauke-m.de>

On Sun, Jul 29, 2018 at 04:03:10PM +0200, Hauke Mehrtens wrote:
> On 07/25/2018 05:28 PM, Andrew Lunn wrote:
> >> +	/* Make sure the firmware of the embedded GPHY is loaded before,
> >> +	 * otherwise they will not be detectable on the MDIO bus.
> >> +	 */
> >> +	of_for_each_phandle(&it, err, np, "lantiq,phys", NULL, 0) {
> >> +		phy_np = it.node;
> >> +		if (phy_np) {
> >> +			struct platform_device *phy = of_find_device_by_node(phy_np);
> >> +
> >> +			of_node_put(phy_np);
> >> +			if (!platform_get_drvdata(phy))
> >> +				return -EPROBE_DEFER;
> >> +		}
> >> +	}
> > 
> > Is there a device tree binding document for this somewhere?
> > 
> >    Andrew
> > 
> 
> No, but I will create one.
> 
> I am also not sure iof this is the correct way of doing this.
> 
> We first have to load the FW into the Ethernet PHY though some generic
> SoC registers and then we can find it normally on the MDIO bus and
> interact with it like an external PHY on the MDIO bus.

Hi Hauke

It look sensible so far, but it would be good to post the PHY firmware
download code as well. Lets see the big picture, then we can decide if
there is a better way.

    Andrew

  reply	other threads:[~2018-07-29 15:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-21 19:13 [PATCH 0/4] net: Add support for Lantiq / Intel vrx200 network Hauke Mehrtens
2018-07-21 19:13 ` [PATCH 1/4] MIPS: lantiq: Do not enable IRQs in dma open Hauke Mehrtens
2018-07-24  0:19   ` Paul Burton
2018-07-24  5:32     ` Hauke Mehrtens
2018-07-24  5:39       ` David Miller
2018-07-21 19:13 ` [PATCH 2/4] net: dsa: Add Lantiq / Intel GSWIP tag support Hauke Mehrtens
2018-07-25 14:20   ` Andrew Lunn
2018-07-29 14:01     ` Hauke Mehrtens
2018-07-21 19:13 ` [PATCH 3/4] net: lantiq: Add Lantiq / Intel vrx200 Ethernet driver Hauke Mehrtens
2018-07-21 20:25   ` John Crispin
2018-07-21 23:18     ` Hauke Mehrtens
2018-07-24  0:34   ` Paul Burton
2018-07-24  5:27     ` Hauke Mehrtens
2018-07-25 15:28   ` Andrew Lunn
2018-07-29 14:03     ` Hauke Mehrtens
2018-07-29 15:51       ` Andrew Lunn [this message]
2018-07-29 15:53         ` Hauke Mehrtens
2018-07-29 16:40           ` Andrew Lunn
2018-07-29 17:44             ` Hauke Mehrtens
2018-07-29 18:10               ` Andrew Lunn
2018-07-21 19:13 ` [PATCH 4/4] net: dsa: Add Lantiq / Intel DSA driver for vrx200 Hauke Mehrtens
2018-07-22  3:17   ` David Miller
2018-07-22  9:29     ` Hauke Mehrtens
2018-07-22  9:29     ` Hauke Mehrtens
2018-07-25 16:12   ` Andrew Lunn
2018-07-29 16:25     ` Hauke Mehrtens
2018-07-29 16:49       ` Andrew Lunn
2018-07-25 16:32   ` John Crispin
2018-07-25 16:46     ` Andrew Lunn

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=20180729155106.GB13198@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dev@kresin.me \
    --cc=f.fainelli@gmail.com \
    --cc=hauke.mehrtens@intel.com \
    --cc=hauke@hauke-m.de \
    --cc=john@phrozen.org \
    --cc=linux-mips@linux-mips.org \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.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