On 27 January 2013 21:12, Andrew Lunn <andrew@xxxxxxx> wrote: > And how would the module get loaded? There is no hardware anchor to > make the module load. No enumeration of some bus causing it to be > loaded. In the ARM world, platform drivers are the norm. The way you do it now is by creating a platform device for it in your arch/arm/mach-* directory. And you are passing an IOMEM resource too. I believe, normally we don't require any DT node or platform device from arch/arm/mach-* for cpufreq drivers. This is something which should always be initialized once it is selected in .config. Because we will call the _probe() (or renamed as kirkwood_cpufreq_init) from module_init() now, it will get initialized directly. No need to any enumeration at all. Now, in case there are multiple values of IOMEM resource depending on machine type, you can create properties in cpu node. Otherwise just embed the address directly into driver as nobody else is going to use it. Makes sense? -- viresh -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
