[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <523FEFCD.70409@skitlab.ru>
Date: Mon, 23 Sep 2013 11:37:49 +0400
From: Aida Mynzhasova <aida.mynzhasova@...tlab.ru>
To: linuxppc-dev@...ts.ozlabs.org
CC: netdev@...r.kernel.org, devicetree@...r.kernel.org,
Richard Cochran <richardcochran@...il.com>,
Claudiu Manoil <claudiu.manoil@...escale.com>
Subject: Device tree node for Freescale Gianfar PTP reference clock source
selection
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@...00 {
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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists