From: Aida Mynzhasova <aida.mynzhasova@skitlab.ru>
To: linuxppc-dev@lists.ozlabs.org
Cc: netdev@vger.kernel.org,
Richard Cochran <richardcochran@gmail.com>,
Claudiu Manoil <claudiu.manoil@freescale.com>,
devicetree@vger.kernel.org
Subject: Device tree node for Freescale Gianfar PTP reference clock source selection
Date: Mon, 23 Sep 2013 11:37:49 +0400 [thread overview]
Message-ID: <523FEFCD.70409@skitlab.ru> (raw)
Hi,
Currently, Freescale Gianfar PTP reference clock source is determined
through hard-coded value in gianfar_ptp driver. I don't think that
recompilation of the entire module (or even worse - the kernel) is a god
idea when we want to change one clock source to another. So, I want to
add new device tree binding, which can be used as:
ptp_clock@24E00 {
compatible = "fsl,etsec-ptp";
reg = <0x24E00 0xB0>;
interrupts = <12 0x8 13 0x8>;
interrupt-parent = < &ipic >;
fsl,cksel = <0>; /* <-- New entry */
fsl,tclk-period = <10>;
fsl,tmr-prsc = <100>;
fsl,tmr-add = <0x999999A4>;
fsl,tmr-fiper1 = <0x3B9AC9F6>;
fsl,tmr-fiper2 = <0x00018696>;
fsl,max-adj = <659999998>;
};
fsl,cksel acceptable values:
<0> for external clock;
<1> for eTSEC system clock;
<2> for eTSEC1 transmit clock;
<3> for RTC clock input.
I am new in this mailing list, and as far as I know, I have to discuss
all updates for device tree files here before sending patch, which uses
new attributes.
Also, should I define new bindings in some special way? I want to add
description of cksel attribute in
/Documentation/devicetree/bindings/net/fsl-tsec-phy.txt. Is it enough or
not?
Thanks!
--
Regards,
Aida
next reply other threads:[~2013-09-23 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 7:37 Aida Mynzhasova [this message]
2013-09-26 1:30 ` Device tree node for Freescale Gianfar PTP reference clock source selection Scott Wood
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=523FEFCD.70409@skitlab.ru \
--to=aida.mynzhasova@skitlab.ru \
--cc=claudiu.manoil@freescale.com \
--cc=devicetree@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).