public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Tony Lindgren <tony@atomide.com>, Benoit Cousson <b-cousson@ti.com>
Cc: linux-omap@vger.kernel.org, Kevin Hilman <khilman@ti.com>,
	Tarun Kanti DebBarma <tarun.kanti@ti.com>
Subject: RE: [PATCH v10 00/11] dmtimer adaptation to platform_driver
Date: Fri, 18 Feb 2011 11:16:29 +0530	[thread overview]
Message-ID: <106a7a107bdd8b83317510d139620757@mail.gmail.com> (raw)
In-Reply-To: <20110218005706.GR20795@atomide.com>

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Tony Lindgren
> Sent: Friday, February 18, 2011 6:27 AM
> To: Tarun Kanti DebBarma
> Cc: linux-omap@vger.kernel.org; khilman@ti.com
> Subject: Re: [PATCH v10 00/11] dmtimer adaptation to platform_driver
>
> Hi,
>
> * Tarun Kanti DebBarma <tarun.kanti@ti.com> [110216 04:56]:
> > dmtimer adaptation to platform_driver.
> >
> > This patch series is adaptation of dmtimer code to platform driver
> > using omap_device and omap_hwmod abstraction.
>
> Looks like this needs rebasing on top of current omap-for-linus
> because of the omap4 hwmod data being merged.
>
> Also note that you may need to change things with the clock
> init with init_early changes.
>
> That's something we need to consider carefully as we don't
> necessarily want to have the system timer depend on hwmod
> and clock framework. But that can be fixed later on after
> your patch series.
>
This is interesting. Major work of the timer series was around
making this early timer work with hwmod. We had such a
discussion earlier, to leave OS tick timer from hwmod because
of various implications.

Regards,
Santosh

      parent reply	other threads:[~2011-02-18  5:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 13:00 [PATCH v10 00/11] dmtimer adaptation to platform_driver Tarun Kanti DebBarma
2011-02-16 13:00 ` [PATCH v10 01/11] OMAP2+: dmtimer: add device names to flck nodes Tarun Kanti DebBarma
2011-02-16 13:00 ` [PATCH v10 02/11] OMAP2420: hwmod data: add dmtimer Tarun Kanti DebBarma
2011-02-16 13:00 ` [PATCH v10 03/11] OMAP2430: " Tarun Kanti DebBarma
2011-02-16 13:00 ` [PATCH v10 04/11] OMAP3: " Tarun Kanti DebBarma
2011-02-16 13:00 ` [PATCH v10 05/11] OMAP4: " Tarun Kanti DebBarma
2011-02-16 13:00 ` [PATCH v10 06/11] OMAP1: dmtimer: conversion to platform devices Tarun Kanti DebBarma
2011-02-16 13:00 ` [PATCH v10 07/11] OMAP2+: dmtimer: convert " Tarun Kanti DebBarma
2011-02-16 13:00 ` [PATCH v10 08/11] OMAP: dmtimer: platform driver Tarun Kanti DebBarma
2011-02-16 13:00 ` [PATCH v10 09/11] OMAP: dmtimer: switch-over to platform device driver Tarun Kanti DebBarma
2011-02-16 13:00 ` [PATCH v10 10/11] OMAP: dmtimer: pm_runtime support Tarun Kanti DebBarma
2011-02-16 13:00 ` [PATCH v10 11/11] OMAP: dmtimer: add timeout to low-level routines Tarun Kanti DebBarma
2011-02-18  0:57 ` [PATCH v10 00/11] dmtimer adaptation to platform_driver Tony Lindgren
2011-02-18  5:37   ` DebBarma, Tarun Kanti
2011-02-18  5:46   ` Santosh Shilimkar [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=106a7a107bdd8b83317510d139620757@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=b-cousson@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tarun.kanti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox