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=-5.4 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 34557C433E7 for ; Mon, 19 Oct 2020 22:04:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D09E3222C4 for ; Mon, 19 Oct 2020 22:04:26 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="nveUUfQp" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387784AbgJSWEZ (ORCPT ); Mon, 19 Oct 2020 18:04:25 -0400 Received: from fllv0015.ext.ti.com ([198.47.19.141]:33034 "EHLO fllv0015.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387769AbgJSWEZ (ORCPT ); Mon, 19 Oct 2020 18:04:25 -0400 Received: from lelv0265.itg.ti.com ([10.180.67.224]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 09JM4KIj092427; Mon, 19 Oct 2020 17:04:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1603145060; bh=pnz3UJFNyqq3sSTb/cZZbI8gtpJFd/d/kMZP1jLkPwI=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=nveUUfQpVF42Tj6ojRtF2O7tDUHWMEmepO+VR1xkdmZMICVYSmaz5OXlr33XAqR4q jmy/mX6R++Oj7XSmXDVpgHJY6t9FyrS6Q6vqX422mXd5bQdGbzdRu001JMmF/PlPYu asn6jm3wwtZi6kBcF6P5ezrKfMG7wqgW6iCMn3sQ= Received: from DFLE107.ent.ti.com (dfle107.ent.ti.com [10.64.6.28]) by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 09JM4KF8084586 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 19 Oct 2020 17:04:20 -0500 Received: from DFLE111.ent.ti.com (10.64.6.32) by DFLE107.ent.ti.com (10.64.6.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3; Mon, 19 Oct 2020 17:04:20 -0500 Received: from lelv0327.itg.ti.com (10.180.67.183) by DFLE111.ent.ti.com (10.64.6.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3 via Frontend Transport; Mon, 19 Oct 2020 17:04:20 -0500 Received: from [10.250.70.26] (ileax41-snat.itg.ti.com [10.172.224.153]) by lelv0327.itg.ti.com (8.15.2/8.15.2) with ESMTP id 09JM4JDw099703; Mon, 19 Oct 2020 17:04:19 -0500 Subject: Re: [PATCH net-next 2/2] net: phy: dp83td510: Add support for the DP83TD510 Ethernet PHY To: Andrew Lunn CC: , , , , References: <20201008162347.5290-1-dmurphy@ti.com> <20201008162347.5290-3-dmurphy@ti.com> <20201016220240.GM139700@lunn.ch> <31cbfec4-3f1c-d760-3035-2ff9ec43e4b7@ti.com> <20201019215506.GY139700@lunn.ch> From: Dan Murphy Message-ID: <4add1229-ad74-48e9-064d-e12d62ecc574@ti.com> Date: Mon, 19 Oct 2020 17:04:19 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20201019215506.GY139700@lunn.ch> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andrew On 10/19/20 4:55 PM, Andrew Lunn wrote: > On Mon, Oct 19, 2020 at 04:33:18PM -0500, Dan Murphy wrote: >> Andrew >> >> On 10/16/20 5:02 PM, Andrew Lunn wrote: >>> On Thu, Oct 08, 2020 at 11:23:47AM -0500, Dan Murphy wrote: >>>> The DP83TD510E is an ultra-low power Ethernet physical layer transceiver >>>> that supports 10M single pair cable. >>> Hi Dan >>> >>> I think you are going to have to add >>> ETHTOOL_LINK_MODE_10baseT1_Full_BIT? We already have 100T1 and 1000T1, >>> but not 10T1 :-( >> The data sheet says 10baseT1L.  Which is not there either and seems to be >> the latest 802.3cg spec and has a greater max distance and used for IoT and >> Automotive. > Hi Dan > > Do you know anything about interropibility? Can a T1 and a T1L talk to > each other, if suitably close? I'm wondering if this device should say > it is both T1 and T1L? Or just T1L? I personally don't know about interoperability my tests were T1L to T1L but I forwarded these questions to my HW PHY team. Dan > Andrew