From: Eric Nelson <eric@nelint.com>
To: netdev@vger.kernel.org
Cc: linux@arm.linux.org.uk, andrew@lunn.ch, fugang.duan@nxp.com,
otavio@ossystems.com.br, edumazet@google.com,
troy.kisky@boundarydevices.com, davem@davemloft.net,
u.kleine-koenig@pengutronix.de, Eric Nelson <eric@nelint.com>
Subject: [PATCH 2/3] net: fec: remove QUIRK_HAS_RACC from i.mx27
Date: Sat, 24 Sep 2016 07:42:18 -0700 [thread overview]
Message-ID: <1474728139-9335-3-git-send-email-eric@nelint.com> (raw)
In-Reply-To: <1474728139-9335-1-git-send-email-eric@nelint.com>
According to the i.MX27 reference manual, this SoC does not have support
for the receive accelerator (RACC) register at offset 0x1C4.
http://cache.nxp.com/files/32bit/doc/ref_manual/MCIMX27RM.pdf
Signed-off-by: Eric Nelson <eric@nelint.com>
---
drivers/net/ethernet/freescale/fec_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/freescale/fec_main.c b/drivers/net/ethernet/freescale/fec_main.c
index d193406..0219e79 100644
--- a/drivers/net/ethernet/freescale/fec_main.c
+++ b/drivers/net/ethernet/freescale/fec_main.c
@@ -92,7 +92,7 @@ static struct platform_device_id fec_devtype[] = {
.driver_data = FEC_QUIRK_USE_GASKET,
}, {
.name = "imx27-fec",
- .driver_data = FEC_QUIRK_HAS_RACC,
+ .driver_data = 0,
}, {
.name = "imx28-fec",
.driver_data = FEC_QUIRK_ENET_MAC | FEC_QUIRK_SWAP_FRAME |
--
2.7.4
next prev parent reply other threads:[~2016-09-24 14:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 16:43 Alignment issues with freescale FEC driver Eric Nelson
2016-09-23 16:54 ` Eric Dumazet
2016-09-23 17:19 ` Eric Nelson
2016-09-23 17:33 ` Eric Nelson
2016-09-23 18:13 ` Andrew Lunn
2016-09-23 18:30 ` Russell King - ARM Linux
2016-09-23 18:39 ` Eric Nelson
2016-09-23 18:35 ` Eric Nelson
2016-09-24 2:45 ` David Miller
2016-09-24 5:13 ` Andy Duan
2016-09-24 14:42 ` [PATCH 0/3] net: fec: updates to align IP header Eric Nelson
2016-09-24 14:42 ` [PATCH 1/3] net: fec: remove QUIRK_HAS_RACC from i.mx25 Eric Nelson
2016-09-24 14:42 ` Eric Nelson [this message]
2016-09-24 14:42 ` [PATCH 3/3] net: fec: align IP header in hardware Eric Nelson
2016-09-26 9:26 ` David Laight
2016-09-26 18:39 ` Eric Nelson
2016-09-28 16:42 ` David Laight
2016-09-28 17:14 ` Eric Nelson
2016-09-28 17:25 ` Russell King - ARM Linux
2016-09-28 18:01 ` Eric Nelson
2016-09-29 11:07 ` David Laight
2016-09-30 13:27 ` Eric Nelson
2016-09-30 13:49 ` David Laight
2016-09-30 14:16 ` Eric Nelson
2016-10-01 19:52 ` Russell King - ARM Linux
2016-10-03 16:42 ` David Laight
2016-10-03 18:48 ` Eric Nelson
2016-10-08 2:44 ` Andy Duan
2016-09-24 15:09 ` [PATCH 0/3] net: fec: updates to align IP header Andy Duan
2016-09-24 15:29 ` Eric Nelson
2016-09-27 11:40 ` David Miller
2016-09-24 2:43 ` Alignment issues with freescale FEC driver David Miller
2016-09-24 12:27 ` Eric Nelson
2016-09-23 17:37 ` Russell King - ARM Linux
2016-09-23 18:26 ` Eric Nelson
2016-09-23 18:37 ` Russell King - ARM Linux
2016-09-23 18:49 ` Eric Nelson
2016-09-23 20:22 ` Uwe Kleine-König
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=1474728139-9335-3-git-send-email-eric@nelint.com \
--to=eric@nelint.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fugang.duan@nxp.com \
--cc=linux@arm.linux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=otavio@ossystems.com.br \
--cc=troy.kisky@boundarydevices.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).