From: Scott Wood <scottwood@freescale.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: netdev@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 3/3] ptp: Added a clock that uses the eTSEC found on the MPC85xx.
Date: Tue, 18 May 2010 11:23:38 -0500 [thread overview]
Message-ID: <4BF2BF0A.8000405@freescale.com> (raw)
In-Reply-To: <20100518063608.GA2720@riccoc20.at.omicron.at>
On 05/18/2010 01:36 AM, Richard Cochran wrote:
> 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.
OK, but that's a separate issue from whether it exists on the chip and
could be used on a different board.
> Also, according to the documentation, it has no bit in the TMR_CTRL or the
> TMR_TEMASK registers.
It does seem inconsistent -- but could just be bad docs.
> 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?
I'll ask around.
-Scott
next prev parent reply other threads:[~2010-05-18 16:23 UTC|newest]
Thread overview: 19+ 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:44 ` 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-14 16:45 ` Richard Cochran
2010-05-17 15:41 ` Wolfgang Grandegger
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 ` 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 16:46 ` Richard Cochran
2010-05-14 17:46 ` Scott Wood
2010-05-17 8:27 ` Richard Cochran
2010-05-17 8:27 ` Richard Cochran
2010-05-17 18:05 ` Scott Wood
2010-05-18 6:36 ` Richard Cochran
2010-05-18 6:36 ` Richard Cochran
2010-05-18 16:23 ` Scott Wood [this message]
2010-05-17 15:41 ` Wolfgang Grandegger
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=4BF2BF0A.8000405@freescale.com \
--to=scottwood@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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.