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.0 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 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 BCC5AC3A5A6 for ; Sun, 22 Sep 2019 16:45:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 849FE20830 for ; Sun, 22 Sep 2019 16:45:44 +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="29AgFZfq" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388061AbfIVQpc (ORCPT ); Sun, 22 Sep 2019 12:45:32 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:59178 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387634AbfIVQpc (ORCPT ); Sun, 22 Sep 2019 12:45:32 -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=1m73hiKgDlbgXkWMZgeWL8NAAMGVSlnpLoJM6IyuyCI=; b=29AgFZfqHl7qToIW5JZpAf6IP2 k1FvEnNN75otJq0QcE9uXVA3lkLxZ1WLX+6uuspDSknQR45zKvdjS6dJYsoGJwSQQWJhsLyb2pJ9J 4oWjR+SW1crdQsaiCDJrkALmEwBH0iS4vrjjr2iFfCtoAZeViUOA5Gk0geFR2fLQ8OBk=; Received: from andrew by vps0.lunn.ch with local (Exim 4.89) (envelope-from ) id 1iC4zI-0007NT-4R; Sun, 22 Sep 2019 18:45:28 +0200 Date: Sun, 22 Sep 2019 18:45:28 +0200 From: Andrew Lunn To: Russell King Cc: Florian Fainelli , Heiner Kallweit , tinywrkb , "David S. Miller" , netdev@vger.kernel.org Subject: Re: [PATCH 4/4] net: phy: at803x: use operating parameters from PHY-specific status Message-ID: <20190922164528.GD27014@lunn.ch> References: <20190922105932.GP25745@shell.armlinux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Sun, Sep 22, 2019 at 12:00:25PM +0100, Russell King wrote: > Read the PHY-specific status register for the current operating mode > (speed and duplex) of the PHY. This register reflects the actual > mode that the PHY has resolved depending on either the advertisements > of autoneg is enabled, or the forced mode if autoneg is disabled. > > This ensures that phylib's software state always tracks the hardware > state. > > It seems both AR8033 (which uses the AR8031 ID) and AR8035 support > this status register. AR8030 is not known at the present time. > > Reported-by: tinywrkb > Fixes: 5502b218e001 ("net: phy: use phy_resolve_aneg_linkmode in genphy_read_status") > Signed-off-by: Russell King Reviewed-by: Andrew Lunn Andrew