Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp121612ybn; Thu, 3 Oct 2019 02:33:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqyXY65Jd2mcFyNv/8QCkmKAZ7F4TwQAQrVyGWtpUfUOOK/rmMbwaJ1zB/2tg440vR/OU/Lz X-Received: by 2002:aa7:d844:: with SMTP id f4mr6332476eds.269.1570095192049; Thu, 03 Oct 2019 02:33:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570095192; cv=none; d=google.com; s=arc-20160816; b=fiFKPhaTsCgMa5yWyFnzpUkfAd2yvNofuUYfPYjbFzMNInuTm2G8iWFePlyoAfp68s 5fGNpBG/yO2zO88+2IS5eFOOI99U3oj45sXGIhpEOjc8NU8VtoO1v/2RaOqldLBE4qFC MiHsxm0Eqrc1TYi0wZFcibWCYtj2/ybkyFScptu2Cb2EQ3ZH2TU9y2NQHtiTHyjX3BYI 57rHUX0JfMUWeJp7+hqt+EDK8bh93nac+oW/nOq6rR6taiWwgw8FMYxOYnU4qDoiIhMy JV/hF9cfIuok/tNb/42usgrgOZrhzNzyIxPiqCCGvfhFw5d7q9pf+RO+DgLZneo57Sio pGWg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=P9zTt6JVcLBVKsSp0EGZr4X1HHOjTST4nbJcuG2gmb0=; b=eWmYkBuKk68SAgLa3XTM6dMf6cSYIbi1TFLuW9hM+6M5mpEzSSC+zOO04U59A6pBWH 4WPzOHhpk53sTFqeIUoXdTHO2hDYg+mN8q+XAKEufxA2Y2Qe20pN5XhDed3n4yJ48ofM qJs3C5a45kjJkRF9+VQM0arv8Yd1m2/ScEKiGEyDDVgybHOe8WCtezxF+j8exxYmFPHe kyWbiVonHmqG+UXyUuLFVsWN9FQX3xc1SPEXQbnIot1vGBf6lxgU004R0Ai5Y3Iwmm62 i6MknqFR8v/LpEWyRriD4wNH/uMOHFPLAnsz48uKQ1OedvMz4s6uIlnIw83R+G/3KBj2 VD5Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b="Ws2T/1yg"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p28si948093ejn.88.2019.10.03.02.32.47; Thu, 03 Oct 2019 02:33:12 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b="Ws2T/1yg"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728963AbfJCJb6 (ORCPT + 99 others); Thu, 3 Oct 2019 05:31:58 -0400 Received: from fllv0015.ext.ti.com ([198.47.19.141]:42348 "EHLO fllv0015.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728743AbfJCJb6 (ORCPT ); Thu, 3 Oct 2019 05:31:58 -0400 Received: from lelv0266.itg.ti.com ([10.180.67.225]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id x939Vrnj054353; Thu, 3 Oct 2019 04:31:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1570095113; bh=P9zTt6JVcLBVKsSp0EGZr4X1HHOjTST4nbJcuG2gmb0=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=Ws2T/1ygmfuTnYSc0i15+fJsvQsMVPI1/XArSZ/lUPr90FyyLlP9GMblLFbXCfoL7 nWup/dphJ872DsMqfjVZ2qGwTXdBUItyAS9ZJN1x+rf1ykG2NArC+pXUhHp7IUdPd4 nQIW+2PJFqlf3Y3ShmGDC7NdoPHpvmGr4YK5kZLw= Received: from DLEE109.ent.ti.com (dlee109.ent.ti.com [157.170.170.41]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x939VrZ1082190 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 3 Oct 2019 04:31:53 -0500 Received: from DLEE105.ent.ti.com (157.170.170.35) by DLEE109.ent.ti.com (157.170.170.41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 3 Oct 2019 04:31:42 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DLEE105.ent.ti.com (157.170.170.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Thu, 3 Oct 2019 04:31:42 -0500 Received: from [10.250.98.116] (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id x939VpeZ102890; Thu, 3 Oct 2019 04:31:51 -0500 Subject: Re: [PATCH] ARM: dts: am335x-sancloud-bbe: Fix PHY mode for ethernet To: Jeroen Hofstee , "linux-omap@vger.kernel.org" CC: Koen Kooi , =?UTF-8?Q?Beno=c3=aet_Cousson?= , Tony Lindgren , open list References: <20191002095416.19603-1-jhofstee@victronenergy.com> <436f1712-7dec-db40-d08f-1a3032af3596@victronenergy.com> From: Grygorii Strashko Message-ID: Date: Thu, 3 Oct 2019 12:31:49 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <436f1712-7dec-db40-d08f-1a3032af3596@victronenergy.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/10/2019 11:16, Jeroen Hofstee wrote: > Hello Grygorri, > > On 10/2/19 4:48 PM, Grygorii Strashko wrote: >> >> >> On 02/10/2019 12:54, Jeroen Hofstee wrote: >>> cd28d1d6e52e: ("net: phy: at803x: Disable phy delay for RGMII mode") >>> broke >>> the ethernet networking on the beaglebone enhanced. >> >> Above commit is incorrect (by itself) and there are few more commits >> on top of >> it, so pls. update reference to commit(s) >> >> bb0ce4c1517d net: phy: at803x: stop switching phy delay config needlessly >> 6d4cd041f0af net: phy: at803x: disable delay only for RGMII mode >> >> > I don't see why that is relevant. The mention patch introduces a > backwards incompatibility for the device tree. Pls read https://patchwork.kernel.org/patch/10773389/ The patch you've mentioned here is buggy by itself and not related to your fix, but final at803x behavior actually defined by above two commits. I've posted this commit because I was confused when i've checked commit you referenced. The patches you > mention don't fix that and hence are unrelated to this patch. No. but they define new at803x behavior which is: After commits (see above) at803x driver disable RX RGMII delay if phy-mode = "rgmii-txid" or will disable TX RGMII delay if phy-mode = "rgmii-rxid" Before above commits, the at803x driver was keeping RX or TX RGMII delay setting untouched as per bootloader or bootstraping configuration for "rgmii-txid"/"rgmii-rxid". > > Furthermore 4.19 is fine, so there is no need to include it in stable > and have a note to make sure also other patches are required etc. Hence all above patches went in 5.1 it would be correct to mention only 6d4cd041f0af net: phy: at803x: disable delay only for RGMII mode -- Best regards, grygorii