From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-media@vger.kernel.org
Cc: linux-omap@vger.kernel.org,
sakari.ailus@maxwell.research.nokia.com,
Kalle Jokiniemi <kalle.jokiniemi@nokia.com>,
tony@atomide.com
Subject: [PATCH 2/3] OMAP3: RX-51: define vdds_csib regulator supply
Date: Fri, 15 Jul 2011 20:24:09 +0200 [thread overview]
Message-ID: <1310754250-28788-3-git-send-email-laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <1310754250-28788-1-git-send-email-laurent.pinchart@ideasonboard.com>
From: Kalle Jokiniemi <kalle.jokiniemi@nokia.com>
The RX-51 uses the CSIb IO complex for camera operation. The
board file is missing definition for the regulator supplying
the CSIb complex, so this is added for better power
management.
Signed-off-by: Kalle Jokiniemi <kalle.jokiniemi@nokia.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: tony@atomide.com
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
Tony, can I push this patch through the V4L/DVB tree, or would you like to
pick it yourself ?
diff --git a/arch/arm/mach-omap2/board-rx51-peripherals.c b/arch/arm/mach-omap2/board-rx51-peripherals.c
index 88bd6f7..17e5685 100644
--- a/arch/arm/mach-omap2/board-rx51-peripherals.c
+++ b/arch/arm/mach-omap2/board-rx51-peripherals.c
@@ -361,6 +361,9 @@ static struct omap2_hsmmc_info mmc[] __initdata = {
static struct regulator_consumer_supply rx51_vmmc1_supply =
REGULATOR_SUPPLY("vmmc", "omap_hsmmc.0");
+static struct regulator_consumer_supply rx51_vaux2_supply =
+ REGULATOR_SUPPLY("vdds_csib", "omap3isp");
+
static struct regulator_consumer_supply rx51_vaux3_supply =
REGULATOR_SUPPLY("vmmc", "omap_hsmmc.1");
@@ -424,6 +427,8 @@ static struct regulator_init_data rx51_vaux2 = {
.valid_ops_mask = REGULATOR_CHANGE_MODE
| REGULATOR_CHANGE_STATUS,
},
+ .num_consumer_supplies = 1,
+ .consumer_supplies = &rx51_vaux2_supply,
};
/* VAUX3 - adds more power to VIO_18 rail */
--
1.7.3.4
next prev parent reply other threads:[~2011-07-15 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 18:24 [PATCH 0/3] OMAP3 ISP patches for v3.1 Laurent Pinchart
2011-07-15 18:24 ` [PATCH 1/3] OMAP3: ISP: Add regulator control for omap34xx Laurent Pinchart
2011-07-15 18:24 ` Laurent Pinchart [this message]
2011-07-15 18:24 ` [PATCH 3/3] omap3isp: Support configurable HS/VS polarities Laurent Pinchart
2011-07-20 13:23 ` [PATCH 0/3] OMAP3 ISP patches for v3.1 Sakari Ailus
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=1310754250-28788-3-git-send-email-laurent.pinchart@ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=kalle.jokiniemi@nokia.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sakari.ailus@maxwell.research.nokia.com \
--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).