From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 5/5] ARM: nitrogen6x: remove clock gate manipulation from DCD
Date: Wed, 8 Oct 2014 16:04:01 +0200 [thread overview]
Message-ID: <1412777041-23714-5-git-send-email-s.hauer@pengutronix.de> (raw)
In-Reply-To: <1412777041-23714-1-git-send-email-s.hauer@pengutronix.de>
The clock driver will ungate all clocks anyway during startup, so
manipulating them in the DCD has no effect.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
arch/arm/boards/boundarydevices-nitrogen6x/clocks.imxcfg | 7 -------
| 1 -
| 1 -
3 files changed, 9 deletions(-)
delete mode 100644 arch/arm/boards/boundarydevices-nitrogen6x/clocks.imxcfg
diff --git a/arch/arm/boards/boundarydevices-nitrogen6x/clocks.imxcfg b/arch/arm/boards/boundarydevices-nitrogen6x/clocks.imxcfg
deleted file mode 100644
index 55adb60..0000000
--- a/arch/arm/boards/boundarydevices-nitrogen6x/clocks.imxcfg
+++ /dev/null
@@ -1,7 +0,0 @@
-wm 32 MX6_CCM_CCGR0 0x00C03F3F
-wm 32 MX6_CCM_CCGR1 0x0030FC03
-wm 32 MX6_CCM_CCGR2 0x0FFFC000
-wm 32 MX6_CCM_CCGR3 0x3FF00000
-wm 32 MX6_CCM_CCGR4 0x00FFF300
-wm 32 MX6_CCM_CCGR5 0x0F0000C3
-wm 32 MX6_CCM_CCGR6 0x000003FF
diff --git a/arch/arm/boards/boundarydevices-nitrogen6x/flash-header-nitrogen6dl-1g.imxcfg b/arch/arm/boards/boundarydevices-nitrogen6x/flash-header-nitrogen6dl-1g.imxcfg
index d077a65..0773f4d 100644
--- a/arch/arm/boards/boundarydevices-nitrogen6x/flash-header-nitrogen6dl-1g.imxcfg
+++ b/arch/arm/boards/boundarydevices-nitrogen6x/flash-header-nitrogen6dl-1g.imxcfg
@@ -8,4 +8,3 @@ dcdofs 0x400
#include "ram-base.imxcfg"
#include "800mhz_4x128mx16.imxcfg"
-#include "clocks.imxcfg"
diff --git a/arch/arm/boards/boundarydevices-nitrogen6x/flash-header-nitrogen6q-1g.imxcfg b/arch/arm/boards/boundarydevices-nitrogen6x/flash-header-nitrogen6q-1g.imxcfg
index ee3145b..bd4134f 100644
--- a/arch/arm/boards/boundarydevices-nitrogen6x/flash-header-nitrogen6q-1g.imxcfg
+++ b/arch/arm/boards/boundarydevices-nitrogen6x/flash-header-nitrogen6q-1g.imxcfg
@@ -8,4 +8,3 @@ dcdofs 0x400
#include "ram-base.imxcfg"
#include "1066mhz_4x128mx16.imxcfg"
-#include "clocks.imxcfg"
--
2.1.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-10-08 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 14:03 [PATCH 1/5] ARM: nitrogen6x: whitespace cleanup Sascha Hauer
2014-10-08 14:03 ` [PATCH 2/5] ARM: nitrogen6x: update 1066MHz 4x128M16 timing from U-Boot Sascha Hauer
2014-10-08 14:03 ` [PATCH 3/5] ARM: nitrogen6x: Fix Duallite RAM Timing Sascha Hauer
2014-10-08 14:04 ` [PATCH 4/5] ARM: nitrogen6x: Add support for 2GB board variants Sascha Hauer
2014-10-08 14:04 ` Sascha Hauer [this message]
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=1412777041-23714-5-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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