From: kernel@martin.sperl.org (kernel at martin.sperl.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] memory: bcm2835: enable driver early in the boot process
Date: Fri, 20 May 2016 07:23:17 +0000 [thread overview]
Message-ID: <1463728997-8241-3-git-send-email-kernel@martin.sperl.org> (raw)
In-Reply-To: <1463728997-8241-1-git-send-email-kernel@martin.sperl.org>
From: Martin Sperl <kernel@martin.sperl.org>
Enable the critical sdram-clocks early during the boot process,
so that these clocks (and their PLLs) can not get disabled
when a different driver disables its clocks again because
it failed to probe propperly (maybe deferred).
Signed-off-by: Martin Sperl <kernel@martin.sperl.org>
---
drivers/memory/bcm2835-sdram.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/drivers/memory/bcm2835-sdram.c b/drivers/memory/bcm2835-sdram.c
index 9d8cce2..7b6406d 100644
--- a/drivers/memory/bcm2835-sdram.c
+++ b/drivers/memory/bcm2835-sdram.c
@@ -431,6 +431,9 @@ static int bcm2835_sdram_probe(struct platform_device *pdev)
/* setup debugfs */
bcm2835_sdram_debugfs(pdev);
+ /* note that we have registered sdram */
+ dev_dbg(&pdev->dev, "registered sdram\n");
+
return 0;
}
@@ -457,7 +460,12 @@ static struct platform_driver bcm2835_sdram_driver = {
.of_match_table = bcm2835_sdram_of_match_table,
},
};
-module_platform_driver(bcm2835_sdram_driver);
+
+static int __init __bcm2835_sdram_driver_init(void)
+{
+ return platform_driver_register(&bcm2835_sdram_driver);
+}
+core_initcall_sync(__bcm2835_sdram_driver_init);
MODULE_AUTHOR("Martin Sperl");
MODULE_DESCRIPTION("sdram driver for bcm2835 chip");
--
2.1.4
prev parent reply other threads:[~2016-05-20 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 7:23 [PATCH 0/2] ARM: bcm2835: probe clock and sdram driver early kernel at martin.sperl.org
2016-05-20 7:23 ` [PATCH 1/2] clk: bcm2835: register clocks early kernel at martin.sperl.org
2016-05-20 7:23 ` kernel at martin.sperl.org [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=1463728997-8241-3-git-send-email-kernel@martin.sperl.org \
--to=kernel@martin.sperl.org \
--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).