From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1E47BC04E53 for ; Wed, 15 May 2019 12:39:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E12C920862 for ; Wed, 15 May 2019 12:39:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726663AbfEOMjk (ORCPT ); Wed, 15 May 2019 08:39:40 -0400 Received: from relay10.mail.gandi.net ([217.70.178.230]:49933 "EHLO relay10.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726392AbfEOMjj (ORCPT ); Wed, 15 May 2019 08:39:39 -0400 Received: from bootlin.com (aaubervilliers-681-1-43-46.w90-88.abo.wanadoo.fr [90.88.161.46]) (Authenticated sender: maxime.chevallier@bootlin.com) by relay10.mail.gandi.net (Postfix) with ESMTPSA id 8EA3C24000E; Wed, 15 May 2019 12:39:36 +0000 (UTC) Date: Wed, 15 May 2019 14:39:36 +0200 From: Maxime Chevallier To: Florian Fainelli , Andrew Lunn , Vivien Didelot , Russell King , netdev@vger.kernel.org, "thomas.petazzoni@bootlin.com" , Antoine Tenart , Heiner Kallweit Subject: dsa: using multi-gbps speeds on CPU port Message-ID: <20190515143936.524acd4e@bootlin.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hello everyone, I'm working on a setup where I have a 88e6390X DSA switch connected to a CPU (an armada 8040) with 2500BaseX and RXAUI interfaces (we only use one at a time). I'm facing a limitation with the current way to represent that link, where we use a fixed-link description in the CPU port, like this : ... switch0: switch0@1 { ... port@0 { reg = <0>; label = "cpu"; ethernet = <ð0>; phy-mode = "2500base-x"; fixed-link { speed = <2500>; full-duplex; }; }; }; ... In this scenario, the dsa core will try to create a PHY emulating the fixed-link on the DSA port side. This can't work with link speeds above 1Gbps, since we don't have any emulation for these PHYs, which would be using C45 MMDs. We could add support to emulate these modes, but I think there were some discussions about using phylink to support these higher speed fixed-link modes, instead of using PHY emulation. However using phylink in master DSA ports seems to be a bit tricky, since master ports don't have a dedicated net_device, and instead reference the CPU-side netdevice (if I understood correctly). I'll be happy to help on that, but before prototyping anything, I wanted to have your thougts on this, and see if you had any plans. Thanks, Maxime