Devicetree
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH v3 3/3] ptp: Added a clock that uses the eTSEC found on the MPC85xx.
Date: Tue, 18 May 2010 08:36:08 +0200	[thread overview]
Message-ID: <20100518063608.GA2720@riccoc20.at.omicron.at> (raw)
In-Reply-To: <4BF18582.6000500-KZfg59tc24xl57MIdRCFDg@public.gmane.org>

On Mon, May 17, 2010 at 01:05:54PM -0500, Scott Wood wrote:
> >>> >+  - tmr_fiper1   Fixed interval period pulse generator.
> >>> >+  - tmr_fiper2   Fixed interval period pulse generator.
> >>
> 
> MPC8572 and P2020 have fiper3 as well.

I doubt they really have a third fiper.

First of all, this signal is not routed anywhere on the boards. Also,
according to the documentation, it has no bit in the TMR_CTRL or the
TMR_TEMASK registers. Unless there is a bit in TMR_TEMASK, you cannot
get an interrupt from it.

If you cannot use the signal externally (in the "real" world) and you
cannot get an interrupt, what good is it to have such a periodic
signal? Polling the bit in the TMR_TEVENT to see when a pulse occurs
seems pointless.

Scott, you have connections, right? Can you clarify this for me?

Thanks,

Richard

  parent reply	other threads:[~2010-05-18  6:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14 16:44 [PATCH v3 0/3] ptp: IEEE 1588 clock support Richard Cochran
2010-05-14 16:45 ` [PATCH v3 1/3] ptp: Added a brand new class driver for ptp clocks Richard Cochran
2010-05-17 15:41   ` Wolfgang Grandegger
2010-05-14 16:46 ` [PATCH v3 2/3] ptp: Added a clock that uses the Linux system time Richard Cochran
2010-05-14 16:46 ` [PATCH v3 3/3] ptp: Added a clock that uses the eTSEC found on the MPC85xx Richard Cochran
2010-05-14 17:46   ` Scott Wood
     [not found]     ` <4BED8C91.8020107-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2010-05-17  8:27       ` Richard Cochran
2010-05-17 18:05         ` Scott Wood
     [not found]           ` <4BF18582.6000500-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2010-05-18  6:36             ` Richard Cochran [this message]
2010-05-18 16:23               ` Scott Wood
2010-05-17 15:41   ` Wolfgang Grandegger

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=20100518063608.GA2720@riccoc20.at.omicron.at \
    --to=richardcochran-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=scottwood-KZfg59tc24xl57MIdRCFDg@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