netdev.vger.kernel.org archive mirror
 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 20:10:27 +0200	[thread overview]
Message-ID: <20180729181027.GA15150@lunn.ch> (raw)
In-Reply-To: <7c866f1b-70f3-8221-debd-be1bd0b6f7dd@hauke-m.de>

> The embedded PHYs are only connected to the switch in this SoC and on
> all other SoCs from this line I am aware of.

Hi Hauke

O.K, then it makes sense to have it part of the switch driver.

> The firmware is 64KBytes big and we have to load that into continuous
> memory which is then used by the PHY itself. When we are late in the
> boot process we could run into memory problems, most devices have 64MB
> or 128MB of RAM.

You might want to look at using CMA. I've never used it myself, so
cannot help much.

> How should the device tree binding should look like?
> 
> Should I create an extra sub node:
> 
> gswip: gswip@E108000 {
> 	#address-cells = <1>;
> 	#size-cells = <0>;
> 	compatible = "lantiq,xrx200-gswip";
> 	reg = <	0xE108000 0x3000 /* switch */
> 		0xE10B100 0x70 /* mdio */
> 		0xE10B1D8 0x30 /* mii */
> 		>;
> 	dsa,member = <0 0>;
> 
> 	ports {
> 		#address-cells = <1>;
> 		#size-cells = <0>;
> 
> 		port@0 {
> 			reg = <0>;
> 			label = "lan3";
> 			phy-mode = "rgmii";
> 			phy-handle = <&phy0>;
> 		};
> 		....
> 	};
> 
> 	mdio@0 {
> 		#address-cells = <1>;
> 		#size-cells = <0>;
> 		compatible = "lantiq,xrx200-mdio";
> 		reg = <0>;
> 
> 		phy0: ethernet-phy@0 {
> 			reg = <0x0>;
> 		};
> 		....
> 	};
> 
> 	# this would be the new part
> 	phys {
> 		gphy0: gphy@20 {
> 			compatible = "lantiq,xrx200a2x-gphy";

It would be good to make it clear this is for firmware download. So
scatter "firmware" or "fw" in some of these names. What we don't want
is a mix up with phy's within the mdio subtree. Otherwise this looks
good. But you should cross post the device tree binding to the device
tree mailing list.

	Andrew

  reply	other threads:[~2018-07-29 19:41 UTC|newest]

Thread overview: 28+ 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
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 [this message]
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-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=20180729181027.GA15150@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;
as well as URLs for NNTP newsgroup(s).