Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp1722735imw; Sat, 16 Jul 2022 13:19:06 -0700 (PDT) X-Google-Smtp-Source: AGRyM1uN0FAFjQLixBAr4hNNmcS5BI1w+/rVIrk7YMjOxdgOwk6OvynQuOGQb/DoxpX6wwcQUHOO X-Received: by 2002:a17:902:b116:b0:16c:dcc3:97b8 with SMTP id q22-20020a170902b11600b0016cdcc397b8mr3990928plr.64.1658002745946; Sat, 16 Jul 2022 13:19:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658002745; cv=none; d=google.com; s=arc-20160816; b=LzX6cm5z8dCl6wxW5Yi/KmZj02tKn2QESZg6EhrT02uC3az+jH9XSMMVaetvawcdQF l2hIccMQhihGEG1iWx5vjNC8RVwD0MtzTkZZXnrgtMOzErJL71bZJiuGAro5Ly2p4DvL h3esYGfgin4UNhj9cXT73GomYUZGIdywcnzopS10arQHVok9nFQq5Yp518xI07jFmDfp i7Gt4dyX9Syw2j1xP8Y/prPFxtZ4Y73z1ywti8PksUxBQxg9DaJf185rk3aSBGyt7mNF C4/THTu+ELhHsRXicueBUwf9UtxaixM8lnZsVlB7fDzblnJ4821cp9jIMEk4upMsRFLk CO4A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=3tjU9WNGMpz4TkxXbjj59cMkF1yuGZho2LASpfrLqgQ=; b=UxmEA5SEaZLYwwed+/hm0seLjoYpuUZ2HwNY7N/TEJp+eYFD7UfrBlshwdhad1VnQb uGZhDUpcdSdFPtOTi4//6OHzZOaqHHCUPjNCZV+lDv05Z46X+5+IQykrmRnQHajlwPg7 6wSkr/tr5xqY0GOIaT+2fqbfNLhG9K2en+eyOyh7XqHzmo9p/akNDshh+sfqOfJIR4/h Hw1NoRASsk/uDkX+GUf6SbAVCdczEdUh6QA0Q9E3bdfMbROdZG0Ndzcj8ZvW6AzVP0sD uzZEwp3mUAZbb6+izJppXr3MJkh7aFoNw7Z5dUvjjVWLdDQDBZKcAmZXTiDiboDErTxj 2SOw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=OiUSEr5K; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d17-20020a056a00245100b0050ad2c9d507si5823983pfj.170.2022.07.16.13.18.50; Sat, 16 Jul 2022 13:19:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=OiUSEr5K; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232576AbiGPUGR (ORCPT + 99 others); Sat, 16 Jul 2022 16:06:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36762 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229457AbiGPUGQ (ORCPT ); Sat, 16 Jul 2022 16:06:16 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [185.16.172.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4EF2D1EAE3; Sat, 16 Jul 2022 13:06:15 -0700 (PDT) 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=3tjU9WNGMpz4TkxXbjj59cMkF1yuGZho2LASpfrLqgQ=; b=OiUSEr5KOQSHXV/kQbwIZBjy5u mqz/iKuq49zwHh83IIeNWKuHJ2DmD6tasGdEn0EbCInPrD0/QCGnKlppmkJuHXJY0U7639eJrGCyZ B9PYkmxkPNJ6PJnMqWwXJcYE71tYZvyh9ZrN0xK/dsUKMpM2yjN6+4aybih9VQtyZ7Tc=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1oCo37-00AZSi-7B; Sat, 16 Jul 2022 22:06:01 +0200 Date: Sat, 16 Jul 2022 22:06:01 +0200 From: Andrew Lunn To: Sean Anderson Cc: "David S . Miller" , Jakub Kicinski , Madalin Bucur , netdev@vger.kernel.org, Paolo Abeni , Eric Dumazet , linux-arm-kernel@lists.infradead.org, Russell King , linux-kernel@vger.kernel.org, Alexandru Marginean , Heiner Kallweit , Vladimir Oltean Subject: Re: [PATCH net-next v3 08/47] net: phylink: Support differing link speeds and interface speeds Message-ID: References: <20220715215954.1449214-1-sean.anderson@seco.com> <20220715215954.1449214-9-sean.anderson@seco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220715215954.1449214-9-sean.anderson@seco.com> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > +/** > + * phy_interface_speed() - get the speed of a phy interface > + * @interface: phy interface mode defined by &typedef phy_interface_t > + * @link_speed: the speed of the link > + * > + * Some phy interfaces modes adapt to the speed of the underlying link (such as > + * by duplicating data or changing the clock rate). Others, however, are fixed > + * at a particular rate. Determine the speed of a phy interface mode for a > + * particular link speed. > + * > + * Return: The speed of @interface > + */ > +static int phy_interface_speed(phy_interface_t interface, int link_speed) > +{ > + switch (interface) { > + case PHY_INTERFACE_MODE_100BASEX: > + return SPEED_100; > + > + case PHY_INTERFACE_MODE_TBI: > + case PHY_INTERFACE_MODE_MOCA: > + case PHY_INTERFACE_MODE_RTBI: > + case PHY_INTERFACE_MODE_1000BASEX: > + case PHY_INTERFACE_MODE_1000BASEKX: > + case PHY_INTERFACE_MODE_TRGMII: > + return SPEED_1000; > + > + case PHY_INTERFACE_MODE_2500BASEX: > + return SPEED_2500; > + > + case PHY_INTERFACE_MODE_5GBASER: > + return SPEED_5000; > + > + case PHY_INTERFACE_MODE_XGMII: > + case PHY_INTERFACE_MODE_RXAUI: > + case PHY_INTERFACE_MODE_XAUI: > + case PHY_INTERFACE_MODE_10GBASER: > + case PHY_INTERFACE_MODE_10GKR: > + return SPEED_10000; > + > + case PHY_INTERFACE_MODE_25GBASER: > + return SPEED_25000; > + > + case PHY_INTERFACE_MODE_XLGMII: > + return SPEED_40000; > + > + case PHY_INTERFACE_MODE_USXGMII: > + case PHY_INTERFACE_MODE_RGMII_TXID: > + case PHY_INTERFACE_MODE_RGMII_RXID: > + case PHY_INTERFACE_MODE_RGMII_ID: > + case PHY_INTERFACE_MODE_RGMII: > + case PHY_INTERFACE_MODE_QSGMII: > + case PHY_INTERFACE_MODE_SGMII: > + case PHY_INTERFACE_MODE_GMII: > + case PHY_INTERFACE_MODE_REVRMII: > + case PHY_INTERFACE_MODE_RMII: > + case PHY_INTERFACE_MODE_SMII: > + case PHY_INTERFACE_MODE_REVMII: > + case PHY_INTERFACE_MODE_MII: > + case PHY_INTERFACE_MODE_INTERNAL: > + return link_speed; > + > + case PHY_INTERFACE_MODE_NA: > + case PHY_INTERFACE_MODE_MAX: > + break; > + } > + > + return SPEED_UNKNOWN; This seem error prone when new PHY_INTERFACE_MODES are added. I would prefer a WARN_ON_ONCE() in the default: so we get to know about such problems. I'm also wondering if we need a sanity check here. I've seen quite a few boards a Fast Ethernet MAC, but a 1G PHY because they are cheap. In such cases, the MAC is supposed to call phy_set_max_speed() to indicate it can only do 100Mbs. PHY_INTERFACE_MODE_MII but a link_speed of 1G is clearly wrong. Are there other cases where we could have a link speed faster than what the interface mode allows? Bike shedding a bit, but would it be better to use host_side_speed and line_side_speed? When you say link_speed, which link are your referring to? Since we are talking about the different sides of the PHY doing different speeds, the naming does need to be clear. Andrew