Kevin Hilman wrote:
Mike Turquette writes:
Lesly AM wrote:
[...]
From: "Mike Rapoport"
[...]
Is it necessary to initialize the remap sleep twice?
No.
Sorry.. I didn't notice that Amit has already pushed this.
The existing remap programming does have a bug in it. Lesly, try
adding
Mike Turquette writes:
> Lesly AM wrote:
[...]
>> From: "Mike Rapoport"
[...]
>>>
>>> Is it necessary to initialize the remap sleep twice?
>>>
>>
>> No.
>> Sorry.. I didn't notice that Amit has already pushed this.
>
> The existing remap programming does have a bug in it. Lesly, try
> addi
Lesly AM wrote:
- Original Message -
From: "Mike Rapoport"
To:
Cc: ; "Nishanth Menon" ; "David
Derrick" ; "Samuel Ortiz"
Sent: Wednesday, January 20, 2010 8:58 PM
Subject: Re: [PATCH v2 1/6] omap3: pm: re-program the sleep state of TRITON
r
x0080...@ti.com writes:
> From: Lesly A M
>
> omap3: pm: re-program the sleep state of TRITON resources by modifying the
> REMAP register
This line duplicates subject, and is duplicated when applying to git.
This causes maintainers to have t manually edit the changelog to
remove the duplicate l
- Original Message -
From: "Mike Rapoport"
To:
Cc: ; "Nishanth Menon" ; "David
Derrick" ; "Samuel Ortiz"
Sent: Wednesday, January 20, 2010 8:58 PM
Subject: Re: [PATCH v2 1/6] omap3: pm: re-program the sleep state of TRITON
resources b
x0080...@ti.com wrote:
> From: Lesly A M
>
> omap3: pm: re-program the sleep state of TRITON resources by modifying the
> REMAP register
>
> Removed the warning print with checking order of scripts, since the order
> is not important. Only the values configured in the register, which is
> poin
From: Lesly A M
omap3: pm: re-program the sleep state of TRITON resources by modifying the
REMAP register
Removed the warning print with checking order of scripts, since the order
is not important. Only the values configured in the register, which is pointing
to
the starting address of each se
