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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 B210EC433DF for ; Thu, 28 May 2020 17:17:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9C01720721 for ; Thu, 28 May 2020 17:17:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405481AbgE1RRy (ORCPT ); Thu, 28 May 2020 13:17:54 -0400 Received: from mx2.suse.de ([195.135.220.15]:50168 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2405353AbgE1RRw (ORCPT ); Thu, 28 May 2020 13:17:52 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 067E7ABB2; Thu, 28 May 2020 17:17:50 +0000 (UTC) Received: by lion.mk-sys.cz (Postfix, from userid 1000) id 32B5960347; Thu, 28 May 2020 19:17:51 +0200 (CEST) Date: Thu, 28 May 2020 19:17:51 +0200 From: Michal Kubecek To: netdev@vger.kernel.org Cc: Petr Machata , Andrew Lunn , Amit Cohen , mlxsw , "o.rempel@pengutronix.de" Subject: Re: Link down reasons Message-ID: <20200528171751.jea5p5qxmeqsstdv@lion.mk-sys.cz> References: <20200527213843.GC818296@lunn.ch> <87zh9stocb.fsf@mellanox.com> <20200528154010.GD840827@lunn.ch> <87r1v4t2yn.fsf@mellanox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87r1v4t2yn.fsf@mellanox.com> Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, May 28, 2020 at 06:54:24PM +0200, Petr Machata wrote: > In another e-mail you suggested this: > > Link detected: no (cable issue) > > But if the link just silently falls back to 100Mbps, there would never > be an opportunity for phy to actually report a down reason. So there > probably is no way for the phy layer to make use of this particular > down reason. Perhaps we could use more general name than "link down reason", e.g. "extended state", and it could be reported even if the link is still up (if there is something to report). Michal