From: Chris Packham <judge.packham@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] net: mvgbe: remove CONFIG_DOVE
Date: Thu, 3 May 2018 23:00:34 +1200 [thread overview]
Message-ID: <20180503110036.15364-1-judge.packham@gmail.com> (raw)
Nothing defines CONFIG_DOVE so remove the code that uses it.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
---
drivers/net/mvgbe.c | 2 --
drivers/net/mvgbe.h | 7 -------
2 files changed, 9 deletions(-)
diff --git a/drivers/net/mvgbe.c b/drivers/net/mvgbe.c
index f833efbe6779..47148e526008 100644
--- a/drivers/net/mvgbe.c
+++ b/drivers/net/mvgbe.c
@@ -27,8 +27,6 @@
#include <asm/arch/soc.h>
#elif defined(CONFIG_ORION5X)
#include <asm/arch/orion5x.h>
-#elif defined(CONFIG_DOVE)
-#include <asm/arch/dove.h>
#endif
#include "mvgbe.h"
diff --git a/drivers/net/mvgbe.h b/drivers/net/mvgbe.h
index 27a3f41e80cd..7a42d70831ed 100644
--- a/drivers/net/mvgbe.h
+++ b/drivers/net/mvgbe.h
@@ -292,17 +292,10 @@
#define EBAR_TARGET_GUNIT 0x00000007
/* Window attrib */
-#if defined(CONFIG_DOVE)
-#define EBAR_DRAM_CS0 0x00000000
-#define EBAR_DRAM_CS1 0x00000000
-#define EBAR_DRAM_CS2 0x00000000
-#define EBAR_DRAM_CS3 0x00000000
-#else
#define EBAR_DRAM_CS0 0x00000E00
#define EBAR_DRAM_CS1 0x00000D00
#define EBAR_DRAM_CS2 0x00000B00
#define EBAR_DRAM_CS3 0x00000700
-#endif
/* DRAM Target interface */
#define EBAR_DRAM_NO_CACHE_COHERENCY 0x00000000
--
2.17.0
next reply other threads:[~2018-05-03 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 11:00 Chris Packham [this message]
2018-05-03 11:00 ` [U-Boot] [PATCH 2/2] net: add Kconfig for MVGBE Chris Packham
2018-05-03 11:17 ` Stefan Roese
2018-05-03 21:36 ` Joe Hershberger
2018-05-03 23:03 ` Chris Packham
2018-05-04 18:47 ` Joe Hershberger
2018-05-15 12:28 ` [U-Boot] [U-Boot,2/2] " Tom Rini
2018-05-03 11:22 ` [U-Boot] [PATCH 1/2] net: mvgbe: remove CONFIG_DOVE Stefan Roese
2018-05-03 15:14 ` Joe Hershberger
2018-05-15 12:28 ` [U-Boot] [U-Boot,1/2] " Tom Rini
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=20180503110036.15364-1-judge.packham@gmail.com \
--to=judge.packham@gmail.com \
--cc=u-boot@lists.denx.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