From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2.6.33] SMDK6410: Specify no GPIO for B_PWR_5V regulator
Date: Thu, 14 Jan 2010 00:41:04 +0000 [thread overview]
Message-ID: <20100114004104.GN18532@trinity.fluff.org> (raw)
In-Reply-To: <1263391024-29502-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Wed, Jan 13, 2010 at 01:57:04PM +0000, Mark Brown wrote:
> Since the fixed voltage regulator grew support for GPIO based
> enables and GPIO 0 is valid on some systems we need to specify
> that there is no valid GPIO enable control.
should this be posted for -rc?
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>
> Sorry, resend due to thinkoed list address.
>
> arch/arm/mach-s3c6410/mach-smdk6410.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-s3c6410/mach-smdk6410.c b/arch/arm/mach-s3c6410/mach-smdk6410.c
> index 8eb8d2c..bc3b1fd 100644
> --- a/arch/arm/mach-s3c6410/mach-smdk6410.c
> +++ b/arch/arm/mach-s3c6410/mach-smdk6410.c
> @@ -211,6 +211,7 @@ static struct fixed_voltage_config smdk6410_b_pwr_5v_pdata = {
> .supply_name = "B_PWR_5V",
> .microvolts = 5000000,
> .init_data = &smdk6410_b_pwr_5v_data,
> + .gpio = -EINVAL,
> };
>
> static struct platform_device smdk6410_b_pwr_5v = {
> --
> 1.6.6
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-01-14 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 13:57 [PATCH 2.6.33] SMDK6410: Specify no GPIO for B_PWR_5V regulator Mark Brown
2010-01-14 0:41 ` Ben Dooks [this message]
2010-01-14 9:53 ` Mark Brown
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=20100114004104.GN18532@trinity.fluff.org \
--to=ben-linux@fluff.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).