On Fri, May 6, 2011 at 9:25 PM, Kevin Hilman wrote:
> Govindraj writes:
>
>> On Thu, May 5, 2011 at 8:28 PM, Kevin Hilman wrote:
>>> Govindraj writes:
>>>
>>> [...]
>>>
>
> ... this is just putting back basically the same thing that was removed in
> patch 1. IOW, this is now being
Govindraj writes:
> On Thu, May 5, 2011 at 8:28 PM, Kevin Hilman wrote:
>> Govindraj writes:
>>
>> [...]
>>
... this is just putting back basically the same thing that was removed in
patch 1. IOW, this is now being checked for *every* PRCM wakeup, which
is no different than
On Thu, May 5, 2011 at 8:28 PM, Kevin Hilman wrote:
> Govindraj writes:
>
> [...]
>
>>>
>>> ... this is just putting back basically the same thing that was removed in
>>> patch 1. IOW, this is now being checked for *every* PRCM wakeup, which
>>> is no different than having it in the idle path.
>
Govindraj writes:
[...]
>>
>> ... this is just putting back basically the same thing that was removed in
>> patch 1. IOW, this is now being checked for *every* PRCM wakeup, which
>> is no different than having it in the idle path.
>>
>> I thought I understood that you had the SW IRQ triggering
On Thu, May 5, 2011 at 5:41 AM, Kevin Hilman wrote:
> "Govindraj.R" writes:
>
>> Use resume idle call from prcm_irq to enable uart_port from low power states.
>> Add api to check pad wakeup status which will we used from uart_resume func.
>> to enable back uart port if a wakeup event occurred.
>>
"Govindraj.R" writes:
> Use resume idle call from prcm_irq to enable uart_port from low power states.
> Add api to check pad wakeup status which will we used from uart_resume func.
> to enable back uart port if a wakeup event occurred.
>
> UART_Resume func. can be removed once we have irq_chainin
Use resume idle call from prcm_irq to enable uart_port from low power states.
Add api to check pad wakeup status which will we used from uart_resume func.
to enable back uart port if a wakeup event occurred.
UART_Resume func. can be removed once we have irq_chaining functionality
available.
Signe
