Re: [PATCH V2 0/3] ARM: dts: omap5-uevm: fixup wrong regulator configuration

[Nishanth Menon]

On Tue, Jul 30, 2013 at 1:52 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote:
> * Benoit Cousson <benoit.cousson@xxxxxxxxx> [130729 15:24]:
>> On 29/07/2013 19:03, Nishanth Menon wrote:
>> > Due to wrong older revision of documentation used as reference, we
>> > seem to have a bunch of LDOs wrongly configured on OMAP5 uEVM. This
>> > series is based power tree on production board 750-2628-XXX platform.
>> > Unfortunately, the wrong voltages may be detrimental to OMAP5 as they
>> > supply hardware blocks at voltages that are out of specification.
>> >
>> > Also available at:
>> > based on v3.11-rc1 tag
>> > http link: https://github.com/nmenon/linux-2.6-playground/commits/push/omap5-palmas-fixes-v2
>> > git link: git://github.com/nmenon/linux-2.6-playground.git
>> > branch: push/omap5-palmas-fixes-v2
>> >
>> > Changes since V1:
>> >  - squash of patches
>> >  - picked up Ack from Keerthy
>> >  - based on v3.11-rc3 tag
>> >
>> > V1: http://marc.info/?t=137407980100008&r=1&w=2
>> >
>> > Nishanth Menon (3):
>> >   ARM: dts: omap5-uevm: document regulator signals used on the actual
>> >     board
>> >   ARM: dts: omap5-uevm: fix regulator configurations mandatory for SoC
>> >   ARM: dts: omap5-uevm: update optional/unused regulator configurations
>> >
>> >  arch/arm/boot/dts/omap5-uevm.dts |   78 ++++++++++++++++++++++++--------------
>> >  1 file changed, 49 insertions(+), 29 deletions(-)
>> >
>> > Regards,
>> > Nishanth Menon
>>
>> For the whole series:
>>
>> Acked-by: Benoit Cousson <benoit.cousson@xxxxxxxxx>
>
> Thanks, I've applied these into omap-for-v3.11/fixes-omap5
> and will send a pull request for these today as these seem
> quite urgent fixes.
yes they are. thanks for picking these up and the reviews.

Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/