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=-2.0 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,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 3757EC34047 for ; Wed, 19 Feb 2020 09:22:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0D35124658 for ; Wed, 19 Feb 2020 09:22:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=armlinux.org.uk header.i=@armlinux.org.uk header.b="Xbq/0U78" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726828AbgBSJWp (ORCPT ); Wed, 19 Feb 2020 04:22:45 -0500 Received: from pandora.armlinux.org.uk ([78.32.30.218]:40034 "EHLO pandora.armlinux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726530AbgBSJWo (ORCPT ); Wed, 19 Feb 2020 04:22:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: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=2gmw5/9ku0lPrufppHRIvdpYWfVdw6IxhC1tSWasJ1c=; b=Xbq/0U78QKnv0b62Wvl6lMzLm B/FLaDW5+HkPwJGMTeR+RQqvTXrXiwcGRqEcUOBwwC9Gqhab6eTJQ4dTkQiUalktx2cmVGb/bDJfO PZBI0yp1iJO7koKijqpP/99yCVPGt85jmtg2FMwAiMKXEwESSqwLqcd4p2Owwkot4RhEu9q3JrjQ4 9OJZV+sDgz/BDEpBb6mj6ZbamX9PIGZrl3zvrgdRj/HvEaLH/NnjHiK61VYk3F8VXkCMQGNqsLOV8 B6KqdA6v84lWOiGAFK/fVskw1dgeVvOcFxuFLKAxxbDyyH3lo4jnMmc+vw6vlpypIgidRTJHfrnZd 5i6FqHoiw==; Received: from shell.armlinux.org.uk ([2002:4e20:1eda:1:5054:ff:fe00:4ec]:49888) by pandora.armlinux.org.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1j4LYs-0004Sb-Pb; Wed, 19 Feb 2020 09:22:30 +0000 Received: from linux by shell.armlinux.org.uk with local (Exim 4.92) (envelope-from ) id 1j4LYp-0001KX-Cp; Wed, 19 Feb 2020 09:22:27 +0000 Date: Wed, 19 Feb 2020 09:22:27 +0000 From: Russell King - ARM Linux admin To: Joel Johnson Cc: "David S. Miller" , Baruch Siach , Gregory Clement , Thomas Petazzoni , Rob Herring , netdev@vger.kernel.org Subject: Re: mvneta: comphy regression with SolidRun ClearFog Message-ID: <20200219092227.GR25745@shell.armlinux.org.uk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Tue, Feb 18, 2020 at 10:14:48PM -0700, Joel Johnson wrote: > In updating recently I'm encountering a regression with the mvneta driver on > SolidRun ClearFog Base devices. I originally filed the bug with Debian > (https://bugs.debian.org/951409) since I was using distro provided packages, > but after further investigation I have isolated the issue as related to > comphy support added during development for kernel version 5.1. > > When booting stock kernels up to 5.0 everything works as expected with three > ethernet devices identified and functional. However, running any kernel 5.1 > or later, I only have a single ethernet device available. The single device > available appears to be the one attached to the SoC itself and not connected > via SerDes lanes using comphy, i.e. the one defined at f1070000.ethernet. > > With some log/diff assisted bisecting, I've been able to confirm that the > "tipping point" changeset is f548ced15f90, which actually performs the DT > change for the ClearFog family of devices. That's the commit at which the > failure starts, but is just the final enablement of the added feature in the > overall series. I've also tested booting the same kernel binary (including > up to v5.6-rc1) and only swapping the dtb for one excluding the problematic > commit and confirmed that simply changing the dtb results in all three > devices being functional, albeit obviously without comphy support. Does debian have support for the comphy enabled in their kernel, which is controlled by CONFIG_PHY_MVEBU_A38X_COMPHY ? -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up