From: Sergey Shtylyov <s.shtylyov@omprussia.ru>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: <linux-renesas-soc@vger.kernel.org>
Subject: [PATCH net 2/3] sh_eth: fix TRSCER mask for R7S72100
Date: Sun, 28 Feb 2021 23:26:34 +0300 [thread overview]
Message-ID: <8e901c23-65ad-d76d-5a05-11d9aa7c4fc3@omprussia.ru> (raw)
In-Reply-To: <7009ba70-4134-1acf-42b9-fa7e59b5d15d@omprussia.ru>
According to the RZ/A1H Group, RZ/A1M Group User's Manual: Hardware,
Rev. 4.00, the TRSCER register has bit 9 reserved, hence we can't use
the driver's default TRSCER mask. Add the explicit initializer for
sh_eth_cpu_data::trscer_err_mask for R7S72100.
Fixes: db893473d313 ("sh_eth: Add support for r7s72100")
Signed-off-by: Sergey Shtylyov <s.shtylyov@omprussia.ru>
---
drivers/net/ethernet/renesas/sh_eth.c | 2 ++
1 file changed, 2 insertions(+)
Index: net/drivers/net/ethernet/renesas/sh_eth.c
===================================================================
--- net.orig/drivers/net/ethernet/renesas/sh_eth.c
+++ net/drivers/net/ethernet/renesas/sh_eth.c
@@ -560,6 +560,8 @@ static struct sh_eth_cpu_data r7s72100_d
EESR_TDE,
.fdr_value = 0x0000070f,
+ .trscer_err_mask = DESC_I_RINT8 | DESC_I_RINT5,
+
.no_psr = 1,
.apr = 1,
.mpr = 1,
next prev parent reply other threads:[~2021-02-28 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 20:24 [PATCH net 0/3] Fix TRSCER masks in the Ether driver Sergey Shtylyov
2021-02-28 20:25 ` [PATCH net 1/3] sh_eth: fix TRSCER mask for SH771x Sergey Shtylyov
2021-03-04 8:42 ` Geert Uytterhoeven
2021-02-28 20:26 ` Sergey Shtylyov [this message]
2021-03-04 8:44 ` [PATCH net 2/3] sh_eth: fix TRSCER mask for R7S72100 Geert Uytterhoeven
2021-02-28 20:27 ` [PATCH net 3/3] sh_eth: fix TRSCER mask for R7S9210 Sergey Shtylyov
2021-03-04 8:51 ` Geert Uytterhoeven
2021-03-01 21:30 ` [PATCH net 0/3] Fix TRSCER masks in the Ether driver patchwork-bot+netdevbpf
2021-03-02 16:32 ` Geert Uytterhoeven
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=8e901c23-65ad-d76d-5a05-11d9aa7c4fc3@omprussia.ru \
--to=s.shtylyov@omprussia.ru \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.