Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp375632pxf; Wed, 7 Apr 2021 01:28:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxqc+KUgWs8s82Hi5/Yiii8AGjl98GFlvFiLmGqoBE5UCihE2Y6FrCb5KlLfut/vdeeyWUg X-Received: by 2002:a05:6e02:18ce:: with SMTP id s14mr1931237ilu.195.1617784129532; Wed, 07 Apr 2021 01:28:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617784129; cv=none; d=google.com; s=arc-20160816; b=SRArV0suFvO8nX+UdK54DaKSsFW8B1Dm0S5ybezFqlQYzkvjEFhke25SB96K1/U59+ tRtbeabmStmA+pjvUn0pomFpw6vQ5Wzf9VdVcdskmxasqej9rCqAG4/h91WTdT0io5QT YdYHfJQor8+Pta5AfmLvmWH80FiiR+iEktAcvigqI/P4GnPpIzGK5A6Z/YkMt1m8CGhW xDSuZFC2OQxzZGTMuFC8N+of2rKWQTdcuIDccdB53lwBS2704hXVG6gzmqki+sk/f8m6 txuh2BAqcuFLm3Mu/qMyllqnx/kNEnhjpj/Xx7U+eEKnJuOEJ4/pvMnY+rQb+kNRWM6p 5Qdw== 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; bh=TVOGgd+LAiuZ7rvZWB7f1XpOcn8GwMvdiAiSNoj09Yw=; b=Xx2tdmWScTBNQsmdxITmey4rEZb3nt/qIst4cd2u9MTUphKsr3vk49BlndkJ3oAc0n tjShc7BYaZ3ezQGD6419dRuwDGQ9sRwTEyTVRXcz4AFHqR3ySl7gtMYsvoTuS5FRgQP6 wHo/5jJGtr49G0eUN8bdale1Hpk6wi3jWY8foLbfWq/nQpr8NsMRsF8EqtcWkLTCbJx0 e2UHpBbX7UCDBaBAuuHsUfwJCkX0InQ30nn902iARE2myMcQi3ftvazLjG4fb8agcK6/ yZTsBsjoPUQf0PVTIPeqOHYbSWJPpuDeJFxfM6APSJETjHHMgvMEvtbvk1fZvtEn6oRf Peuw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n6si20041414jaj.81.2021.04.07.01.28.33; Wed, 07 Apr 2021 01:28:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245175AbhDFUGu (ORCPT + 99 others); Tue, 6 Apr 2021 16:06:50 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:36450 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234411AbhDFUGt (ORCPT ); Tue, 6 Apr 2021 16:06:49 -0400 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1lTrxn-00FB5Q-Mq; Tue, 06 Apr 2021 22:06:15 +0200 Date: Tue, 6 Apr 2021 22:06:15 +0200 From: Andrew Lunn To: "Voon, Weifeng" Cc: "Sit, Michael Wei Hong" , "peppe.cavallaro@st.com" , "alexandre.torgue@st.com" , "joabreu@synopsys.com" , "davem@davemloft.net" , "kuba@kernel.org" , "mcoquelin.stm32@gmail.com" , "linux@armlinux.org.uk" , "Ong, Boon Leong" , "qiangqing.zhang@nxp.com" , "Wong, Vee Khee" , "fugang.duan@nxp.com" , "Chuah, Kim Tatt" , "netdev@vger.kernel.org" , "linux-stm32@st-md-mailman.stormreply.com" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "hkallweit1@gmail.com" Subject: Re: [PATCH net-next v2 0/2] Enable 2.5Gbps speed for stmmac Message-ID: References: <20210405112953.26008-1-michael.wei.hong.sit@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > The limitation is not on the MAC, PCS or the PHY. For Intel mgbe, the > overclocking of 2.5 times clock rate to support 2.5G is only able to be > configured in the BIOS during boot time. Kernel driver has no access to > modify the clock rate for 1Gbps/2.5G mode. The way to determined the > current 1G/2.5G mode is by reading a dedicated adhoc register through mdio bus. > In short, after the system boot up, it is either in 1G mode or 2.5G mode > which not able to be changed on the fly. Right. It would of been a lot easier if this was in the commit message from the beginning. Please ensure the next version does say this. > Since the stmmac MAC can pair with any PCS and PHY, I still prefer that we tie > this platform specific limitation with the of MAC. As stmmac does handle platform > specific config/limitation. So yes, this needs to be somewhere in the intel specific stmmac code, with a nice comment explaining what is going on. What PHY are you using? The Aquantia/Marvell multi-gige phy can do rate adaptation. So you could fix the MAC-PHY link to 2500BaseX, and let the PHY internally handle the different line speeds. Andrew