From: grinberg@compulab•co.il (Igor Grinberg)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 05/12] Add dummy smsc911x regulators to cm-t35.
Date: Tue, 27 Mar 2012 17:53:52 +0200 [thread overview]
Message-ID: <4F71E290.2050403@compulab.co.il> (raw)
In-Reply-To: <1332494504-10251-6-git-send-email-Russ.Dill@ti.com>
Hi Russ,
This patch works, but can we, please use the attached patch instead?
Thanks
On 03/23/12 11:21, Russ Dill wrote:
> Signed-off-by: Russ Dill <russ.dill@ti•com>
> ---
> arch/arm/mach-omap2/board-cm-t35.c | 9 +++++++++
> 1 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-cm-t35.c b/arch/arm/mach-omap2/board-cm-t35.c
> index 41b0a2f..289ded3 100644
> --- a/arch/arm/mach-omap2/board-cm-t35.c
> +++ b/arch/arm/mach-omap2/board-cm-t35.c
> @@ -26,6 +26,7 @@
>
> #include <linux/i2c/at24.h>
> #include <linux/i2c/twl.h>
> +#include <linux/regulator/fixed.h>
> #include <linux/regulator/machine.h>
> #include <linux/mmc/host.h>
>
> @@ -630,10 +631,18 @@ static inline void cm_t3730_init_mux(void) {}
> static struct omap_board_config_kernel cm_t35_config[] __initdata = {
> };
>
> +static struct regulator_consumer_supply dummy_supplies[] = {
> + REGULATOR_SUPPLY("vddvario", "smsc911x.0"),
> + REGULATOR_SUPPLY("vdd33a", "smsc911x.0"),
> + REGULATOR_SUPPLY("vddvario", "smsc911x.1"),
> + REGULATOR_SUPPLY("vdd33a", "smsc911x.1"),
> +};
> +
> static void __init cm_t3x_common_init(void)
> {
> omap_board_config = cm_t35_config;
> omap_board_config_size = ARRAY_SIZE(cm_t35_config);
> + regulator_register_fixed(0, dummy_supplies, ARRAY_SIZE(dummy_supplies));
> omap3_mux_init(board_mux, OMAP_PACKAGE_CUS);
> omap_serial_init();
> omap_sdrc_init(mt46h32m32lf6_sdrc_params,
--
Regards,
Igor.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-ARM-OMAP3-cm-t35-add-smsc911x-regulators.patch
Type: text/x-patch
Size: 1711 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120327/56f3e669/attachment.bin>
next parent reply other threads:[~2012-03-27 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1332494504-10251-1-git-send-email-Russ.Dill@ti.com>
[not found] ` <1332494504-10251-6-git-send-email-Russ.Dill@ti.com>
2012-03-27 15:53 ` Igor Grinberg [this message]
2012-03-27 17:28 ` [PATCH 05/12] Add dummy smsc911x regulators to cm-t35 Tony Lindgren
2012-03-28 6:33 ` Igor Grinberg
2012-03-28 17:03 ` Tony Lindgren
2012-03-30 15:23 ` Igor Grinberg
2012-04-03 17:26 ` Tony Lindgren
2012-03-27 18:32 ` Russ Dill
2012-03-28 6:34 ` Igor Grinberg
2012-04-03 17:43 ` Tony Lindgren
2012-04-05 7:34 ` Igor Grinberg
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=4F71E290.2050403@compulab.co.il \
--to=grinberg@compulab$(echo .)co.il \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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