From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B536214F78; Mon, 18 Dec 2023 10:10:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="LUinvacZ" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=+atTE69qUF4qmAtBOv2QlTxSSQnSgQ2ejCWr//9J2gU=; b=LUinvacZ+I/oBS1JF9SJ3GoiJu 3DlMzLFt3ljsLnEz3JgreIvMNv7MXaVYMG+3cy0ZcFOthBu4lx56aFOI+VCqvQlyQAJNiSi39f9Ty LIBpHbnLiRjBHnrPFLvQ7OHJb/jGVonHP7rvUbyB/17qEzcX4v+YdLI6RJiJS4f++52k=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1rFAZx-003ESu-IU; Mon, 18 Dec 2023 11:10:29 +0100 Date: Mon, 18 Dec 2023 11:10:29 +0100 From: Andrew Lunn To: Maxime Chevallier Cc: davem@davemloft.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com, Jakub Kicinski , Eric Dumazet , Paolo Abeni , Russell King , linux-arm-kernel@lists.infradead.org, Christophe Leroy , Herve Codina , Florian Fainelli , Heiner Kallweit , Vladimir Oltean , =?iso-8859-1?Q?K=F6ry?= Maincent , Jesse Brandeburg , Jonathan Corbet , Marek =?iso-8859-1?Q?Beh=FAn?= , Piergiorgio Beruto , Oleksij Rempel , =?iso-8859-1?Q?Nicol=F2?= Veronese Subject: Re: [PATCH net-next v4 13/13] Documentation: networking: document phy_link_topology Message-ID: <32461e61-b518-4ecc-bf51-7d22f8580212@lunn.ch> References: <20231215171237.1152563-1-maxime.chevallier@bootlin.com> <20231215171237.1152563-14-maxime.chevallier@bootlin.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231215171237.1152563-14-maxime.chevallier@bootlin.com> > +An Ethernet Interface from userspace's poing of view is nothing but a point > +:c:type:`struct net_device `, which exposes configuration options > +trough the legacy ioctls and the ethool netlink commands. The base assumption through > +when designing these configuration channels were that the link looked > +something like this :: > + > + +-----------------------+ +----------+ +--------------+ > + | Ethernet Controller / | | Ethernet | | Connector / | > + | MAC | ------ | PHY | ---- | Port | ---... to LP > + +-----------------------+ +----------+ +--------------+ > + struct net_device struct phy_device > + > +Commands that needs to configure the PHY will go through the net_device.phydev > +field to reach the PHY and perform the relevant configuration. > + > +This assumption falls appart in more complex topologies that can arise when, apart. Andrew