linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: a0131647 <sourav.poddar@ti.com>
Cc: balbi@ti.com, linux-omap@vger.kernel.org,
	khilman@deeprootsystems.com, paul@pwsan.com, tony@atomide.com,
	vaibhav.bedia@ti.com, linux@arm.linux.org.uk,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC/RFT PATCH 0/2] SERIAL: OMAP: Remove idle handling from driver
Date: Fri, 15 Feb 2013 19:20:45 +0530	[thread overview]
Message-ID: <511E3D35.4060909@ti.com> (raw)
In-Reply-To: <511E3B3F.1000609@ti.com>

On Friday 15 February 2013 07:12 PM, a0131647 wrote:
> Hi,
> On Friday 15 February 2013 06:38 PM, Felipe Balbi wrote:
>> On Fri, Feb 15, 2013 at 03:07:45PM +0200, Felipe Balbi wrote:
>>> On Fri, Feb 15, 2013 at 06:33:58PM +0530, a0131647 wrote:
>>>> Hi,
>>>> On Friday 15 February 2013 05:36 PM, Santosh Shilimkar wrote:
>>>>> OMAP UART IP needs manual idle modes based on state of the
>>>>> IP. Currently this is handled by the driver with function pointers
>>>>> implemented in platform code.
>>>>>
>>>>> This however breaks in case of device tree because of missing
>>>>> idle handling.
>>>>>
>>>>> The series tries to address the issue
>>>>>
>>>>> Patches has been tested on OMAP4 and OMAP5 devices where the console
>>>>> slugishness was observed without idle mode handling. CPUIDLE and
>>>>> suspend tested ok on these devices.
>>>>>
>>>>> Need help in testing on OMAP2, OMAP3 and AM3XXX devices.
>>>>>
>>>> Tested this series on omap3630 beagle board for:
>>>> 1. Retention in idle and suspend.
>>>> 2. Off mode in idle and suspend.
>>>>
>>>> Tested-by: Sourav Poddar<sourav.poddar@ti.com>
>>> try setting autosuspend_delay to -1
>> Also try DT boot and try to wakeup from echo mem>  /sys/power/state by
>> sending data through UART console.
>>
> Suspend/resume with dt is not functional with the current mainline.
>
With DT, suspend driver itself are not getting registered.
The patch is in Paul's queue [1]

regards,
Santosh

[1] https://patchwork-mail2.kernel.org/patch/2116671/




  reply	other threads:[~2013-02-15 13:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 12:06 [RFC/RFT PATCH 0/2] SERIAL: OMAP: Remove idle handling from driver Santosh Shilimkar
2013-02-15 13:03 ` a0131647
2013-02-15 13:07   ` Felipe Balbi
2013-02-15 13:08     ` Felipe Balbi
2013-02-15 13:42       ` a0131647
2013-02-15 13:50         ` Santosh Shilimkar [this message]
2013-02-18 10:04 ` Santosh Shilimkar
2013-02-18 10:10   ` Felipe Balbi
2013-02-18 10:11     ` Felipe Balbi
2013-02-18 10:25       ` Santosh Shilimkar
2013-02-18 10:42         ` Felipe Balbi
2013-02-18 10:45           ` Felipe Balbi
2013-02-18 10:55             ` Santosh Shilimkar
2013-02-18 11:13               ` Felipe Balbi
2013-02-18 14:36                 ` Santosh Shilimkar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=511E3D35.4060909@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=balbi@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paul@pwsan.com \
    --cc=sourav.poddar@ti.com \
    --cc=tony@atomide.com \
    --cc=vaibhav.bedia@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).