From patchwork Wed Nov 21 11:21:08 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Magnus Damm X-Patchwork-Id: 1001104 Return-Path: X-Original-To: patchwork-incoming-netdev@ozlabs.org Delivered-To: patchwork-incoming-netdev@ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=netdev-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="En1k98Hd"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 430KrN69mLz9s3l for ; Wed, 21 Nov 2018 22:20:52 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730194AbeKUVyv (ORCPT ); Wed, 21 Nov 2018 16:54:51 -0500 Received: from mail-pl1-f193.google.com ([209.85.214.193]:41385 "EHLO mail-pl1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726016AbeKUVyv (ORCPT ); Wed, 21 Nov 2018 16:54:51 -0500 Received: by mail-pl1-f193.google.com with SMTP id u6so5110665plm.8; Wed, 21 Nov 2018 03:20:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:date:message-id:subject; bh=nw6dc5iZbSCPR03grqUq+UNCgBQdZ4fARGVnrZPG1Kw=; b=En1k98HdNtd3kRcWX2E33XTbSmzakcaDsYhFBVollVQtb3H0NGZ0cl7ARgqWwDNTqf H1LaidqbITEf0HZA8Fatak3j+QPbvxy5wZxCs7Epv0h2yZi0y2xB5kl+vy2YOAiIKM0x MKzqzDa8sTcM8GZkv7d3RGWTn6Ct/tRO5vyMnvxsyy8b/rElQRdAC0vfOLfoXcc595o8 cD34Oc35Ls83X8RzCzDzaeLS6+pVxdiDJJdfW5WG8YeMJoHjoZxucal7CmGlNtz+nCz3 Fh4QC62upVIOOiwfrOl+OzWIsnoytJM5BVXoAgqsxDxbR//0Ov5Ss9rK70Q9NOfApv12 Wx+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:date:message-id:subject; bh=nw6dc5iZbSCPR03grqUq+UNCgBQdZ4fARGVnrZPG1Kw=; b=g0mBYFVHT1sb9zXyoqPJVq5wppja65DKV0l82eIPNzX5JaI9buN31RshVRKVg+Jv3O WbTzPR2ABtZEGA0Qc3g/yxdHezAQm1pzHJczRzxuDLRIm6XRQk8zjb0VvJcnV8ReKYAi E00qh7SstmAmi1qY3xqa6FkFwQvG6h1WVAMs8z/6qTx5Ml/unG5h4IbXxi9l9ocHunUb 1dPfnbZeIoIAcrtA2ysrH/T5anO83pAbw4QIkKOMxwzirStXZclVI8TGLhUCLvTJIrne UeoxuGrwliyS10GUV5b4kKwitwc3zD8hCtQmmeSWXBS055pn3etYSMDNsICM2mgpCoFW ZQbQ== X-Gm-Message-State: AA+aEWbBGGY9T9S461rn6oizrLxiwS8xZuioV4r9GDbKBqlXnISApsul f2Vbu5FhD5xEcThAEGHzrHNyBSDf X-Google-Smtp-Source: AFSGD/Vs4iIIpoTJzPgaV8BVzwRY1BDvQdqhNSWniH2jHVGhHIZ9ZYd0RubMeFCYamZr4oQfnpFJag== X-Received: by 2002:a63:d208:: with SMTP id a8mr5477835pgg.77.1542799250131; Wed, 21 Nov 2018 03:20:50 -0800 (PST) Received: from [127.0.0.1] (l193216.ppp.asahi-net.or.jp. [218.219.193.216]) by smtp.gmail.com with ESMTPSA id v9sm19598438pfe.49.2018.11.21.03.20.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Nov 2018 03:20:48 -0800 (PST) From: Magnus Damm To: netdev@vger.kernel.org Cc: linux-renesas-soc@vger.kernel.org, Magnus Damm , davem@davemloft.net, sergei.shtylyov@cogentembedded.com Date: Wed, 21 Nov 2018 20:21:08 +0900 Message-Id: <154279926877.10272.700833429936129422.sendpatchset@octo> Subject: [PATCH v3 00/02] ravb: Duplex handling update V3 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org ravb: Duplex handling update V3 [PATCH v3 01/02] ravb: Do not announce HDX as supported [PATCH v3 02/02] ravb: Clean up duplex handling This series is V3 of duplex handling improvements for the Ethernet-AVB driver. Previous versions of this series have been posted to linux-renesas-soc as RFC so V3 is the first actual version to make it to netdev. Based on the latest data sheet for R-Car Gen3 [1] and R-Car Gen2 [2] the following information is part of the EthernetAVB-IF overview page: Transfer speed: Supports transfer at 100 and 1000 Mbps Mode: Full-duplex mode It seems that the driver implementation is not matching the information provided in the friendly data sheet, and on top of this during run-time when changing PHY configuration of the link partner the Ethernet-AVB PHY seems to want to announce unsupported modes. [1] R-Car Series, 3rd Generation Rev.1.00 (Apr 2018) [2] R-Car Series, 2nd Generation Rev.2.00 (Feb 2016) Changes since V2: - Updated patch 1/2 to make use of phy_remove_link_mode() - Added Reviewed-by from Sergei - thanks! Changes since V1: - Updated patches to reflect input from Sergei and Geert - thanks! Fixes: c156633f1353 ("Renesas Ethernet AVB driver proper") Signed-off-by: Magnus Damm Reviewed-by: Sergei Shtylyov --- Applies on top of next-20181121 drivers/net/ethernet/renesas/ravb.h | 1 - drivers/net/ethernet/renesas/ravb_main.c | 23 +++++------------------ 2 files changed, 5 insertions(+), 19 deletions(-)