Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp3215209rwd; Fri, 16 Jun 2023 14:06:00 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4oEXezYGTZeP/6TcTq6JwlEwsIw5JbLA3zoA66plhh7m1XnjlHeu5jTVKuPIWksF/Hh4Ob X-Received: by 2002:a05:6a20:394a:b0:116:df6e:c857 with SMTP id r10-20020a056a20394a00b00116df6ec857mr4097337pzg.16.1686949560063; Fri, 16 Jun 2023 14:06:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686949560; cv=none; d=google.com; s=arc-20160816; b=y0O00c43FOHa0MUZAtnvLk4sXLpxYwgheJIInw33R+67A9RBT3wj0mZ2ydAxAwCYp+ HZUuxLVxLjiAztCz2He/m4A+84mVKpQ78rCTeK1nr+UQKzHWyc/xHRuDXUReSEpslQEs bMYZG2oDVgmBygkb6IpITmNGj/DAVHTY8QqHe6DFdpM0H6+MvcinfCYbJbcNbx8R0hIq HT6FTc1FBy/vLmJGhziyE6YAq5W9lYygaietO3Dp3i4lJCc1InZM1/hqXSm2VvTn2Dx0 sbozutwQKHnBfveITK6tbYxmJTlhO6QMKizU3C9rax8F1o/Hb8Ji7iuxglCt5D7lMuc3 Ee5Q== 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=nf8z9XousGG+fVE7OsptakvEUAwhGZgWUXM8tGBA97M=; b=053pmlxnWbIBWm+fs71vsMGchFBxutrTPU1eN+HVyRRDZSKAZGX4SSVsbaaK6zs/ut V8OHdq70JuqEEDZBHXc4wxMlEppPAqwUzHzQlhFgYCNm+mJOwqa+fZ2Ye3ymiEWCCuag sFYNKR62i4w9gUIldWDCKXYMli6bPPqj3mHYGIja+V8TP8uJGGErGRct7g7Wgkf/Y8fo k1SJ/49FbFsYWXuEWT2z0iArslI8aklTDAHhN3Hq+/BUB7YRqTbrdDDqkrC58YdpOdn3 e8g5cM/oSvUuKwx6FCpRB0fW2sQ2xW2ixRjE+oQMnIuGz6BPZGrhPYf9KL2M8o88kZ6o 9Frw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=jdEqE2Wn; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y19-20020a1709027c9300b001b3d5fdd1c3si9115237pll.188.2023.06.16.14.05.45; Fri, 16 Jun 2023 14:06:00 -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=jdEqE2Wn; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233019AbjFPUuA (ORCPT + 99 others); Fri, 16 Jun 2023 16:50:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60952 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229561AbjFPUt7 (ORCPT ); Fri, 16 Jun 2023 16:49:59 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8A18335B0; Fri, 16 Jun 2023 13:49:58 -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=nf8z9XousGG+fVE7OsptakvEUAwhGZgWUXM8tGBA97M=; b=jdEqE2Wn/cO1xvbzkNfLi+Atgo jR6e5hb9TOYewjSGCf0W1Httwa9X92uNwLzho6/sTGvZH3jUNpHgHOjya1oB0y2kMwB62re10s1zD MiydOAT7bkzDbqSpFuGWcBjS3q9Rql9zz53tgrdi0GO99joBx5vMwyjF9+pXq1A9tMM0=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1qAGOE-00Gl5j-KY; Fri, 16 Jun 2023 22:49:50 +0200 Date: Fri, 16 Jun 2023 22:49:50 +0200 From: Andrew Lunn To: "Radu Pirea (NXP OSS)" Cc: hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, sebastian.tobuschat@nxp.com Subject: Re: [PATCH net-next v1 06/14] net: phy: add 1000baseT1 to phy_basic_t1_features Message-ID: References: <20230616135323.98215-1-radu-nicolae.pirea@oss.nxp.com> <20230616135323.98215-7-radu-nicolae.pirea@oss.nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230616135323.98215-7-radu-nicolae.pirea@oss.nxp.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, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED 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 On Fri, Jun 16, 2023 at 04:53:15PM +0300, Radu Pirea (NXP OSS) wrote: > Add 1000baseT1 bit to phy_basic_t1_features. Please add an explanation why this is safe. For example, why the RTL9000AA does not start saying it supports 1000BaseT1_Full. Has 1000BaseT1_Full been standardised? If there a feature bit in a register to indicate the hardware supports it? That would be the preferred method to determine what the hardware can do. Andrew