From: Kim Phillips <kim.phillips@freescale.com>
To: <Yuantian.Tang@freescale.com>
Cc: rjw@sisk.pl, linuxppc-dev@lists.ozlabs.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/3] cpufreq: Add cpufreq driver for Freescale e500mc SOCs
Date: Wed, 27 Mar 2013 14:32:36 -0500 [thread overview]
Message-ID: <20130327143236.7cb4613b78ad18d79bfbcc57@freescale.com> (raw)
In-Reply-To: <1364265391-26077-3-git-send-email-Yuantian.Tang@freescale.com>
On Tue, 26 Mar 2013 10:36:31 +0800
<Yuantian.Tang@freescale.com> wrote:
> +static int __init ppc_corenet_cpufreq_init(void)
> +{
> + int ret = 0;
> + struct device_node *np;
> + const struct of_device_id *match;
> +
> + np = of_find_matching_node(NULL, node_matches);
> + if (!np)
> + return -ENODEV;
> +
> + match = of_match_node(node_matches, np);
> + freq_data.cpus_per_cluster = (long)match->data;
> + mutex_init(&freq_data.cpufreq_lock);
> + of_node_put(np);
> +
> + ret = cpufreq_register_driver(&ppc_corenet_cpufreq_driver);
> + if (ret)
> + return ret;
> +
> + pr_info("Freescale PowerPC corenet CPU frequency scaling driver\n");
> +
> + return ret;
> +}
> +
> +static void __exit ppc_corenet_cpufreq_exit(void)
> +{
> + cpufreq_unregister_driver(&ppc_corenet_cpufreq_driver);
> +}
> +
> +module_init(ppc_corenet_cpufreq_init);
> +module_exit(ppc_corenet_cpufreq_exit);
this needs to be a module_platform_driver.
Kim
next prev parent reply other threads:[~2013-03-27 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 2:36 [PATCH 1/3] powerpc/mpc85xx: Update the clock device tree nodes Yuantian.Tang
2013-03-26 2:36 ` [PATCH 2/3] clk: add PowerPC corenet clock driver support Yuantian.Tang
2013-03-26 2:36 ` [PATCH 3/3] cpufreq: Add cpufreq driver for Freescale e500mc SOCs Yuantian.Tang
2013-03-26 5:03 ` Viresh Kumar
2013-03-27 19:32 ` Kim Phillips [this message]
2013-03-28 3:02 ` Tang Yuantian-B29983
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=20130327143236.7cb4613b78ad18d79bfbcc57@freescale.com \
--to=kim.phillips@freescale.com \
--cc=Yuantian.Tang@freescale.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rjw@sisk.pl \
/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).