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.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 E8BE2C433E0 for ; Wed, 13 May 2020 18:01:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 85BE4205CB for ; Wed, 13 May 2020 18:01:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="SYsl/Dgy" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390018AbgEMSBt (ORCPT ); Wed, 13 May 2020 14:01:49 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:58502 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732488AbgEMSBs (ORCPT ); Wed, 13 May 2020 14:01:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=dA0dBS/M2ZOOg0j3lay3GFmcbsWG9ZBUT4mX89gO5Zk=; b=SYsl/DgykWYBa+3iZ+2Ezs8zK+ kRxfI7UBuSxWHB82HFivrmaO8bnGbV1KeH/x9sOesVMUcJtRAxRRVlHYsSETD34kmT91yW6Pp3n+a oDB76jwIQHc2GVrH4QdsAY/+RtwmbEfeiYhtxeucIMfB/JbYshb2aUC2Kvcy36PB41f4=; Received: from andrew by vps0.lunn.ch with local (Exim 4.93) (envelope-from ) id 1jYvhM-002Bsq-CQ; Wed, 13 May 2020 20:01:40 +0200 Date: Wed, 13 May 2020 20:01:40 +0200 From: Andrew Lunn To: Oleksij Rempel Cc: Mark Rutland , Marek Vasut , Florian Fainelli , devicetree@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , Pengutronix Kernel Team , David Jander , "David S. Miller" , Heiner Kallweit Subject: Re: [PATCH net-next v1] net: phy: tja11xx: add cable-test support Message-ID: <20200513180140.GK499265@lunn.ch> References: <20200513123440.19580-1-o.rempel@pengutronix.de> <20200513133925.GD499265@lunn.ch> <20200513174011.kl6l767cimeo6dpy@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200513174011.kl6l767cimeo6dpy@pengutronix.de> Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > What would be the best place to do a test before the link is getting up? > Can it be done in the phy core, or it should be done in the PHY driver? > > So far, no action except of logging these errors is needed. You could do it in the config_aneg callback. A kernel log entry is not very easy to use. You might want to see how easy it is to send a cable test result to userspace. Anything which is interested in this information can then listen for it. All the needed code is there, you will just need to rearrange it a bit. Andrew