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 22233351C20; Fri, 8 May 2026 13:35:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=156.67.10.101 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778247340; cv=none; b=iF73xTxMiSDHX8AtB3J8BLkocA4Yy0XI1QjN62dhZzdXH1NYMar1z5mag0mDW/otTtNSD8Fl4cEBlb2SFUcE0FWLxj6iUTzZsjymI59EQY8SNHbRj16T4C/bjoDSf/ewDY6shUOGTcK8nXfmuX1aQOepsSeWlQy9CeR/tff335Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778247340; c=relaxed/simple; bh=W5z+ZvjeraSq0lSpTjZEb81FwbkIx92nnUKXxoZ2Y9E=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=odcV2bX9+06ON+qPVdFnCN7oadKgVTZ2tUSYVejHrM2TjcN6vnR0gWMp+aFBCbQ0WEw1VnJDjgdLOkCl4FegI3h32jJsXG9FdMmyxf4zZdbr5AzkNsuc2Ks37zABswqbCrKnoZ9iWc+imuwtFrhkDa8vWoSdFfvDchmiFHk0HQA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch; spf=pass smtp.mailfrom=lunn.ch; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b=dEsn2jJk; arc=none smtp.client-ip=156.67.10.101 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="dEsn2jJk" 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=uRlWfI16RymHotfKoKopTsF4SVqazk8teSam4cHD0H0=; b=dEsn2jJkfn0vWzDqmxpz/dpbvV 9/vq5HjVqavwgrmrWiobypSOnn3E2jm6DDa+Bi4CXBt5amdylGIbVxVkQACH2LcKGMBM+VrFtnd5O DYHzi0irzD7tE0L8DU/LxjfhmbgByTU0+VR5bhkzErWpUKXV/KmeOrnFv5Kub5qE4Jp4=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1wLLLm-001yZO-4f; Fri, 08 May 2026 15:34:42 +0200 Date: Fri, 8 May 2026 15:34:42 +0200 From: Andrew Lunn To: Daniel Thompson Cc: Alex Elder , andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, maxime.chevallier@bootlin.com, rmk+kernel@armlinux.org.uk, andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, linusw@kernel.org, brgl@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org, mohd.anwar@oss.qualcomm.com, a0987203069@gmail.com, alexandre.torgue@foss.st.com, ast@kernel.org, boon.khai.ng@altera.com, chenchuangyu@xiaomi.com, chenhuacai@kernel.org, daniel@iogearbox.net, hawk@kernel.org, hkallweit1@gmail.com, inochiama@gmail.com, john.fastabend@gmail.com, julianbraha@gmail.com, livelycarpet87@gmail.com, matthew.gerlach@altera.com, mcoquelin.stm32@gmail.com, me@ziyao.cc, prabhakar.mahadev-lad.rj@bp.renesas.com, richardcochran@gmail.com, rohan.g.thomas@altera.com, sdf@fomichev.me, siyanteng@cqsoftware.com.cn, weishangjuan@eswincomputing.com, wens@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-gpio@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next 10/12] net: stmmac: tc956x: add TC956x/QPS615 support Message-ID: References: <20260501155421.3329862-1-elder@riscstar.com> <20260501155421.3329862-11-elder@riscstar.com> <2ce5897d-5bbb-486a-b0f0-0e30e54b451a@lunn.ch> Precedence: bulk X-Mailing-List: devicetree@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: > BTW if you are bothered by SP_SEL_SGMII_2500M, that name comes directly > from the TRM and I'd prefer to keep it if I can. The enumerated value > we have to write into the SP_SEL for 2500base-X is "SGMII 2500M". We try to avoid anything to do with SGMII and 2500 because it is technically wrong. Cisco never defined SGMII for 2500, it is something silicon vendors have made up, without any foundation in any standardisation. We much prefer to refer to it as 2500BaseX with broken signalling, which is a much more accurate description. The TRM is also not a public document. If it was, i could see some value in keeping with the naming, but since ~0 developers have the document, this is less useful. Andrew