From: d-gerlach@ti.com (Dave Gerlach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: ti: Use generic platdev driver
Date: Wed, 14 Sep 2016 16:36:02 -0500 [thread overview]
Message-ID: <57D9C2C2.6070807@ti.com> (raw)
In-Reply-To: <20160914204137.20346-1-d-gerlach@ti.com>
On 09/14/2016 03:41 PM, Dave Gerlach wrote:
> Now that the cpufreq-dt-platdev is used to create the cpufreq-dt platform
> device for all OMAP platforms and the platform code that did it
> before has been removed, add ti,am33xx and ti,dra7xx to the machine list
> in cpufreq-dt-platdev which had relied on the removed platform code to do
> this previously.
>
> Fixes: 7694ca6e1d6f ("cpufreq: omap: Use generic platdev driver")
> Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
> ---
This got left out when OMAP was originally added to the
cpufreq-dt-platdev, so cpufreq disappeared on am335x and dra7 platforms.
This patch together with the series here [1] will fix this regression.
Regards,
Dave
[1] http://marc.info/?l=linux-pm&m=147388667613317&w=2
> drivers/cpufreq/cpufreq-dt-platdev.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> index 0bb44d5b5df4..d5e8ba50f8a3 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -68,6 +68,8 @@ static const struct of_device_id machines[] __initconst = {
>
> { .compatible = "sigma,tango4" },
>
> + { .compatible = "ti,am33xx", },
> + { .compatible = "ti,dra7", },
> { .compatible = "ti,omap2", },
> { .compatible = "ti,omap3", },
> { .compatible = "ti,omap4", },
>
next prev parent reply other threads:[~2016-09-14 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 20:41 [PATCH] cpufreq: ti: Use generic platdev driver Dave Gerlach
2016-09-14 21:36 ` Dave Gerlach [this message]
2016-09-15 6:25 ` Viresh Kumar
2016-09-16 21:29 ` Dave Gerlach
2016-09-16 21:59 ` Rafael J. Wysocki
2016-09-19 20:41 ` Dave Gerlach
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=57D9C2C2.6070807@ti.com \
--to=d-gerlach@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).