linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Quadros <roger.quadros@nokia.com>
To: Tomi.Valkeinen@nokia.com
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
	linux-fbdev@vger.kernel.org
Subject: [PATCHv3 2/5] OMAP: RX51: Add "vdds_sdi" supply voltage for SDI
Date: Thu, 15 Apr 2010 12:06:18 +0000	[thread overview]
Message-ID: <1271333181-23609-3-git-send-email-roger.quadros@nokia.com> (raw)
In-Reply-To: <1271333181-23609-2-git-send-email-roger.quadros@nokia.com>

From: Roger Quadros <roger.quadros@nokia.com>

The SDI Display subsystem needs access to the vdds_sdi supply
regulator. This is TWL4030's VAUX1 supply on RX-51.

Signed-off-by: Roger Quadros <roger.quadros@nokia.com>
---
 arch/arm/mach-omap2/board-rx51-peripherals.c |   15 +++++++++++++++
 1 files changed, 15 insertions(+), 0 deletions(-)

diff --git a/arch/arm/mach-omap2/board-rx51-peripherals.c b/arch/arm/mach-omap2/board-rx51-peripherals.c
index f404537..3ef805e 100644
--- a/arch/arm/mach-omap2/board-rx51-peripherals.c
+++ b/arch/arm/mach-omap2/board-rx51-peripherals.c
@@ -300,6 +300,19 @@ static struct regulator_consumer_supply rx51_vsim_supply = {
 	.dev_name = "mmci-omap-hs.1",
 };
 
+#if defined(CONFIG_FB_OMAP2) || defined(CONFIG_FB_OMAP2_MODULE)
+extern struct platform_device rx51_display_device;
+#endif
+
+static struct regulator_consumer_supply rx51_vaux1_consumers[] = {
+#if defined(CONFIG_FB_OMAP2) || defined(CONFIG_FB_OMAP2_MODULE)
+	{
+		.supply	= "vdds_sdi",
+		.dev	= &rx51_display_device.dev,
+	},
+#endif
+};
+
 static struct regulator_init_data rx51_vaux1 = {
 	.constraints = {
 		.name			= "V28",
@@ -310,6 +323,8 @@ static struct regulator_init_data rx51_vaux1 = {
 		.valid_ops_mask		= REGULATOR_CHANGE_MODE
 					| REGULATOR_CHANGE_STATUS,
 	},
+	.num_consumer_supplies	= ARRAY_SIZE(rx51_vaux1_consumers),
+	.consumer_supplies	= rx51_vaux1_consumers,
 };
 
 static struct regulator_init_data rx51_vaux2 = {
-- 
1.6.0.4


  reply	other threads:[~2010-04-15 12:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15 12:06 [PATCHv3 0/5] OMAP: RX51: Add LCD Panel Support for N900 Roger Quadros
2010-04-15 12:06 ` [PATCHv3 1/5] OMAP: RX51: Add LCD Panel support Roger Quadros
2010-04-15 12:06   ` Roger Quadros [this message]
2010-04-15 12:06     ` [PATCHv3 3/5] OMAP: RX51: Add Touch Controller in SPI board info Roger Quadros
2010-04-15 12:06       ` [PATCHv3 4/5] OMAP: DSS2: Add ACX565AKM Panel Driver Roger Quadros
2010-04-15 12:06         ` [PATCHv3 5/5] OMAP: RX51: Update board defconfig Roger Quadros
2010-05-06 18:27   ` [PATCHv3 1/5] OMAP: RX51: Add LCD Panel support Kevin Hilman
2010-05-07  7:03     ` Roger Quadros
2010-04-15 12:08 ` [PATCHv3 0/5] OMAP: RX51: Add LCD Panel Support for N900 Roger Quadros
2010-04-15 14:00   ` Grazvydas Ignotas
2010-04-15 14:05     ` Tomi Valkeinen
2010-04-20 12:53 ` Roger Quadros
2010-04-20 14:40   ` Tomi Valkeinen
2010-04-21  7:15     ` Roger Quadros

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=1271333181-23609-3-git-send-email-roger.quadros@nokia.com \
    --to=roger.quadros@nokia.com \
    --cc=Tomi.Valkeinen@nokia.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).