From: Mason <slash.tmp@free.fr>
To: Arnd Bergmann <arnd@arndb.de>, Viresh Kumar <viresh.kumar@linaro.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-pm <linux-pm@vger.kernel.org>
Subject: Re: [PATCH RFC] Add cpufreq support
Date: Tue, 9 Feb 2016 11:17:48 +0100 [thread overview]
Message-ID: <56B9BCCC.8060404@free.fr> (raw)
In-Reply-To: <7910928.pmJjZiV1Lk@wuerfel>
On 08/02/2016 14:45, Arnd Bergmann wrote:
> That's why I said we could introduce a 'v3' with the meaning
> it should have had to start with: compatible means actually
> compatible with the driver.
If I understand correctly, something needs to change in the
framework before I can push cpufreq support for my platform
upstream, correct?
Could you CC me if anything happens on that front?
In my local 4.4 branch, I think I should use whatever method
was recommended at the time.
Was that to define the platform's init_late method, and call
platform_device_register_simple from there? (Could you take
a quick glance at the patch, and see if it is acceptable in
the context of kernel 4.4?)
Regards.
WARNING: multiple messages have this Message-ID (diff)
From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] Add cpufreq support
Date: Tue, 9 Feb 2016 11:17:48 +0100 [thread overview]
Message-ID: <56B9BCCC.8060404@free.fr> (raw)
In-Reply-To: <7910928.pmJjZiV1Lk@wuerfel>
On 08/02/2016 14:45, Arnd Bergmann wrote:
> That's why I said we could introduce a 'v3' with the meaning
> it should have had to start with: compatible means actually
> compatible with the driver.
If I understand correctly, something needs to change in the
framework before I can push cpufreq support for my platform
upstream, correct?
Could you CC me if anything happens on that front?
In my local 4.4 branch, I think I should use whatever method
was recommended at the time.
Was that to define the platform's init_late method, and call
platform_device_register_simple from there? (Could you take
a quick glance at the patch, and see if it is acceptable in
the context of kernel 4.4?)
Regards.
next prev parent reply other threads:[~2016-02-09 10:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 16:58 [PATCH RFC] Add cpufreq support Mason
2016-02-05 16:58 ` Mason
2016-02-05 22:24 ` Arnd Bergmann
2016-02-05 22:24 ` Arnd Bergmann
2016-02-07 12:22 ` Viresh Kumar
2016-02-07 12:22 ` Viresh Kumar
2016-02-08 12:24 ` Arnd Bergmann
2016-02-08 12:24 ` Arnd Bergmann
2016-02-08 12:31 ` Viresh Kumar
2016-02-08 12:31 ` Viresh Kumar
2016-02-08 12:34 ` Arnd Bergmann
2016-02-08 12:34 ` Arnd Bergmann
2016-02-08 12:41 ` Viresh Kumar
2016-02-08 12:41 ` Viresh Kumar
2016-02-08 13:10 ` Arnd Bergmann
2016-02-08 13:10 ` Arnd Bergmann
2016-02-08 13:16 ` Viresh Kumar
2016-02-08 13:16 ` Viresh Kumar
2016-02-08 13:45 ` Arnd Bergmann
2016-02-08 13:45 ` Arnd Bergmann
2016-02-09 10:17 ` Mason [this message]
2016-02-09 10:17 ` Mason
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=56B9BCCC.8060404@free.fr \
--to=slash.tmp@free.fr \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--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.