Re: RFC on cpufreq implementation
Viresh Kumar <[email protected]> Mon, 2 Feb 2015 09:28:19 +0530
| Newsgroups | org.kernel.vger.cpufreq,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-pm |
|---|---|
| Message-ID | <CAKohpomzCEjXUrxUJjypaA77=r4j_ZPa+x3gM=cNN0kc3ux0uQ@mail.gmail.com> |
On 31 January 2015 at 05:14, Mason <[email protected]> wrote: > I see some platforms have it in their machine-specific folder, others > are in drivers/cpufreq. (When to use mach vs plat?) drivers/cpufreq/ > If it's supposed to go in drivers/cpufreq, I suppose there are naming > conventions to follow? You can check existing drivers. > Also, if it's in drivers/cpufreq, we are not supposed to include > any machine-specific includes? And I'm back to my original question > where am I supposed to store machine-specific information, such as > register descriptions and MMIO addresses and offsets? Define registers/etc in your driver only or somewhere in include/ . Also, try to see if you can reuse cpufreq-dt.c, your driver wouldn't make it to the kernel otherwise.