All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jon-hunter@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	"DebBarma, Tarun Kanti" <tarun.kanti@ti.com>
Subject: Re: [PATCH 0/9] ARM: OMAP: DMTIMER clean-up in preparation for device-tree
Date: Tue, 22 May 2012 15:33:05 -0500	[thread overview]
Message-ID: <4FBBF801.1010307@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1205171047580.2921@utopia.booyaka.com>

Hi Tony, Paul,

On 05/17/2012 11:48 AM, Paul Walmsley wrote:
> On Thu, 17 May 2012, Jon Hunter wrote:
> 
>> Yes that's right. What is your preference here, the options are ...
>>
>> 1. Move the clkt_clksel.c file to arch/arm/plat-omap and change the
>> omap2_xxx API names to omap_xxx.
>> 2. Add the functions in clkt_clksel.c to arch/arm/plat-omap/clock.c and
>> get rid of clkt_clksel.c altogether.
> 
> #1.

I have posted a new series here [1] to fix omap1 dmtimers and commonise
the code to set dmtimer source clock between omap1 and omap2.

My plan is to rebase this series on top of that, if you are ok with
those changes.

[1] http://marc.info/?l=linux-omap&m=133771799505501&w=2

Cheers
Jon

  reply	other threads:[~2012-05-22 20:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 23:35 [PATCH 0/9] ARM: OMAP: DMTIMER clean-up in preparation for device-tree Jon Hunter
2012-05-16  9:28 ` Cousson, Benoit
2012-05-16 13:34   ` Jon Hunter
2012-05-17 10:29     ` Cousson, Benoit
2012-05-16 20:14   ` Jon Hunter
2012-05-16 23:30     ` Paul Walmsley
2012-05-17 15:56       ` Jon Hunter
2012-05-17 16:48         ` Paul Walmsley
2012-05-22 20:33           ` Jon Hunter [this message]
2012-05-17  5:07     ` DebBarma, Tarun Kanti
2012-05-17 16:00       ` Jon Hunter
2012-06-04 14:11   ` Jon Hunter
2012-05-16 14:37 ` 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=4FBBF801.1010307@ti.com \
    --to=jon-hunter@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --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 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.