From: Mason <mpeg.blue@free.fr>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Linux PM" <linux-pm@vger.kernel.org>,
cpufreq <cpufreq@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Arnd Bergmann" <arnd@arndb.de>, "Måns Rullgård" <mans@mansr.com>
Subject: Re: RFC on cpufreq implementation
Date: Sat, 31 Jan 2015 00:44:15 +0100 [thread overview]
Message-ID: <54CC174F.10703@free.fr> (raw)
In-Reply-To: <CAKohponrzDb4ZGvRtJ5jtGTPAy4RCfRsYGvdjR5fx51K2=evCg@mail.gmail.com>
On 30/01/2015 02:15, Viresh Kumar wrote:
> What do you want to do with this driver? If you want to get it reviewed,
> please send it properly with git-send-email instead of attachments..
>
> If its just an internal one, then sorry, the lists aren't for such reviews.
The long-term goal is to mainline the whole port, but it's rather
overwhelming, and I haven't found a way to divide-and-conquer, yet.
I've been reading guides and documentation for weeks, but nothing
has made my brain click.
Everything seems to involve DeviceTree, and AFAIU, going down that
rabbit-hole means making lots of changes all over. (But I probably
misunderstood that part too.)
Right now, all I have is this cleaned up cpufreq driver. And I don't
even know where to put it!
I see some platforms have it in their machine-specific folder, others
are in drivers/cpufreq. (When to use mach vs plat?)
If it's supposed to go in drivers/cpufreq, I suppose there are naming
conventions to follow?
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?
Two months ago, Arnd wrote:
> I meant the IO_ADDRESS stuff. Modern code uses ioremap() instead
> since the IO_ADDRESS was platform specific, and drivers can no longer
> use platform headers on CONFIG_ARCH_MULTIPLATFORM, which is used
> for all new code now.
Regards.
WARNING: multiple messages have this Message-ID (diff)
From: mpeg.blue@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: RFC on cpufreq implementation
Date: Sat, 31 Jan 2015 00:44:15 +0100 [thread overview]
Message-ID: <54CC174F.10703@free.fr> (raw)
In-Reply-To: <CAKohponrzDb4ZGvRtJ5jtGTPAy4RCfRsYGvdjR5fx51K2=evCg@mail.gmail.com>
On 30/01/2015 02:15, Viresh Kumar wrote:
> What do you want to do with this driver? If you want to get it reviewed,
> please send it properly with git-send-email instead of attachments..
>
> If its just an internal one, then sorry, the lists aren't for such reviews.
The long-term goal is to mainline the whole port, but it's rather
overwhelming, and I haven't found a way to divide-and-conquer, yet.
I've been reading guides and documentation for weeks, but nothing
has made my brain click.
Everything seems to involve DeviceTree, and AFAIU, going down that
rabbit-hole means making lots of changes all over. (But I probably
misunderstood that part too.)
Right now, all I have is this cleaned up cpufreq driver. And I don't
even know where to put it!
I see some platforms have it in their machine-specific folder, others
are in drivers/cpufreq. (When to use mach vs plat?)
If it's supposed to go in drivers/cpufreq, I suppose there are naming
conventions to follow?
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?
Two months ago, Arnd wrote:
> I meant the IO_ADDRESS stuff. Modern code uses ioremap() instead
> since the IO_ADDRESS was platform specific, and drivers can no longer
> use platform headers on CONFIG_ARCH_MULTIPLATFORM, which is used
> for all new code now.
Regards.
next prev parent reply other threads:[~2015-01-30 23:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 17:24 RFC on cpufreq implementation Mason
2015-01-15 17:24 ` Mason
2015-01-16 9:08 ` Krzysztof Kozlowski
2015-01-16 9:08 ` Krzysztof Kozlowski
2015-01-16 11:10 ` Mason
2015-01-16 11:10 ` Mason
2015-01-16 11:43 ` Krzysztof Kozlowski
2015-01-16 11:43 ` Krzysztof Kozlowski
2015-01-16 11:43 ` Krzysztof Kozlowski
2015-01-16 12:10 ` Javi Merino
2015-01-16 12:10 ` Javi Merino
2015-01-16 14:00 ` Mason
2015-01-16 14:00 ` Mason
2015-01-19 7:52 ` Viresh Kumar
2015-01-19 7:52 ` Viresh Kumar
2015-01-19 22:03 ` Mason
2015-01-19 22:03 ` Mason
2015-01-20 3:55 ` Viresh Kumar
2015-01-20 3:55 ` Viresh Kumar
2015-01-19 9:22 ` Amit Kucheria
2015-01-19 9:22 ` Amit Kucheria
2015-01-19 22:13 ` Mason
2015-01-19 22:13 ` Mason
2015-01-29 16:43 ` Mason
2015-01-29 16:43 ` Mason
2015-01-30 1:15 ` Viresh Kumar
2015-01-30 1:15 ` Viresh Kumar
2015-01-30 23:44 ` Mason [this message]
2015-01-30 23:44 ` Mason
2015-02-02 3:58 ` Viresh Kumar
2015-02-02 3:58 ` Viresh Kumar
2015-02-04 0:07 ` Mason
2015-02-04 0:07 ` Mason
2015-02-04 0:32 ` Måns Rullgård
2015-02-04 0:32 ` Måns Rullgård
2015-02-04 4:12 ` Viresh Kumar
2015-02-04 4:12 ` Viresh Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54CC174F.10703@free.fr \
--to=mpeg.blue@free.fr \
--cc=arnd@arndb.de \
--cc=cpufreq@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mans@mansr.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.