On 09-07-15, 09:55, Pi-Cheng Chen wrote: > That's what I did in previous version. But the reason I use the device- > driver model is to handle the defer probing issue. Since there's no > arch/arm64/mach-mediatek/ directory to hold the device registration > code anymore, no device tree way to match cpufreq driver > (please correct me if there's any), and initcall seems not handle > defer probing either, therefore I put both device and driver > registration in this function. I know it's crappy. :( > Do you have any suggestion to do it right and handle defer probing > properly? Sounds reasonable. Just add proper comment in code to explain that. -- viresh -- 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
