From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> To: Arnd Bergmann <arnd@arndb.de> Cc: Lior Amsalem <alior@marvell.com>, Andrew Lunn <andrew@lunn.ch>, Ike Pan <ike.pan@canonical.com>, Nadav Haklai <nadavh@marvell.com>, Ian Molton <ian.molton@codethink.co.uk>, Lennert Buytenhek <kernel@wantstofly.org>, David Marlin <dmarlin@redhat.com>, Rami Rosen <rosenr@marvell.com>, Yehuda Yitschak <yehuday@marvell.com>, Jani Monoses <jani.monoses@canonical.com>, Tawfik Bayouk <tawfik@marvell.com>, Dan Frazier <dann.frazier@canonical.com>, Eran Ben-Avi <benavi@marvell.com>, Li Li <li.li@canonical.com>, Leif Lindholm <leif.lindholm@arm.com>, Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>, Jason Cooper <jason@lakedaemon.net>, Jon Masters <jcm@redhat.com>, Ben Dooks <ben-linux@fluff.org>, Gregory Clement <gregory.clement@free-electrons.com>, linux-arm-kernel@lists.infradead.org, Chris Van Hoof <vanhoof@canonical.com>, Nicolas Pitre <nico@fluxnic.net>, netdev@vger.k Subject: Re: [PATCH 1/4] net: mvneta: driver for Marvell Armada 370/XP network unit Date: Tue, 4 Sep 2012 17:56:10 +0200 [thread overview] Message-ID: <20120904175610.2c2934f1@skate> (raw) In-Reply-To: <201209041436.36430.arnd@arndb.de> Arnd, Thanks for looking so quickly into this driver! Le Tue, 4 Sep 2012 14:36:36 +0000, Arnd Bergmann <arnd@arndb.de> a écrit : > On Tuesday 04 September 2012, Thomas Petazzoni wrote: > > .../devicetree/bindings/net/marvell-neta.txt | 24 + > > drivers/net/ethernet/marvell/Kconfig | 11 + > > drivers/net/ethernet/marvell/Makefile | 1 + > > drivers/net/ethernet/marvell/mvneta.c | 2732 ++++++++++++++++++++ > > drivers/net/ethernet/marvell/mvneta.h | 496 ++++ > > 5 files changed, 3264 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/net/marvell-neta.txt > > create mode 100644 drivers/net/ethernet/marvell/mvneta.c > > create mode 100644 drivers/net/ethernet/marvell/mvneta.h > > I usually prefer putting the definitions into the .c file rather > than a separate header if there is only only file including it > anyway. Fine. I hesitated on this one, but since the driver was already quite long, I thought a separate header would be nicer, but I don't have a strong opinion, so I'll resubmit with this change. > > +eth@d0070000 { > > + compatible = "marvell,neta"; > > + reg = <0xd0070000 0x2500>; > > + interrupts = <8>; > > + device_type = "network"; > > + clock-frequency = <250000000>; > > + status = "okay"; > > + phy-mode = "sgmii"; > > + phy-addr = <25>; > > I think we normally put the phy into a separate device node on an > mdio bus and then use the of_phy_* functions to connect it to > the ethernet device. Even though it may not be a convincing argument, none of the existing DT files in arch/arm/boot/dts seem to instantiate a separate PHY device and a proper MDIO bus. However, the PowerPC platforms indeed make this distinction a lot clearer. However, this network unit has a clever MAC that autonomously queries the PHY for the link status, and reports changes (link, duplex, speed) in the form of MAC interrupts and MAC registers. Therefore, for basic operation, there is no need for a separate PHY driver nor to expose the MDIO bus in any way. The only thing needed is the PHY address, which is filled into a register of the MAC so that it can start its automatic query of the PHY. Knowing this, would it be acceptable to have this driver without an explicit MDIO bus in the DT? Thanks, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/4] net: mvneta: driver for Marvell Armada 370/XP network unit Date: Tue, 4 Sep 2012 17:56:10 +0200 [thread overview] Message-ID: <20120904175610.2c2934f1@skate> (raw) In-Reply-To: <201209041436.36430.arnd@arndb.de> Arnd, Thanks for looking so quickly into this driver! Le Tue, 4 Sep 2012 14:36:36 +0000, Arnd Bergmann <arnd@arndb.de> a ?crit : > On Tuesday 04 September 2012, Thomas Petazzoni wrote: > > .../devicetree/bindings/net/marvell-neta.txt | 24 + > > drivers/net/ethernet/marvell/Kconfig | 11 + > > drivers/net/ethernet/marvell/Makefile | 1 + > > drivers/net/ethernet/marvell/mvneta.c | 2732 ++++++++++++++++++++ > > drivers/net/ethernet/marvell/mvneta.h | 496 ++++ > > 5 files changed, 3264 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/net/marvell-neta.txt > > create mode 100644 drivers/net/ethernet/marvell/mvneta.c > > create mode 100644 drivers/net/ethernet/marvell/mvneta.h > > I usually prefer putting the definitions into the .c file rather > than a separate header if there is only only file including it > anyway. Fine. I hesitated on this one, but since the driver was already quite long, I thought a separate header would be nicer, but I don't have a strong opinion, so I'll resubmit with this change. > > +eth at d0070000 { > > + compatible = "marvell,neta"; > > + reg = <0xd0070000 0x2500>; > > + interrupts = <8>; > > + device_type = "network"; > > + clock-frequency = <250000000>; > > + status = "okay"; > > + phy-mode = "sgmii"; > > + phy-addr = <25>; > > I think we normally put the phy into a separate device node on an > mdio bus and then use the of_phy_* functions to connect it to > the ethernet device. Even though it may not be a convincing argument, none of the existing DT files in arch/arm/boot/dts seem to instantiate a separate PHY device and a proper MDIO bus. However, the PowerPC platforms indeed make this distinction a lot clearer. However, this network unit has a clever MAC that autonomously queries the PHY for the link status, and reports changes (link, duplex, speed) in the form of MAC interrupts and MAC registers. Therefore, for basic operation, there is no need for a separate PHY driver nor to expose the MDIO bus in any way. The only thing needed is the PHY address, which is filled into a register of the MAC so that it can start its automatic query of the PHY. Knowing this, would it be acceptable to have this driver without an explicit MDIO bus in the DT? Thanks, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
next prev parent reply other threads:[~2012-09-04 15:56 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-04 13:06 net: Network driver for the Armada 370 and Armada XP ARM Marvell SoCs Thomas Petazzoni 2012-09-04 13:06 ` Thomas Petazzoni 2012-09-04 13:06 ` [PATCH 1/4] net: mvneta: driver for Marvell Armada 370/XP network unit Thomas Petazzoni 2012-09-04 13:06 ` Thomas Petazzoni 2012-09-04 14:36 ` Arnd Bergmann 2012-09-04 14:36 ` Arnd Bergmann 2012-09-04 15:56 ` Thomas Petazzoni [this message] 2012-09-04 15:56 ` Thomas Petazzoni 2012-09-04 18:31 ` Andrew Lunn 2012-09-04 18:31 ` Andrew Lunn 2012-09-05 7:32 ` Thomas Petazzoni 2012-09-05 7:32 ` Thomas Petazzoni 2012-09-05 15:25 ` Florian Fainelli 2012-09-05 15:25 ` Florian Fainelli 2012-09-04 13:06 ` [PATCH 2/4] net: mvneta: update MAINTAINERS file for the mvneta maintainers Thomas Petazzoni 2012-09-04 13:06 ` Thomas Petazzoni 2012-09-04 13:06 ` [PATCH 3/4] arm: mvebu: add Ethernet controllers using mvneta driver for Armada 370/XP Thomas Petazzoni 2012-09-04 13:06 ` Thomas Petazzoni 2012-09-04 13:06 ` [PATCH 4/4] arm: mvebu: enable Ethernet controllers on Armada 370/XP eval boards Thomas Petazzoni 2012-09-04 13:06 ` Thomas Petazzoni 2012-10-23 16:54 [PATCH v3] Network driver for the Armada 370 and Armada XP ARM Marvell SoCs Thomas Petazzoni 2012-10-23 16:54 ` [PATCH 1/4] net: mvneta: driver for Marvell Armada 370/XP network unit Thomas Petazzoni 2012-10-23 16:54 ` Thomas Petazzoni 2012-10-25 3:06 ` David Miller 2012-10-25 3:06 ` David Miller 2012-10-25 6:21 ` Thomas Petazzoni 2012-10-25 6:21 ` Thomas Petazzoni 2012-10-26 10:03 [PATCH v4] Network driver for the Armada 370 and Armada XP ARM Marvell SoCs Thomas Petazzoni 2012-10-26 10:03 ` [PATCH 1/4] net: mvneta: driver for Marvell Armada 370/XP network unit Thomas Petazzoni 2012-10-26 10:03 ` Thomas Petazzoni 2012-10-30 12:07 ` Nobuhiro Iwamatsu 2012-10-30 12:07 ` Nobuhiro Iwamatsu 2012-10-30 12:28 ` Thomas Petazzoni 2012-10-30 12:28 ` Thomas Petazzoni 2012-10-31 11:12 ` Florian Fainelli 2012-10-31 11:12 ` Florian Fainelli
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=20120904175610.2c2934f1@skate \ --to=thomas.petazzoni@free-electrons.com \ --cc=alior@marvell.com \ --cc=andrew@lunn.ch \ --cc=arnd@arndb.de \ --cc=ben-linux@fluff.org \ --cc=benavi@marvell.com \ --cc=dann.frazier@canonical.com \ --cc=dmarlin@redhat.com \ --cc=gregory.clement@free-electrons.com \ --cc=ian.molton@codethink.co.uk \ --cc=ike.pan@canonical.com \ --cc=jani.monoses@canonical.com \ --cc=jason@lakedaemon.net \ --cc=jcm@redhat.com \ --cc=kernel@wantstofly.org \ --cc=leif.lindholm@arm.com \ --cc=li.li@canonical.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=nadavh@marvell.com \ --cc=netdev@vger.k \ --cc=nico@fluxnic.net \ --cc=rosenr@marvell.com \ --cc=sebastian.hesselbarth@gmail.com \ --cc=tawfik@marvell.com \ --cc=vanhoof@canonical.com \ --cc=yehuday@marvell.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.