Received: by 2002:a05:622a:1442:b0:3a5:28ea:c4b9 with SMTP id v2csp746342qtx; Thu, 17 Nov 2022 07:24:09 -0800 (PST) X-Google-Smtp-Source: AA0mqf6ZqQ/i9WfCbChShCwdLpKxqsFQmMHwb6XNsDQYsfNzEXXob9QDByO1jE7QXa1gtq042pjT X-Received: by 2002:a17:90a:9f03:b0:211:59c6:6133 with SMTP id n3-20020a17090a9f0300b0021159c66133mr3247312pjp.238.1668698649119; Thu, 17 Nov 2022 07:24:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668698649; cv=none; d=google.com; s=arc-20160816; b=Mg8nUH3mUXgQb0F2F3COFlOUjxhVlFc213BduKviH4SesMFCqk0o8gMMc3nmPmzMwW RkmbqSz0gKgJui/wVZAnRHn2gRuJBmGJXkzpudIv318uZnj3hRJTGyf8HmK+5JJKiCfP zFY65sP3eK2oXBxKLeDQcIFJMstDz9JvABJaUTKhNBX27NMKbtu0ONArhE/MwC1cj2uY ZXhAf2rVgyKpU1p9E9V0wzW+3m9LcGOXZ1E8pyCdN9M1jg6Un77JD7s1FO1IZWc25x63 +12Y7MtY5nXSZ94iPu4NMA3F/nFj9TXr3UnRRbHQpVQxuOK+hg7tH5dDTMuKPt7fXCrK n8MQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=riDO6qHjkXJO4FMqmQwEaErq/K8CVkbFub7re4pItDY=; b=qOF8SOk4g508wceE+KncyrxgYLtOE7F5+BgH/tGru2R4C3a1hkGKXJNZ8NA+X1lFFf 2r+XM9kCOTrgWkWp68npbvkwHD69YJuVdHEsOhKzvRmdYIBnKpa5bYcRWVycgkY9XUDy UJGbel5GLwdibpYvac1EE1wf7QV6qt66y31VdVZRaOCCmQkhyUr//bNEUw8XEyY83vI+ tipn8vmXv0/yluYTjgoJ4mUPkKJrJW0mb30ymTQ4uAd+SUWD8WyK+k5VfaX30YKUkdrI pmwiKuu4Xd10xAloqn4OEb/obF/DMutuh4ELE0rs6TPICrf2V9N2l2dal203+qw8moAm iKkw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=DBPmY9Vx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id rm1-20020a17090b3ec100b0021823c190aesi1072728pjb.123.2022.11.17.07.23.57; Thu, 17 Nov 2022 07:24:09 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=DBPmY9Vx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234952AbiKQOpT (ORCPT + 92 others); Thu, 17 Nov 2022 09:45:19 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41028 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239263AbiKQOot (ORCPT ); Thu, 17 Nov 2022 09:44:49 -0500 Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9912851338; Thu, 17 Nov 2022 06:44:33 -0800 (PST) Received: by mail-ej1-x62c.google.com with SMTP id ft34so5490671ejc.12; Thu, 17 Nov 2022 06:44:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=riDO6qHjkXJO4FMqmQwEaErq/K8CVkbFub7re4pItDY=; b=DBPmY9VxDmx8RgOYEwV0YLA7Jp25y31ofjo3bMYX9sqNFWGs6XWlG3dy3pC3DEE4KY OY+t9dvDa5aNDhoH1/A6FXkzdPxkHQrGMSAudIM9vzg2UD2GfZzOE0UOS56dXKeKClmI oHO8dP7I2chYnOSlTCbak2/sQERaqDYp4JD5gGW/h0oOJ4k0t+OHd4X9U3yNAT9iISaA 2w6Cus5wH/+ZdOgyVzgT/82NwdHKeP8d4pOa1W9Njy0kS32W1v2dWFRdT8GVsAuqrv+V M1p7BpU6myxNxE3aDuDsvB/BZNYUaqRyXlpTezLtCjfPedgLY2DtNZ0yst4hKGBNA0zU TEpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=riDO6qHjkXJO4FMqmQwEaErq/K8CVkbFub7re4pItDY=; b=P8o2g+2oOLwecUmHt115xfwpBoMvaWrE0xl9QsufDNoWFnm/rqe4OpseZxrd1HECTD v7hc0APJSa8U/Q8kH3fBFDanmG//Fiau+x1CX59sUgpxniMmWS6ltunoqETZWW6fEgJm c2SStULiupI4c1ysaGJ9TntGW21FVV2lF+PQ9OGe5Zll4mAtnS9Q81sLihep8MbYFxU9 Sg+m0IyjNbJjnkMFdz3eo00NOkbvlbL7Ohl64HyS2toByzL0UtUA8QHUxmGPeXDRt5zf Sgq4EnbzZnBNBfBuuZl+wVsrVXVJhsgJDEBzSxYrrA2r1Epd5LJYsFIVIcCZzudxyhcL P2TQ== X-Gm-Message-State: ANoB5plk2SdERxIBt5tMfAeTn+U3nEAykWJOwbA4n4JLnHUiRX8Lk80Z d4tOdkWt4y7MUsExrD9wJGBe+7mPAgLBWos/Iw8BqIggWLkgdQ== X-Received: by 2002:a17:906:c18c:b0:7b2:8a6e:c569 with SMTP id g12-20020a170906c18c00b007b28a6ec569mr2428029ejz.582.1668696272081; Thu, 17 Nov 2022 06:44:32 -0800 (PST) MIME-Version: 1.0 References: <20221116200150.4657-1-linux.amoon@gmail.com> <20221116200150.4657-2-linux.amoon@gmail.com> In-Reply-To: From: Anand Moon Date: Thu, 17 Nov 2022 20:14:16 +0530 Message-ID: Subject: Re: [linux-next-v2 1/5] arm64: dts: rockchip: Fix gmac phy mode to rgmii on Rock 3A SBC. To: Peter Geis Cc: Rob Herring , Krzysztof Kozlowski , Heiko Stuebner , Chukun Pan , Michael Riesch , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Peter On Thu, 17 Nov 2022 at 02:06, Peter Geis wrote: > > On Wed, Nov 16, 2022 at 3:02 PM Anand Moon wrote: > > > > On rk356x ethernet phy support reduced media independent interface (RMII) > > and reduced gigabit media independent interface (RGMII). > > So set the phy mode to rgmii to support clock delay, also > > add TX and RX delay for phy-mode. > > Controller based clock delay, the various rgmii-id modes (rgmii-txid > and rgmii-rxid are also valid) apply the delays in the phy. They are > usually at a fixed amount, but some phys support variable delays. > > You want your commit message to accurately describe the problem, such > as "In rgmii-id mode, the phy on the rock-3a is unreliable due to > incorrect delays. Switch to rgmii mode in order to handle the delays > in the controller." > > > > > Fix following warning > > > > [ 7.365215] rk_gmac-dwmac fe010000.ethernet: Can not read property: tx_delay. > > [ 7.365219] rk_gmac-dwmac fe010000.ethernet: set tx_delay to 0x30 > > [ 7.365224] rk_gmac-dwmac fe010000.ethernet: Can not read property: rx_delay. > > [ 7.365228] rk_gmac-dwmac fe010000.ethernet: set rx_delay to 0x10 > > I've been meaning to make this a dev_debug message, because in the > various rgmii-id modes it is feasible for these to be non-existent in > the device-tree. In rgmii-id mode these are disabled, no matter what > they are set to in the dt. As per the public datasheet share by Radxa below [0] https://dl.radxa.com/rock3/docs/hw/datasheet/RTL8211F-CG-Datasheet.pdf This Ethernet controller supports RGMII mode. > > > > > Signed-off-by: Anand Moon > > --- > > V2: Fix commit message and added the RX and TX clock delay. > > --- > > arch/arm64/boot/dts/rockchip/rk3568-rock-3a.dts | 5 ++++- > > 1 file changed, 4 insertions(+), 1 deletion(-) > > > > diff --git a/arch/arm64/boot/dts/rockchip/rk3568-rock-3a.dts b/arch/arm64/boot/dts/rockchip/rk3568-rock-3a.dts > > index ea74ba32fbbd..e1c75532dcee 100644 > > --- a/arch/arm64/boot/dts/rockchip/rk3568-rock-3a.dts > > +++ b/arch/arm64/boot/dts/rockchip/rk3568-rock-3a.dts > > @@ -253,13 +253,16 @@ &gmac1 { > > assigned-clock-rates = <0>, <125000000>; > > clock_in_out = "output"; > > phy-handle = <&rgmii_phy1>; > > - phy-mode = "rgmii-id"; > > + phy-mode = "rgmii"; > > pinctrl-names = "default"; > > pinctrl-0 = <&gmac1m1_miim > > &gmac1m1_tx_bus2 > > &gmac1m1_rx_bus2 > > &gmac1m1_rgmii_clk > > &gmac1m1_rgmii_bus>; > > + > > + tx_delay = <0x4f>; > > + rx_delay = <0x26>; > > These are pretty far off from the default, have you verified the upper > and lower bounds for the rock-3a? These should be roughly in the > middle of that range. > No I have not tested this way but as per the datasheet, it supports TXDLY Add 2ns delay to RXC for RXD latching (via 4.7k-ohm to DVDD_RG) RXDLY Add 2ns delay to RXC for RXD latching (via 4.7k-ohm to DVDD_RG) I feel I should ignore the above warning and add it below. rx-internal-delay-ps = <2000>; tx-internal-delay-ps = <2000>; Thanks -Anand > > status = "okay"; > > }; > > > > -- > > 2.38.1 > >