On Tue, Oct 11, 2011 at 4:00 AM, Kevin Hilman wrote:
> "Govindraj.R" writes:
>
>> Currently we use a shared irq handler to identify uart activity and then
>> trigger a timer.
>
> OK.
>
>> Based the timeout value set from sysfs the timer used to expire.
>
> Please re-phrase as I'm not sure what is
"Govindraj.R" writes:
> Currently we use a shared irq handler to identify uart activity and then
> trigger a timer.
OK.
> Based the timeout value set from sysfs the timer used to expire.
Please re-phrase as I'm not sure what is being said here.
> If no uart-activity was detected timer-expiry
Currently we use a shared irq handler to identify uart activity and then
trigger a timer. Based the timeout value set from sysfs the timer used to
expire. If no uart-activity was detected timer-expiry func sets can_sleep
flag. Based on this we will disable the uart clocks in idle path.
Since the c