Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2926483pxb; Mon, 18 Oct 2021 04:58:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx3EAckJtcOQdft5br4Duhn0OxbEzF8HH+FrOxVktCbmkzW7dWsNCnsHn8cfe1QV/pYuab4 X-Received: by 2002:a17:90b:30d6:: with SMTP id hi22mr47722092pjb.4.1634558318495; Mon, 18 Oct 2021 04:58:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634558318; cv=none; d=google.com; s=arc-20160816; b=wZ/ISxXymLb43cDtnWDtmMMf3PDhdYvlOYCq/BJsTg/e4pEwtozu9o/k1ER8rHH3es dqKPbAWzi6vk/pxIED6UjPgGUIBPrcurGpPjQRPtU1e6uXLmZBKqsLDMb6H2nCNY9JAF p1R8g2H8yA4Z1nJ+7pfcGY3hUXUiW38gc2HdO6zWKcf4vKOS7UDnflUpteLdQlpA+Zms UQRH4vNDBjDhq+vuUx6XF49+5FHxPIStU6zDsx/tEW1vnuBohNieoMpMFE4sprW3kN6n 30Hspm3yaUrNYElxldwX+rgPM6NxdOWc77q3lmXW/D4NQATrd1TW/Vvx4bRoH0LzCs4n it1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=umxEonDhuq7wJRPOmYI5y95hbocfVbb1Z5tS5jIsRAE=; b=mdT2LN5RbNwOeswoRztdnm5aErTC97AtGobwWHsfthuD5azfAr27FscvmuDa5BKqvF 4buxL5+Dk5L3p5fpX+nLD8qMb+VpKubLOSmG7t7XnLuTZr8Z2xWOxDJ3G7pOoMoxdbaD xyPGSLkkjrmvRv9GA0mlTVdPFQmDpCDQtSu8uFpYvoZF1LE8qgxjwylxwhvaaf6Du1Go Csm0L86+Bn3Xy6ut6Dy8AyPSSHPzuL+Bi12/U2+I1yU4Zv4gPT1+XTgKr9uX+HvxUJjz qrFkBN9PCuV7a1uWCxVDrkff+onBGFsJ4hT8MHu5OBkY3I1JbziWZe/bcfU4GHxCfqJb vpaQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u63si2530154pgd.111.2021.10.18.04.58.24; Mon, 18 Oct 2021 04:58:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231216AbhJRL7j (ORCPT + 99 others); Mon, 18 Oct 2021 07:59:39 -0400 Received: from pegase2.c-s.fr ([93.17.235.10]:46085 "EHLO pegase2.c-s.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229519AbhJRL7j (ORCPT ); Mon, 18 Oct 2021 07:59:39 -0400 Received: from localhost (mailhub3.si.c-s.fr [172.26.127.67]) by localhost (Postfix) with ESMTP id 4HXwNQ3pXVz9sSg; Mon, 18 Oct 2021 13:57:26 +0200 (CEST) X-Virus-Scanned: amavisd-new at c-s.fr Received: from pegase2.c-s.fr ([172.26.127.65]) by localhost (pegase2.c-s.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RL3x8vznDKhL; Mon, 18 Oct 2021 13:57:26 +0200 (CEST) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase2.c-s.fr (Postfix) with ESMTP id 4HXwNQ2lbsz9sSY; Mon, 18 Oct 2021 13:57:26 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 466508B76C; Mon, 18 Oct 2021 13:57:26 +0200 (CEST) X-Virus-Scanned: amavisd-new at c-s.fr Received: from messagerie.si.c-s.fr ([127.0.0.1]) by localhost (messagerie.si.c-s.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id MRjVM3w8MEjt; Mon, 18 Oct 2021 13:57:26 +0200 (CEST) Received: from PO20335.IDSI0.si.c-s.fr (unknown [172.25.230.103]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 102D18B763; Mon, 18 Oct 2021 13:57:26 +0200 (CEST) Subject: Re: [PATCH net-next] phy: micrel: ksz8041nl: do not use power down mode To: Francesco Dolcini , f.fainelli@gmail.com, Andrew Lunn , Sergei Shtylyov Cc: Heiner Kallweit , Russell King , "David S. Miller" , Jakub Kicinski , Stefan Agner , Marcel Ziswiler , netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <20211018094256.70096-1-francesco.dolcini@toradex.com> <180289ac-4480-1e4c-d679-df4f0478ec65@csgroup.eu> <20211018101802.GA7669@francesco-nb.int.toradex.com> <20211018112735.GB7669@francesco-nb.int.toradex.com> From: Christophe Leroy Message-ID: Date: Mon, 18 Oct 2021 13:57:25 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <20211018112735.GB7669@francesco-nb.int.toradex.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr-FR Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org +Sergei Shtylyov Adding Sergei Shtylyov in the discussion, as he submitted the patch for the support of KSZ8041RNLI. Le 18/10/2021 à 13:27, Francesco Dolcini a écrit : > On Mon, Oct 18, 2021 at 12:46:14PM +0200, Christophe Leroy wrote: >> >> >> Le 18/10/2021 à 12:18, Francesco Dolcini a écrit : >>> Hello Christophe, >>> >>> On Mon, Oct 18, 2021 at 11:53:03AM +0200, Christophe Leroy wrote: >>>> >>>> >>>> Le 18/10/2021 à 11:42, Francesco Dolcini a écrit : >>>>> From: Stefan Agner >>>>> >>>>> Some Micrel KSZ8041NL PHY chips exhibit continous RX errors after using >>>>> the power down mode bit (0.11). If the PHY is taken out of power down >>>>> mode in a certain temperature range, the PHY enters a weird state which >>>>> leads to continously reporting RX errors. In that state, the MAC is not >>>>> able to receive or send any Ethernet frames and the activity LED is >>>>> constantly blinking. Since Linux is using the suspend callback when the >>>>> interface is taken down, ending up in that state can easily happen >>>>> during a normal startup. >>>>> >>>>> Micrel confirmed the issue in errata DS80000700A [*], caused by abnormal >>>>> clock recovery when using power down mode. Even the latest revision (A4, >>>>> Revision ID 0x1513) seems to suffer that problem, and according to the >>>>> errata is not going to be fixed. >>>>> >>>>> Remove the suspend/resume callback to avoid using the power down mode >>>>> completely. >>>> >>>> As far as I can see in the ERRATA, KSZ8041 RNLI also has the bug. >>>> Shoudn't you also remove the suspend/resume on that one (which follows in >>>> ksphy_driver[]) >>> >>> Yes, I could, however this patch is coming out of a real issue we had with >>> KSZ8041NL with this specific phy id (and we have such a patch in our linux >>> branch since years). >>> >>> On the other hand the entry for KSZ8041RNLI in the driver is somehow weird, >>> since the phy id according to the original commit does not even exists on >>> the datasheet. Would you be confident applying such errata for that phyid >>> without having a way of testing it? >> >> >> If your patch was to add the suspend/resume capability I would agree with >> you, but here we are talking about removing it, so what risk are we taking ? > yes, you are right. > >> In addition, commit 4bd7b5127bd0 ("micrel: add support for KSZ8041RNLI") >> clearly tells that the only thing it did was to copy KSZ8041NL entry, so for >> me updating both entries would really make sense. >> >> It looks odd to me that you refer in your commit log to an ERRATA that tells >> you that the bug also exists on the KSZ8041RNLI and you apply it only >> partly. > > I think I was not clear enough, the entry I changed should already cover > KSZ8041RNLI, the phyid is supposed to be just the same according to the > datasheet. This entry for KSZ8041RNLI seems really special with this > un-documented phyid. > But I'm just speculating, I do not have access to these hardware. > > Said that if there are no concern from anybody else, to be on the safe/cautious > side, I can just update also this entry. > > Francesco >