public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: Move designware timer OF glue into drivers/clocksource
Date: Tue, 10 Jul 2012 16:10:31 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1207101609270.32033@ionos> (raw)
In-Reply-To: <20120710111324.GA8701@elf.ucw.cz>

On Tue, 10 Jul 2012, Pavel Machek wrote:

> Hi!
> 
> On Tue 2012-07-10 13:07:36, Thomas Gleixner wrote:
> > On Tue, 10 Jul 2012, Pavel Machek wrote:
> > >  		timer0: timer at ffc08000 {
> > > -				compatible = "socfpga,sp-timer";
> > > +				compatible = "snps,dw-apb-timer-sp";
> > 
> > apb timer. That rings a bell. Does that have anything to do with
> > 
> > arch/x86/kernel/apb_timer.c ? That's from one of the intel mobile
> > chips and might be the very same IP block.
> 
> As far as I can tell, drivers/clocksource/dw_apb_timer.c is already
> used on Intel MID platform... What I'm moving is device tree glue,
> that is unsuitable for x86 plaforms with classical BIOS. (And AFAICT,
> intel MID also uses something different).

Ah, ok. Did not look at the details. Just the "abp" popped up in my
mind :)
 
> > > -obj-y					:= common.o time.o
> > > +obj-y					:= common.o ../../../drivers/clocksource/dw_apb_timer_of.o
> > 
> > Urgh! Why can't we just compile it from drivers/clocksource/Makefile
> > ?
> 
> It will cost me a new config option, but I can do that, yes.

Please.

Thanks,

	tglx

  reply	other threads:[~2012-07-10 14:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10  9:42 Move designware timer OF glue into drivers/clocksource Pavel Machek
2012-07-10 11:07 ` Thomas Gleixner
2012-07-10 11:13   ` Pavel Machek
2012-07-10 14:10     ` Thomas Gleixner [this message]
2012-07-10 11:23   ` Pavel Machek
2012-07-10 11:24 ` Jamie Iles
2012-07-10 12:19   ` Pavel Machek
2012-07-10 13:41     ` Arnd Bergmann
2012-07-10 18:08       ` Pavel Machek
2012-07-10 12:20 ` Thomas Petazzoni
2012-07-10 18:11   ` Pavel Machek

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=alpine.LFD.2.02.1207101609270.32033@ionos \
    --to=tglx@linutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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