On 16:49-20130619, Tero Kristo wrote: > On 06/19/2013 04:30 PM, Nishanth Menon wrote: > >On 16:19-20130619, Tero Kristo wrote: > >[...] > >>+ > >>+/* > >>+ * 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...? How about this: we do have 443x.dtsi and 4460.dtsi -> add the corresponding clock nodes there? ideally, driver should just do devm_clk_get and should not worry about what SoC revision it is running on. -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
