* Grygorii Strashko <grygorii.strashko@xxxxxx> [160621 05:21]: > On 06/21/2016 02:56 PM, Tony Lindgren wrote: > > So are these safe to apply in whatever order? > > > > Patch 1 should go first. > > but do you agree with comment I've added in patch 1: > >>> > > RFC: because it will break DT ABI, mdio will not work on devices with > old DTs and new kernel which still do have [ti,hwmods = "davinci_mdio"] > property defined in DT: > platform 48485000.mdio: Cannot lookup hwmod 'davinci_mdio' > davinci_mdio 48485000.mdio: _od_fail_runtime_resume: FIXME: missing > hwmod/omap_dev info > davinci_mdio: probe of 48485000.mdio failed with error -5 Well the ti,hwmods entry we can keep and remove later. How about parse it manually in the driver and just print a warning if no clocks are found and ti,hwmods is set? I think that's the best we can do here. With the warning people know at least what to do. Regards, Tony -- 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
