From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <4BF2BF0A.8000405@freescale.com> Date: Tue, 18 May 2010 11:23:38 -0500 From: Scott Wood MIME-Version: 1.0 To: Richard Cochran Subject: Re: [PATCH v3 3/3] ptp: Added a clock that uses the eTSEC found on the MPC85xx. References: <4BED8C91.8020107@freescale.com> <20100517082757.GA9703@riccoc20.at.omicron.at> <4BF18582.6000500@freescale.com> <20100518063608.GA2720@riccoc20.at.omicron.at> In-Reply-To: <20100518063608.GA2720@riccoc20.at.omicron.at> Content-Type: text/plain; charset=UTF-8; format=flowed Cc: netdev@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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