From: Kevin Hilman <khilman@ti.com>
To: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>
Cc: "Tero.Kristo@nokia.com" <Tero.Kristo@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] omap: dmtimer: Enable autoidle
Date: Tue, 15 Feb 2011 08:14:17 -0800 [thread overview]
Message-ID: <87ipwluvfq.fsf@ti.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03745CA5D1@dbde02.ent.ti.com> (Tarun Kanti DebBarma's message of "Tue, 15 Feb 2011 18:11:16 +0530")
"DebBarma, Tarun Kanti" <tarun.kanti@ti.com> writes:
> [...]
>> >> >> >
>> >> >> > Should this be changed to apply only on that one? I don't know
>> >about
>> >> >> > OMAP4, but I think this should work on OMAP2 at least based on
>> >spec.
>> >> >> It works on OMAP2 and OMAP4.
>> >> >Ok, on OMAP4 I should have clarified further.
>> >> >AUTOIDLE is present only for millisecond timers: 1,2,10.
>> >> >The reset of the timers do not have this bit.
>> >>
>> >> Does it matter if the bit is set on the timers that don't have it or
>> >does
>> >> the HW just ignore it? Or should we enumerate the timers that support
>> >it
>> >> on omap4?
>> >For other timers it happens to be SOFTRESET bit. So HW would not ignore.
>>
>> Ok, so this one should only be implemented for omap2/3 or added logic is
>> needed for omap4.
> YES.
>
Tarun is autoidle feature handled in your hwmod conversion series?
If not, this should be implemented as a patch on top of your series
since we will know which timers have this capability.
Kevin
prev parent reply other threads:[~2011-02-15 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 17:26 [PATCH] omap: dmtimer: Enable autoidle Tero Kristo
2011-02-14 23:28 ` Kevin Hilman
2011-02-15 8:16 ` Tero.Kristo
2011-02-15 9:20 ` DebBarma, Tarun Kanti
2011-02-15 9:31 ` DebBarma, Tarun Kanti
2011-02-15 9:45 ` Tero.Kristo
2011-02-15 9:51 ` DebBarma, Tarun Kanti
2011-02-15 12:29 ` Tero.Kristo
2011-02-15 12:41 ` DebBarma, Tarun Kanti
2011-02-15 16:14 ` Kevin Hilman [this message]
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=87ipwluvfq.fsf@ti.com \
--to=khilman@ti.com \
--cc=Tero.Kristo@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=tarun.kanti@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