linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vz@mleia.com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 07/19] ARM: imx legacy: qong: move peripheral initialization to .init_late
Date: Mon, 19 Sep 2016 04:37:19 +0300	[thread overview]
Message-ID: <1474249051-10718-7-git-send-email-vz@mleia.com> (raw)
In-Reply-To: <1474248988-10626-1-git-send-email-vz@mleia.com>

The change moves some of peripheral registrations and initializations
(all peripherals dependent on GPIOs) from .init_machine to .init_late
level, this allows to safely shift the shared GPIO controller driver
initialization level after init level of i.MX IOMUXC driver.

Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
---
 arch/arm/mach-imx/mach-qong.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/mach-imx/mach-qong.c b/arch/arm/mach-imx/mach-qong.c
index 34df64f..8c2cbd6 100644
--- a/arch/arm/mach-imx/mach-qong.c
+++ b/arch/arm/mach-imx/mach-qong.c
@@ -251,7 +251,6 @@ static void __init qong_init(void)
 
 	mxc_init_imx_uart();
 	qong_init_nor_mtd();
-	qong_init_fpga();
 	imx31_add_imx2_wdt();
 }
 
@@ -268,5 +267,6 @@ MACHINE_START(QONG, "Dave/DENX QongEVB-LITE")
 	.init_irq = mx31_init_irq,
 	.init_time	= qong_timer_init,
 	.init_machine = qong_init,
+	.init_late	= qong_init_fpga,
 	.restart	= mxc_restart,
 MACHINE_END
-- 
2.8.1

  parent reply	other threads:[~2016-09-19  1:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19  1:36 [PATCH 00/19] ARM: imx legacy: move peripheral initializations to .init_late Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 01/19] ARM: imx legacy: kzm: move peripheral initialization " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 02/19] ARM: imx legacy: mx31lite: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 03/19] ARM: imx legacy: mx31ads: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 04/19] ARM: imx legacy: mx31lilly: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 05/19] ARM: imx legacy: pcm037: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 06/19] ARM: imx legacy: mx31-3ds: " Vladimir Zapolskiy
2016-09-19  1:37 ` Vladimir Zapolskiy [this message]
2016-09-19  1:37 ` [PATCH 08/19] ARM: imx legacy: armadillo5x0: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 09/19] ARM: imx legacy: mx31moboard: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 10/19] ARM: imx legacy: vpr200: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 11/19] ARM: imx legacy: imx27-visstrim-m10: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 12/19] ARM: imx legacy: mx27-3ds: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 13/19] ARM: imx legacy: mx35-3ds: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 14/19] ARM: imx legacy: apf9328: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 15/19] ARM: imx legacy: scb9328: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 16/19] ARM: imx legacy: pcm043: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 17/19] ARM: imx legacy: mx21ads: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 18/19] ARM: imx legacy: mx27ads: " Vladimir Zapolskiy
2016-09-19  1:37 ` [PATCH 19/19] ARM: imx legacy: pca100: " Vladimir Zapolskiy
2016-09-20 14:43 ` [PATCH 00/19] ARM: imx legacy: move peripheral initializations " Shawn Guo

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=1474249051-10718-7-git-send-email-vz@mleia.com \
    --to=vz@mleia.com \
    --cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).