On 06/19/2013 04:30 PM, Nishanth Menon wrote:
On 16:19-20130619, Tero Kristo wrote:
<snip>
diff --git a/arch/arm/boot/dts/omap4-clocks.dtsi
b/arch/arm/boot/dts/omap4-clocks.dtsi
new file mode 100644
index 0000000..b420d8a
--- /dev/null
+++ b/arch/arm/boot/dts/omap4-clocks.dtsi
[...]
+/* XXX Missing round_rate, set_rate in ops */
could be dropped?
+dpll_core_m3x2_div_ck: dpll_core_m3x2_div_ck@4a004134 {
+ compatible = "divider-clock";
+ clocks = <&dpll_core_x2_ck>;
+ #clock-cells = <0>;
+ reg = <0x4a004134 0x4>;
+ bit-mask = <0x1f>;
+ index-starts-at-one;
+};
[..]
+
+/* XXX Missing round_rate, set_rate in ops */
could be dropped?
Yeah, I blame my bugged script here. :)
+dpll_per_m3x2_div_ck: dpll_per_m3x2_div_ck@4a008154 {
+ compatible = "divider-clock";
+ clocks = <&dpll_per_x2_ck>;
+ #clock-cells = <0>;
+ reg = <0x4a008154 0x4>;
+ bit-mask = <0x1f>;
+ index-starts-at-one;
+};
+
[...]
+
+/*
+ * clocks specific to omap4460
+ */
+/*
+ * clocks specific to omap4430
+ */
+/*
+ * clocks common to omap44xx
+ */
could be dropped?
Same.
btw, are we differentiating 4430 and 4460?A
Example:
bandgap_fclk in 4430
Vs
div_ts_ck, bandgap_ts_fclk in 4460?
Both nodes are available for both SoCs as of now. Driver should
differentiate which clock node to use though. Added Eduardo for
commenting this part, maybe we should add a couple of entries to the
list in cclock44xx_data.c...?
-Tero
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
