[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYgCxf9R1aU2QdPUBxErhK=E2tM=6L-yMLA_L3+ntj3nQ@mail.gmail.com>
Date: Tue, 2 Apr 2013 10:26:12 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Fabio Baltieri <fabio.baltieri@...aro.org>,
Lee Jones <lee.jones@...aro.org>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: Srinidhi Kasagar <srinidhi.kasagar@...ricsson.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: ux500: update V-INTCORE constraints
On Wed, Mar 27, 2013 at 4:21 PM, Fabio Baltieri
<fabio.baltieri@...aro.org> wrote:
> Update V-INTCORE regulator constraints to allow voltage and
> configuration changes from consumer drivers.
>
> Signed-off-by: Fabio Baltieri <fabio.baltieri@...aro.org>
> ---
> Hi Linus,
>
> this patch adds the regulators bits I'm missing for ux500-musb patches.
> Without this I just get a runtime warning like:
>
> V-INTCORE: operation not allowed
>
> but the driver works anyway and there are no build dependencies, so I
> think this can safely go in the arm-soc tree on its own, and the whole
> thing should work happily in -next.
Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
I know that Lee's been sending off a large set of regulator patches
lately, some include alterations to this platform config.
Maybe it's better to take this patch into the regulator tree if these
machine configs will come in that way? Also like Lee to have a
look at this...
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists