* H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> [190907 06:57]: > For the ti-cpufreq driver we need a clear separation between omap34 and omap36 families > since they have different silicon revisions and efuses. > > So far ti,omap3630/ti,omap36xx is just an additional flag to ti,omap3 while omap34 has no > required entry. > > Therefore we can not match omap34 boards properly. > > This needs to add ti,omap3430 and ti,omap3630 where it is missing. > > We also clean up some instances of missing ti,am3517 so that we can rely on > seeing either one of: > > ti,am3517 > ti,omap3430 > ti,omap3630 > > in addition to ti,omap3. > > We leave ti,omap34xx and ti,omap36xx untouched for compatibility. Thanks for doing this: Acked-by: Tony Lindgren <tony@xxxxxxxxxxx>
