Hi, Nice to see this moving along :) * Tero Kristo <t-kristo@xxxxxx> [160411 01:20]: > > The ordering on this set is kind of tricky to avoid any boot issues, > and it still currently causes a boot breakage between the DTS data > introduction and removal of hwmod data; this generates duplicate > entries for clocks which is prone to cause issues (both DT and hwmod > have the same entries in place under the hwmod data is removed.) I > didn't quite figure out a good way to avoid this, and could use some > guidance here. Shall we squash the DT + hwmod data patches together? > This avoids the boot breakage but creates pretty large patches. Also, > AMx3xx data needs to be grouped together as part of their data is > re-used commonly by both SoCs. How about use clocks from dts if clocks property is defined? Otherwise fall back to the old static data. Then drop the static data later on with follow up patches. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
