Hi Sören,
On Tue, 2013-03-05 at 12:04 -0800, Sören Brinkmann wrote:
> For this reasons, I'd like to propose moving Zynq into the same
> direction. I.e. adding a clock controller with the following DT
> description (details may change but the general idea should become
> clear):
> clkc: clkc {
> #clock-cells = <1>;
> compatible = "xlnx,ps7-clkc";
> ps_clk_frequency = <33333333>; # board x-tal
> # optional props
> gem0_emio_clk_freq = <125000000>;
> gem1_emio_clk_freq = <50000000>;
> can_mio_clk_freq_xx = <1234>; # this is possible 54 times
> with xx = 00..53
> };
The clock controller should only contain properties for input frequency
(which can obviously not be calculated at run-time).
Are the gem*, can* properties inputs? If they are actually outputs, the
corresponding frequencies should be requested by the clock consumers and
not hard-coded in DT.
Please keep in mind that DT properties use dashes instead of
underscores.
Best regards,
Jan
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
