From: "Cousson, Benoit" <b-cousson@ti.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"Hilman, Kevin" <khilman@ti.com>, Paul Walmsley <paul@pwsan.com>,
Russell King <rmk@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: omap clocksource timer selection: dmtimer OR 32K-Sync timer
Date: Fri, 13 Jan 2012 17:09:21 +0100 [thread overview]
Message-ID: <4F105731.8010008@ti.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A8317A52F0@DBDE01.ent.ti.com>
On 1/13/2012 4:52 PM, Hiremath, Vaibhav wrote:
> On Fri, Jan 13, 2012 at 20:49:35, Cousson, Benoit wrote:
[...]
>> A series was sent to do that by Felipe last year, but we somehow forgot
>> to rebase it on newer kernel and thus never reposted it.
>
> If you are ok, I can help you here.
Thanks it will be cool if you can fix that series.
> Can you please point me to git repo for
> the same.
>
> And also, this is important for AM33xx support in mainline.
Here is the link to the original series.
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg37403.html
The hwmod format changed a lot since them, so it should be refreshed.
Regards,
Benoit
WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: omap clocksource timer selection: dmtimer OR 32K-Sync timer
Date: Fri, 13 Jan 2012 17:09:21 +0100 [thread overview]
Message-ID: <4F105731.8010008@ti.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A8317A52F0@DBDE01.ent.ti.com>
On 1/13/2012 4:52 PM, Hiremath, Vaibhav wrote:
> On Fri, Jan 13, 2012 at 20:49:35, Cousson, Benoit wrote:
[...]
>> A series was sent to do that by Felipe last year, but we somehow forgot
>> to rebase it on newer kernel and thus never reposted it.
>
> If you are ok, I can help you here.
Thanks it will be cool if you can fix that series.
> Can you please point me to git repo for
> the same.
>
> And also, this is important for AM33xx support in mainline.
Here is the link to the original series.
http://www.mail-archive.com/linux-omap at vger.kernel.org/msg37403.html
The hwmod format changed a lot since them, so it should be refreshed.
Regards,
Benoit
next prev parent reply other threads:[~2012-01-13 16:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 12:21 omap clocksource timer selection: dmtimer OR 32K-Sync timer Hiremath, Vaibhav
2012-01-13 12:21 ` Hiremath, Vaibhav
2012-01-13 12:49 ` Shilimkar, Santosh
2012-01-13 12:49 ` Shilimkar, Santosh
2012-01-13 13:42 ` Hiremath, Vaibhav
2012-01-13 13:42 ` Hiremath, Vaibhav
2012-01-13 14:41 ` Shilimkar, Santosh
2012-01-13 14:41 ` Shilimkar, Santosh
2012-01-13 14:57 ` Hiremath, Vaibhav
2012-01-13 14:57 ` Hiremath, Vaibhav
2012-01-13 16:50 ` Tony Lindgren
2012-01-13 16:50 ` Tony Lindgren
2012-01-16 9:16 ` Hiremath, Vaibhav
2012-01-16 9:16 ` Hiremath, Vaibhav
2012-01-13 15:19 ` Cousson, Benoit
2012-01-13 15:19 ` Cousson, Benoit
2012-01-13 15:52 ` Hiremath, Vaibhav
2012-01-13 15:52 ` Hiremath, Vaibhav
2012-01-13 16:09 ` Cousson, Benoit [this message]
2012-01-13 16:09 ` Cousson, Benoit
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=4F105731.8010008@ti.com \
--to=b-cousson@ti.com \
--cc=hvaibhav@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rmk@arm.linux.org.uk \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.