From: Aida Mynzhasova <aida.mynzhasova@skitlab.ru>
To: Richard Cochran <richardcochran@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] powerpc/83xx: gianfar_ptp: select 1588 clock source through dts file
Date: Wed, 18 Sep 2013 20:40:25 +0400 [thread overview]
Message-ID: <5239D779.7070504@skitlab.ru> (raw)
In-Reply-To: <20130918160846.GA4397@netboy>
On 18.09.2013 20:08, Richard Cochran wrote:
> On Wed, Sep 18, 2013 at 05:21:04PM +0400, Aida Mynzhasova wrote:
>> IEEE 1588 timer reference clock source is determined through hard-coded
>> value in gianfar_ptp driver by default. This patch allows to select ptp
>> clock source by means of device tree file node.
>>
>> For instance:
>>
>> fsl,cksel = <0>;
>>
>> for using external (TSEC_TMR_CLK input) high precision timer
>> reference clock.
>>
>> Other acceptable values:
>>
>> <1> : eTSEC system clock
>> <2> : eTSEC1 transmit clock
>> <3> : RTC clock input
>
> Do the other clock sources even work at all?
>
> We were not able to get them working.
>
> Thanks,
> Richard
>
Hi Richard,
I've tried to use 2 clock sources: external from TSEC_TMR_CLK input (for
this I had to update multiplexer settings in uboot) and eTSEC system
clock - counter worked fine with both.
My attempts to use eTSEC1 transmit clock and RTC clock were unsuccessful
(the system hanged up) irrespective of using hard-coded value or entry
in dts file.
Thanks.
next prev parent reply other threads:[~2013-09-18 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 13:21 [PATCH] powerpc/83xx: gianfar_ptp: select 1588 clock source through dts file Aida Mynzhasova
2013-09-18 15:44 ` Claudiu Manoil
2013-09-18 16:39 ` Aida Mynzhasova
2013-09-19 16:30 ` Claudiu Manoil
2013-09-19 17:12 ` Richard Cochran
2013-09-18 16:08 ` Richard Cochran
2013-09-18 16:40 ` Aida Mynzhasova [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-24 7:39 Aida Mynzhasova
2013-09-24 17:14 ` Richard Cochran
2013-09-24 17:14 ` Richard Cochran
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=5239D779.7070504@skitlab.ru \
--to=aida.mynzhasova@skitlab.ru \
--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.