From: Magnus Damm <magnus.damm@gmail.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH/RFC v2 01/02] ravb: Do not announce HDX as supported
Date: Mon, 20 Aug 2018 23:59:45 +0900 [thread overview]
Message-ID: <153477718520.16950.10138071667883935510.sendpatchset@octo> (raw)
In-Reply-To: <153477717610.16950.5787705338176325405.sendpatchset@octo>
From: Magnus Damm <damm+renesas@opensource.se>
According to the data sheet the Ethernet-AVB hardware in R-Car Gen3
and R-Car Gen2 SoCs do not support half duplex operation. So update
the driver to mark 100Mbit and 1Gbps HDX as unsupported.
Not-Yet-Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
Fixes: c156633f1353 ("Renesas Ethernet AVB driver proper")
Reviewed-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
---
Written on top of next-20180820
drivers/net/ethernet/renesas/ravb_main.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--- 0001/drivers/net/ethernet/renesas/ravb_main.c
+++ work/drivers/net/ethernet/renesas/ravb_main.c 2018-08-20 23:42:46.670859449 +0900
@@ -1076,8 +1076,9 @@ static int ravb_phy_init(struct net_devi
netdev_info(ndev, "limited PHY to 100Mbit/s\n");
}
- /* 10BASE is not supported */
- phydev->supported &= ~PHY_10BT_FEATURES;
+ /* Neither 10BASE nor half duplex are supported */
+ phydev->supported &= ~(PHY_10BT_FEATURES | SUPPORTED_100baseT_Half |
+ SUPPORTED_1000baseT_Half);
phy_attached_info(phydev);
next prev parent reply other threads:[~2018-08-20 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 14:59 [PATCH/RFC v2 00/02] ravb: Duplex handling update V2 Magnus Damm
2018-08-20 14:59 ` Magnus Damm [this message]
2018-08-20 14:59 ` [PATCH/RFC v2 02/02] ravb: Clean up duplex handling Magnus Damm
2018-08-20 15:30 ` Sergei Shtylyov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=153477718520.16950.10138071667883935510.sendpatchset@octo \
--to=magnus.damm@gmail.com \
--cc=linux-renesas-soc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).