Devicetree
 help / color / mirror / Atom feed
From: Michal Simek <monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
To: grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org
Cc: michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org
Subject: [PATCH 0/1] How to choose system timer?
Date: Thu, 10 Nov 2011 14:10:21 +0100	[thread overview]
Message-ID: <1320930623-15060-1-git-send-email-monstr@monstr.eu> (raw)

Hi,

I have one design question about specifying system timer in DTS.
Our proposed solution is to specify system-timer in chosen
node and then Linux kernel probe it.

For example:
	chosen {
		bootargs = " console=ttyS0,115200 ";
		linux,stdout-path = "/plb@0/serial@83e00000";
		system-timer = <&xps_timer_0>;
	} ;

Is it correct solution? We would like to use 
standard solution and not to reinvent the wheel.
How others archs handle it? AFAIK you have internal cpu
timer which is used as system timer.

I have also attached the patch for microblaze.

Thanks,
Michal



*** BLURB HERE ***

Peter A. G. Crosthwaite (1):
  microblaze: Added fdt chosen capability for timer

 arch/microblaze/kernel/timer.c |   12 ++++++++----
 1 files changed, 8 insertions(+), 4 deletions(-)

-- 
1.7.5.4

             reply	other threads:[~2011-11-10 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-10 13:10 Michal Simek [this message]
     [not found] ` <1320930623-15060-1-git-send-email-monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2011-11-10 13:10   ` [PATCH 0/1] How to choose system timer? Michal Simek
     [not found]     ` <1320930623-15060-2-git-send-email-monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2011-11-10 13:10       ` [PATCH 1/1] microblaze: Added fdt chosen capability for timer Michal Simek
     [not found]         ` <1320930623-15060-3-git-send-email-monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2011-11-10 14:21           ` John Williams

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=1320930623-15060-1-git-send-email-monstr@monstr.eu \
    --to=monstr-psz03upnqpehxe+lvdladg@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
    --cc=john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
    --cc=michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.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