The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: broonie@kernel.org
Cc: shawn.guo@linaro.org, linux-kernel@vger.kernel.org,
	thierry.reding@gmail.com,
	Fabio Estevam <fabio.estevam@freescale.com>
Subject: [PATCH] regulator: core: Use postcore_initcall(regulator_init_complete)
Date: Mon, 25 Nov 2013 19:57:35 -0200	[thread overview]
Message-ID: <1385416655-7859-1-git-send-email-festevam@gmail.com> (raw)

From: Fabio Estevam <fabio.estevam@freescale.com>

Commit 22ceeee1 (pwm-backlight: Add power supply support) introduced the usage
of regulator API into the pwm backlight driver and caused a regression on some 
boards like mx28evk and mx6qsabresd, resulting in blank display output:

pwm-backlight backlight.18: dummy supplies not allowed

Calling regulator_init_complete via late_initcall can be too 'late' for the 
regulator to be available for the pwm backlight driver.

Call regulator_init_complete with postcore_initcall level instead.

Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
---
 drivers/regulator/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 3fe1313..d908a95 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -3850,4 +3850,4 @@ unlock:
 
 	return 0;
 }
-late_initcall(regulator_init_complete);
+postcore_initcall(regulator_init_complete);
-- 
1.8.1.2


             reply	other threads:[~2013-11-25 21:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 21:57 Fabio Estevam [this message]
2013-11-26  0:46 ` [PATCH] regulator: core: Use postcore_initcall(regulator_init_complete) Mark Brown
2013-11-27  0:55   ` Mark Brown
2013-12-15 13:06     ` Shawn Guo
2013-12-15 17:03       ` Fabio Estevam
2013-12-16  8:40         ` 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=1385416655-7859-1-git-send-email-festevam@gmail.com \
    --to=festevam@gmail.com \
    --cc=broonie@kernel.org \
    --cc=fabio.estevam@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=thierry.reding@gmail.com \
    /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