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=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham 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 09BD2C282CB for ; Fri, 8 Feb 2019 10:37:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AF5FE20857 for ; Fri, 8 Feb 2019 10:37:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Jq/rA/IH" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726655AbfBHKhO (ORCPT ); Fri, 8 Feb 2019 05:37:14 -0500 Received: from mail-pl1-f180.google.com ([209.85.214.180]:39005 "EHLO mail-pl1-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726162AbfBHKhO (ORCPT ); Fri, 8 Feb 2019 05:37:14 -0500 Received: by mail-pl1-f180.google.com with SMTP id 101so1504604pld.6 for ; Fri, 08 Feb 2019 02:37:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=gOuN0McLmaF/pafaa3XLXQ0JlLVtZb0vXlFG2ZPLqKU=; b=Jq/rA/IHdrSENbZe+g6C9MfoxKbyD1biTILMC/zrEjiCJMvIF/RRIjfxRGVOnP3RnD uF9sigFv+QkeKKi4DOrrVLQdcUQoxiQXPObywokRM27IbvbrthvJq1Yos5wxfM4TJmuv +sNOU3jmEHY71eWYmr/wMDL32CwbDaXWEG6/ey/u6EPoBxvGQ66OrmQT3U4NAMzFeKOS wIx365RG1IcVMARYSFszn1m9jCma4hZetjYZS6cDRJmAWrHkNeFVt7Ja9msFbfyqohrJ zod+PSbAbcOyiJQ2MAFjNJOdPmzWkw7cjPDek7O1uA4BxU7oSb5IwQLu6c3xk9EEb2+c MU/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=gOuN0McLmaF/pafaa3XLXQ0JlLVtZb0vXlFG2ZPLqKU=; b=Z6ivYfJq2LxtlMKS/hMgWKzCUyNy10y4HUVu5G8yFbvXqdhWEJM3L+JNwdLrWO5SwS XcujeR20TsiYe392z/A7Pg4ZaW3iaJbMiYe0E43GCYv1THgHfMHzsZwzuOGlGKHX2bhc HDgOU6ZPhrSbdjPCd5Y23UGOPTXYlehXALbCFPMM9AHCT0/DZtCeWWXHUkT7uSVBBMhG iUHAK8HVmLTWh78zHkeohqQhqbnHgI4ZvVIkZI97817Lur81MEu/pBBTabNhHz/B7+kB BHi1270FcPMHyAY54whnX2l04XTrx4YpL45mn8iWM3az97jSfVAQSgZAR2cC7FAqmuRF 0YCg== X-Gm-Message-State: AHQUAuZu2iq0Fa5HLsCV4DpkbzTdLCYybgrSq1IcPgnvG71xWzaotQOY p54fk+84gDb9cwHCqQ5r/A0++yEa X-Google-Smtp-Source: AHgI3IZ35j8MrkRJ9gI51iZGJz7FLThLVtP/00fNbo2AQSRlr1lm9mIqS3OISk1i0IQoFX74/7Mkwg== X-Received: by 2002:a17:902:622:: with SMTP id 31mr21563649plg.171.1549622233045; Fri, 08 Feb 2019 02:37:13 -0800 (PST) Received: from [10.4.1.112] ([103.66.79.45]) by smtp.gmail.com with ESMTPSA id v62sm749583pfk.72.2019.02.08.02.37.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Feb 2019 02:37:12 -0800 (PST) Subject: Re: Is advertising of 2500Mbps support must from phy device to set phy at 2500Mbps link speed To: Andrew Lunn Cc: netdev@vger.kernel.org References: <496b56c8-666a-7c5c-f3c6-0e709584ec0d@gmail.com> <20190205145601.GJ3397@lunn.ch> <20190206133858.GF20405@lunn.ch> From: abhijit Message-ID: <6cbbb9cb-119e-eb7d-e230-6bf496300eb4@gmail.com> Date: Fri, 8 Feb 2019 16:07:10 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20190206133858.GF20405@lunn.ch> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Thanks Andrew for your reply. I will have look at IEEE document and c45. On Wednesday 06 February 2019 07:08 PM, Andrew Lunn wrote: >> Currently, we don't have any phy drivers. Generic driver doesn't seems to >> support 2500Mbps. > Correct. genphy only supports upto 1G. The c45 based genphy_c45 is > slowly gaining more features and might soon support 2.5G. > >> If I have to write the driver, whether it is necessary for >> phy device to advertise speed of 2500Mbps? > The user could force it, using the ethool command you suggested. But > it is the PHY driver which configures this. If you add the driver code > to force it, you might as well add the driver code to allow it to be > negotiated. > >> Phy is custom phy and is currently under test. If you know any phy device >> that supports 2500Mbps and whose data sheet is available freely please let >> me know. > There are none that i know of with open data sheets. However the IEEE > standards should be freely available and they describe the registers > the PHY is expected to have. There are also patches floating around > which add 2.5G and 5G support to the marvell10g driver. I expect these > patches to get merged soon, but maybe in a different form to make > genphy_c45 more generic. > > Andrew